What social engineering testing is
Social engineering testing is an authorised assessment of how people, processes and security controls respond to realistic attempts to manipulate trust. Depending on the agreed scenario, this can include phishing, vishing, smishing, pretexting or other targeted interactions.
The objective is not to embarrass individuals or create a blame exercise. It is to understand where an attacker could exploit information, authority, urgency or process gaps, and where staff respond well.
Every engagement is carefully scoped with clear boundaries, escalation routes and handling rules before any contact begins.
Carefully governed, realistic scenarios
Effective social engineering is more than sending a generic email to everyone. We develop scenarios around the organisation, the behaviours being assessed and the controls you want to understand.
Open source intelligence may inform the scenario, but the work remains within the agreed legal, ethical and operational boundaries.
What we test
The exact coverage depends on the environment and the scope we agree with you. Typical testing includes the areas below.
Open source intelligence
Publicly available information that could help an attacker identify staff, suppliers, technologies, authority structures or plausible pretexts.
Target and scenario design
Representative groups, realistic objectives and scenarios aligned to the risk you want to measure.
Phishing
Authorised email based scenarios designed to assess reporting, verification and response behaviour.
Vishing
Authorised voice scenarios that test how requests for information, action or access are handled.
Smishing
Authorised SMS based scenarios where this is appropriate to the agreed objective and audience.
Pretexting and impersonation
Use of a plausible identity or situation to test whether established verification processes are followed.
Credential and information requests
How people respond when asked to disclose or use sensitive information, without collecting more than the approved scenario requires.
Process and approval controls
Whether help desks, finance, HR, facilities or other teams follow expected verification and escalation steps.
Reporting and escalation
How quickly and effectively suspicious contact is recognised, reported and handled.
Technical control interaction
Where relevant, how email security, web filtering, identity controls and reporting mechanisms support staff.
Positive behaviours
Where people challenge, verify or report the scenario correctly, so effective controls and culture are visible in the outcome.
Organisational lessons
Patterns that point to improvements in process, tooling, communications or role specific training.
Training can follow the assessment
Where the results show a need for targeted development, related Security Training can be shaped around the scenarios, roles and process gaps that matter to your organisation.
A measurement exercise, not a blame exercise
People should not be treated as the security problem. Attackers exploit the situations, information and processes around them. A useful assessment therefore looks at the system as a whole: the scenario, the controls, the response route and the organisational context.
Reporting focuses on patterns and practical improvements while respecting the handling and confidentiality rules agreed for the engagement.
How we test
Every engagement is different, but the process should never be a mystery. We agree what we are testing and how we will approach it before any assessment begins.
Scope
We start by understanding what you want to test and what you need to learn. Together, we define the environment, access, accounts, exclusions and rules of engagement so the boundaries are clear.
Test
We assess the agreed scope using hands on investigation and the tools appropriate to the engagement. We investigate weaknesses and connected attack paths while taking care to minimise risk.
If we uncover something that needs immediate attention, we will not wait for the final report to tell you.
Report
You receive clear evidence of what we found, why it matters and what your team can do about it, with technical detail and concise executive context.
Retest
Once agreed findings have been addressed, we retest them to verify that the original vulnerabilities can no longer be reproduced and update the outcome.
What you receive
The report is written so technical teams and decision makers can work from the same assessment.
- Findings — the weaknesses that matter, described in the context of the environment tested.
- Evidence — enough detail to understand and, where appropriate, reproduce each issue.
- Impact — what an attacker could achieve, not only a severity label.
- Remediation — practical guidance your team can use to address the issue.
- Prioritisation — a clear view of what to fix first.
- Executive context — a concise summary for security leaders and decision makers.
- Retest of high and critical findings — once agreed issues have been addressed, we retest them and update the outcome.
When should you commission social engineering testing?
There is no single right interval. These are common points at which organisations ask us to test.
Before or after awareness initiatives
To establish a baseline or understand whether targeted education and process changes are having the intended effect.
After process or organisational changes
When new staff, suppliers, support models or approval routes have changed how sensitive requests are handled.
When targeted attacks are a credible concern
For organisations or roles likely to face impersonation, fraud, credential theft or information gathering attempts.
To test reporting and escalation
When you want to know whether suspicious contact reaches the right team quickly enough.
As part of a wider red team or assurance programme
Where human and process controls need to be assessed alongside technical controls.
After a real social engineering incident
To identify process gaps and verify improvements without recreating unnecessary harm.
Related services
This assessment is one part of the attack surface. These related services are often considered alongside it. You can also see all penetration testing services.
Network & Infrastructure Penetration Testing
Assess the technical attack paths that stolen access or credentials could expose.
Wireless Penetration Testing
Test local wireless exposure and the routes available from a nearby foothold.
Security training
Develop role specific understanding and practical response skills after the assessment.
Social engineering testing FAQs
Short answers to common questions before an assessment. If yours is not here, tell us what you need.
Is social engineering testing legal?
It must be explicitly authorised and carefully scoped. We agree the permitted scenarios, targets, times, data handling, escalation routes and prohibited actions before any activity begins.
Will employees know they are being tested?
That depends on the objective and scope. The sponsor group and escalation contacts are agreed in advance, while broader notification is designed around the integrity and safety of the exercise.
Do you collect real passwords?
The handling of credentials and sensitive data is agreed before testing. We avoid collecting more than is necessary to meet the approved objective and use safe simulation where appropriate.
Can you test phishing, vishing and smishing?
Yes, where the requested method is appropriate and authorised. Different channels can be scoped separately or combined around a defined scenario.
How are results reported?
The report focuses on patterns, controls, reporting behaviour and practical improvements. Individual handling and confidentiality are agreed during scoping.
Is this the same as security awareness training?
No. Testing measures how controls and behaviours respond to a scenario. Training develops knowledge and skills. They can support each other, but they have different purposes.
Can you retest after improvements?
Yes. A follow up exercise can be designed to assess whether agreed process, control or training changes have improved the response.
Ready to put your security to the test?
Tell us what you would like tested, what you are trying to understand and any timescales you are working with.
We will help you define the right scope and approach before anything begins.