A social engineering assessment is an authorised, scoped attempt to manipulate your staff and your processes the way a real attacker would, through phishing emails, phone calls, messages or physical access, so you find the weak points before someone hostile does. Phishing assessment is the most common part of it, but the strongest assessments also test the procedures behind the people: who can reset a password, change a supplier's bank details or walk through a door unchallenged.
This guide explains what the work covers, how to scope and authorise it safely under UK guidance, what a useful report contains, what drives the price, and how to turn the findings into fixes.
Key Takeaways
- A social engineering assessment tests people and processes, not just inboxes. Phishing simulation is one method among several.
- Phishing is the most common cyber attack on UK organisations, so it is the sensible place to start for most startups, schools and charities.
- Written authorisation, a signed scope and a named person who can stop the test protect your staff and your business.
- Judge the exercise by reporting rates and process fixes, not by naming and shaming people who clicked.
- Pair it with technical testing and baseline controls such as Cyber Essentials so one mistake cannot become a breach.
Table of Contents
- What a social engineering assessment actually is
- Why phishing is the first thing to test
- Methods a social engineering assessment can include
- Scoping and authorising the work safely
- What the report should tell you
- Acting on the findings
- Linking it to technical controls and Cyber Essentials
- What affects the cost
- How to choose a provider
- Talk to Solusec about your next test
- FAQ
- Sources
What a social engineering assessment actually is
The National Protective Security Authority (NPSA) describes social engineering as obtaining information from others under false pretences by building an inappropriate trust relationship. It can be aimed at employees in order to gain entry to a site, access secure IT systems or persuade someone to share protected information using a bogus pretext.
An assessment turns that into a controlled exercise. An independent tester, with your written permission, tries the same tactics against a defined group of people and processes. They record what worked, what was stopped and what was reported, then explain how to close the gaps.
It differs from a vulnerability scan or a standard penetration test. Those look for flaws in software and configuration. A social engineering assessment looks for flaws in behaviour, habit and procedure. If you want to understand where the technical side ends and the human side begins, our explanation of penetration testing versus a vulnerability scan is a good companion read.

Why phishing is the first thing to test
The numbers explain why most assessments start with email. The UK Government's Cyber Security Breaches Survey 2025/2026 found phishing was by far the most prevalent type of breach or attack, experienced by 38% of businesses and 25% of charities. It was also the type most often cited as the most disruptive, by 69% of the businesses and charities that had experienced a breach or attack.
The previous year's edition showed the same pattern. The Cyber Security Breaches Survey 2025 found phishing accounted for 93% of businesses and 95% of charities that had experienced a cyber crime.
The National Cyber Security Centre (NCSC) notes that phishing can hit an organisation of any size or type and may be the first step in a targeted spear-phishing attack. A small charity or a school is no less likely a target than a large firm, and usually has fewer people checking each message.
Methods a social engineering assessment can include
The mix depends on your risks. Typical options are:
| Method | What the tester does | What it reveals |
|---|---|---|
| Phishing simulation | Sends realistic emails with links, attachments or login pages | Click, disclosure and reporting behaviour |
| Spear phishing | Crafts messages aimed at specific roles, such as finance or the head teacher's office | Whether targeted pretexts beat your filters and staff |
| Phone pretexting (vishing) | Calls staff or the help desk posing as a colleague, supplier or IT | Weak identity checks and information leakage |
| Text-message pretexting (smishing) | Sends messages that urge a quick action | Risk on mobile devices |
| Physical access testing | Attempts to enter a site, tailgate or reach restricted areas | Door, reception and visitor procedures |
| Process challenges | Requests a payment change, password reset or new supplier set-up | Whether procedures hold under pressure |
You rarely need every row. A ten-person startup might only need a phishing simulation plus a test of how a payment-change request is handled. A secondary school with several sites may want a physical element as well.
Where phishing assessment fits
Think of phishing assessment as the repeatable, measurable core. The NPSA's phishing simulation guidance identifies three measures of success: the click rate, the disclosure rate (people who enter credentials when prompted) and the reporting rate (people who report the email).

The reporting rate is the one many organisations overlook. A staff member who spots a suspicious email and tells IT gives you an early warning that no filter can match. A rising reporting rate is often a better sign of progress than a falling click rate.
The same guidance recommends a structured and systematic approach so that results can be compared over time and across groups, and the largest practical sample size, while keeping the questions you are answering manageable. It also warns against sending the same simulation to too many people working close together, because responses then reflect how many others received it rather than individual judgement.
Scoping and authorising the work safely
A social engineering assessment deceives real people, so the paperwork matters more than in a technical test. Done badly, it harms trust, breaches data rules or upsets suppliers.
What the scope should record
The NCSC's CyAS Scheme Standard is written for advanced adversary simulation, but its list of what must be formally recorded and signed off is a good model for any assessment. It includes goals and objectives, critical functions and assets, exclusions, risk mitigation, a core team on your side with authority to pause or stop the work, data handling, the social engineering methodology and its boundaries, and cost.
For a smaller organisation, that translates into a short written agreement that answers:
- What are we trying to learn? For example, whether staff report phishing, or whether the finance team verifies bank-detail changes.
- Who and what is in scope? Departments, roles, sites, phone lines. Name what is out of bounds, such as personal accounts and family members.
- Which methods are allowed? Email only, or email plus calls, or physical visits.
- Who can stop it? A named senior contact reachable throughout.
- How is data handled? What the tester captures, where it is stored and when it is deleted.
- When does it run? Avoid exam periods, year-end or a major incident.
The NCSC's adversary simulation guidance encourages an adversarial mindset while agreeing objectives with the customer, rather than just copying known tactics. In practice, agree the goal and the limits, then let the tester choose realistic pretexts within them.
If you want to see how scoping works for technical testing, our guide to scoping a penetration test for approvers sets out the approval steps, and much of it applies here too.
Pick the high-impact processes first
Research from 360iResearch suggests prioritising high-impact workflows such as payment changes, password resets, privileged access, executive communications, vendor onboarding and physical entry. These are the moments where one convincing request does the most damage, so they give the most useful findings.
HR, legal and consent
The NCSC warns that phishing simulations can create legal risk: punishing people for clicking on emails you sent starts to resemble entrapment, so check with your HR department before running one. Involve HR and, if you have one, your legal adviser before the exercise starts.
NIST's guidance for learning programmes makes a similar point from the US side. It says legal teams should help design and review phishing exercises to avoid problems such as using legitimate brands in the bait, and that staff should be told exercises happen on a random basis and that results guide learning rather than punishment.
If the test touches software or services run by a third party, such as a hosted email platform or a supplier portal, you also need their permission. The UK Government Service Manual says you must get explicit consent from any third-party supplier whose software you want to review as part of a test, and check your contract confirms it.
Handling personal data
A test can capture names, email addresses and, in a credential-harvesting exercise, login attempts. Decide in advance what is recorded, who sees it and how long it is kept. A useful habit is to look at how any service or tool you use explains its own data handling; a page such as this overview of security, encryption and data handling shows the kind of detail worth looking for. Your tester should be able to give you the same clarity about how they store test data.
What the report should tell you
A good report does more than list who fell for what. The NCSC says an adversary simulation report should cover all engagement stages, including reconnaissance, explain how objectives were achieved, identify opportunities to detect the activity and recommend improvements.
The same guidance says that where social engineering was used, the details of targeted users should be anonymised to avoid harm. The report should focus on the privileges obtained and how they supported the rest of the attack, not on naming individuals. That is the standard to ask for.
Expect these elements:
- A summary for non-technical readers, with the headline result and the business impact.
- Method and timeline, so you can see what was tried and when.
- Measured results, such as click, disclosure and reporting rates by department or role, not by person.
- Severity ratings for each finding. The NCSC's penetration testing guidance describes a typical test as engagement, scoping, testing, reporting and follow-up, with a severity rating for issues found.
- Process findings, for example that a help-desk agent reset a password without verifying identity.
- Prioritised, proportionate recommendations that a small team can actually do.
Acting on the findings
The point of the exercise is the change afterwards. Three principles help.
Do not rely on training alone. The NCSC is clear that no training package, including phishing simulations, can teach users to spot every phishing attempt, and that asking people to examine every email in depth is unrealistic because responding to emails and clicking links is part of work. Build defences that still work when someone makes a mistake.
Fix the process, not just the person. 360iResearch recommends reviewing trends by process and control owner rather than relying on one employee-focused metric, and pairing exercises with role-based training, stronger identity verification, technical reporting mechanisms, help-desk safeguards and recurring validation. If a payment change went through on one email, the fix is a call-back rule, not a stern reminder.
Keep it non-punitive. NIST states that no employee should be called out for their response; treated as learning opportunities, exercises show where vulnerabilities lie and who may need extra support. Staff who fear blame stop reporting, and your reporting rate is your best early warning.
A practical sequence after the report:
- Brief leadership on the headline findings and agree owners and deadlines.
- Fix the high-severity process gaps first: verification rules, approval chains, visitor handling.
- Make reporting easy, with one button or one address and a quick, friendly response.
- Share anonymised results with all staff, with what went well as well as what did not.
- Re-test after the changes, using a comparable method so you can see the movement.
The NPSA adds that vulnerability at work can mirror vulnerability at home, and recommends highlighting personal relevance when designing exercises. Tips on spotting scam texts and calls that protect staff families also protect your organisation.
Linking it to technical controls and Cyber Essentials
People will sometimes click. What limits the damage is the technical layer: up-to-date software, secure configuration, malware protection, sensible access rights and multi-factor authentication. That layer is what Cyber Essentials covers, and it is often the sensible next step after a phishing exercise shows how easily a credential can be taken.
If you want an independent check of your technical posture first, a gap analysis for Cyber Essentials is priced at £300. Schools can look at Cyber Essentials for schools, and organisations that want hands-on verification of their controls can read about Cyber Essentials Plus. For a clear view of which level suits you, see Cyber Essentials versus CE Plus.
What affects the cost
Prices vary by provider and there is no single UK rate card, so be wary of any quote given without a scoping conversation. The factors that move the price are consistent:
- Number of methods. Email-only simulation is simpler than email plus phone plus physical visits.
- Number of people and sites in scope, and whether targeting is generic or tailored to roles.
- Depth of reconnaissance. Researching staff and suppliers to build convincing pretexts takes tester time.
- Reporting and follow-up. A debrief with your leadership, or a re-test, adds effort but adds value.
- Timing and constraints, such as out-of-hours work or multiple sites.
For context on our published technical testing prices, an external IP test is £3,000 and a CMS website test is £2,500. Those are for technical tests, not social engineering work, but they show how we price: a clear fixed fee for a clearly defined scope. Ask any provider to state the scope, the number of days and what the report includes.
How to choose a provider
Look for accredited testers who talk to you directly, agree a written scope and explain results in plain English. Ask who will actually carry out the work, how they protect staff details in the report, and how they handle stopping the test if something goes wrong. Our guide on choosing a penetration testing provider lists questions that apply equally to a human-layer assessment.
Talk to Solusec about your next test
We are a CREST-accredited organisation, and you deal directly with the experts who test and assess, not a sales team. We keep advice proportionate for startups, small businesses, schools, colleges, universities and charities, so you get findings you can act on.
If you are planning to test the human side of your security alongside your systems, tell us about your people, sites and priorities and we will talk through a sensible scope with you.

Start with our penetration testing services, or get in touch through solusec.co.uk to discuss what you need. If you want regular assurance rather than a one-off, our annual penetration testing option shows how repeat testing can be set up.
FAQ
What is the difference between social engineering testing and a phishing assessment?
Phishing assessment is one part of social engineering testing. It focuses on emails and messages and measures click, disclosure and reporting rates. Wider social engineering testing can add phone calls, physical access attempts and tests of procedures such as payment changes and password resets.
Do we need to tell staff before a social engineering assessment?
A small group of senior people must know and approve it, including someone with authority to stop the test. Most staff are not told the date, as that would defeat the purpose. NIST advises telling employees generally that exercises run on a random basis and that results are used for learning, not punishment.
How often should we run a phishing assessment?
There is no single required frequency. A structured, repeatable approach lets you compare results over time, as the NPSA recommends. Many organisations run an exercise after a change in staff, systems or processes, and then repeat it to check that fixes have worked.
Is a social engineering assessment legal?
Yes, when it is authorised in writing, scoped and carried out with care for people's data and wellbeing. Involve HR and legal advice before starting, avoid punishing staff who click, and get consent from any third parties whose systems are involved.
Will a social engineering assessment stop us being phished?
No exercise can stop every attack. It shows where your people and procedures are weakest, so you can add checks, make reporting easy and strengthen technical controls so that a single mistake is less likely to become a breach.
Sources
- Social Engineering, NPSA
- Cyber Security Breaches Survey 2025/2026, GOV.UK
- Cyber Security Breaches Survey 2025, GOV.UK
- Phishing attacks: defending your organisation (PDF), NCSC
- Phishing attacks: defending your organisation, NCSC
- Phishing simulations guide, NPSA
- A quick reference guide for organisations, NPSA
- Scheme Standard v1.1, Cyber Adversary Simulation (CyAS), NCSC
- Adversary simulation: what you need to know, NCSC
- Adversary simulation: what you need to know (PDF), NCSC
- Penetration testing, NCSC
- Vulnerability and penetration testing, GOV.UK Service Manual
- Building a Cybersecurity and Privacy Learning Program, NIST SP 800-50 Rev. 1
- Social Engineering Penetration Testing, 360iResearch
- Security, encryption, and your data, Omphalis
Recommended
This article was created with assistance of AI. We never use AI with your data unless given explicit permission.
