PenTesting Company
Nighttime satellite view of the United States, showing city lights from coast to coast

Social engineering testing

Social Engineering Tests - Protect Your Organization

Many security incidents start with people, not software. A social engineering test measures how your organization responds when someone tries to trick staff into giving up access or information, and it shows you where to strengthen training and controls.

Short answer

What a social engineering test is, and how it differs from training.

Planning an on-site visit at a named site? Jump to the on-site authorization worksheet.

What is social engineering testing?

Social engineering is an umbrella term for attacks that target people rather than hardware or software. Instead of breaking a system directly, an attacker convinces someone to open a door for them, by clicking a link, sharing a password, approving a request, or handing over information they should not.

Social engineering testing is an authorized, scoped exercise that measures how your people and processes respond when someone tries to trick them into giving up access or information. Testers run scenarios agreed with your organization, such as a phishing email or a phone call with a believable pretext, and note how each one was handled and which controls helped. You get a report on patterns and process gaps, with practical guidance for training, procedures, and technical controls, without blame.

Phishing email

What it measures
Whether people open the message, click, enter details on a landing page, or report it, how quickly the first report reaches the security team, and whether email filtering and the report button help.
When to choose it
You want to see how staff handle the kind of message they are most likely to receive, for example after awareness training or a change to email controls.

Phone pretexting (vishing)

What it measures
Whether staff, such as the help desk, follow their own identity verification steps when a caller uses a believable pretext, what information is shared, and whether the call is escalated.
When to choose it
Your help desk, front desk, or support team can reset passwords, grant access, or share account details over the phone.

Physical scenarios, where in scope

What it measures
Whether someone without authorization can gain access to an agreed location or device, and whether staff challenge or report them.
When to choose it
Your offices or sites hold equipment, records, or network access that matters, and you want to check how access controls and staff respond in person. Physical scenarios are included only when agreed in scope.
Plan a social engineering test

Not sure which scenarios fit? Tell us about your organization and we will help you choose.

Training, simulations, and a social engineering test

Teams often ask whether they still need a test if they already run awareness training or a phishing platform. Those programs teach and practice. A test is a scoped, authorized look at agreed scenarios, with a written report.

Security awareness training

What it does
Teaches staff how to recognize and report suspicious messages, calls, and in-person requests.
What you get
Curriculum, completion records, and a shared vocabulary for how to handle those requests.
When it fits
Ongoing, especially for new staff and after you change procedures or tools.

Automated phishing simulations

What it does
Sends recurring simulated messages and tracks who opened, clicked, submitted details, or reported the message.
What you get
Rates over time, and often a coaching loop for people who click. Individual scores are common.
When it fits
You want practice at work, on a schedule, without a separate consulting engagement.

Social engineering test

What it does
Runs a defined set of authorized scenarios in an agreed window. That can include phishing email, phone pretexting, and physical access where in scope.
What you get
A written report on process and control gaps, a readout, and practical guidance, without blame. Results focus on patterns, not individuals, unless you agree otherwise in scope.
When it fits
You want an independent look at how people and processes handle a specific set of scenarios, or evidence of testing as one input to a broader program.

Many teams keep training and a simulation platform year-round, then add a social engineering test when they want an independent look at a defined set of scenarios. The test does not replace training, and training does not replace the test. Authorized testing only happens inside the written scope.

Laptop, desktop, and mobile devices used during application testing

What a good report includes

Results you can act on, without blame.

  • Which scenarios were attempted and how they were handled.
  • Business impact described in plain language.
  • Severity rated with a documented, consistent method.
  • Practical guidance for training, process, and technical controls.
  • A readout to walk through the findings with your team.

Social engineering testing methodology, phase by phase

The phases below show how an authorized engagement runs, and what you provide or receive at each step. Pretexts are approved in advance.

Engagements follow a shared structure so your team can see what happens, who is involved, and when testing stops. Authorized testing only happens inside the written scope.

  1. 1

    Scoping and written authorization

    Approval gate

    Named approvers sign

  2. 2

    Reconnaissance

    Agreed sources only

  3. 3

    Pretext and campaign design

    Approval gate

    Approved before use

  4. 4

    Execution

    Email, phone and physical, as scoped

  5. 5

    Credential and access handling

  6. 6

    Reporting

    Aggregate results

  7. 7

    Retest

Approval gates in an authorized social engineering test: named approvers sign written authorization, then approve each pretext, before any email, call, or physical scenario goes out.
Social engineering testing methodology phases, with what happens in each phase and what the client provides or receives
PhaseWhat happensWhat you provide or receive
Scoping and written authorizationThe goals, channels (email, phone, physical, or a combination), named target groups, named approvers, pretexts approved in advance, out-of-bounds people, locations and topics, the testing window, opt-outs, stop conditions, and data handling are agreed in writing. Written authorization has to come from whoever controls each people group, system, and location in scope, including a building owner or landlord when a physical scenario requires it. Pretexts do not use a real third-party brand without permission, and they do not impersonate a real, named person. Pretexts that touch pay, layoffs, health, or personal emergencies stay out unless the organization agrees otherwise in the scope. Authorized testing only happens inside the written scope.You provide written authorization, named approvers, the in-scope channels and groups, exclusions, and a named contact. You receive a written statement of work and rules of engagement.
Reconnaissance limited to agreed sourcesResearch is limited to the sources agreed in scope, such as public pages the organization publishes, to support approved pretexts. It does not extend to employees' private lives or to sources left out of the written scope.You provide or confirm the agreed sources. Reconnaissance usually informs later phases rather than arriving as a standalone deliverable.
Pretext and campaign designEach scenario and pretext for the channels in scope is designed and submitted for approval before any messages are sent or calls are made. A physical scenario, when included, also records that testers will carry written authorization and an after-hours contact on site.You review and approve the pretexts and campaign materials in writing. Messages are not sent, and calls or physical scenarios are not started, until that approval is in place.
Execution across email, phone and physical as scopedOnly the approved scenarios run, in the agreed window, across the email, phone, or physical channels named in scope. An email-only scope stays on the named email group; phone or physical work needs those channels, named targets or groups, locations, and written authorization. The scope-choice table later on this page shows that difference. Agreed measures are recorded, such as reports, clicks, submissions, whether verification steps were followed, and how quickly the organization responded. If a named contact asks to pause, the test stops. For a physical scenario, testers carry the written authorization and an after-hours contact on site. If authorized access is obtained, further work follows the agreed rules of engagement; it is not assumed from a narrower scope.You keep the named contacts available during the window and provide any mid-test decisions the rules call for. If we confirm a critical-severity issue during testing, the rules of engagement set how and how quickly your named contact is told, rather than waiting for the report.
Handling of any credentials or access obtainedAny submitted credentials or access obtained are handled only as the statement of work allows, and only per the rules of engagement. For example, the test can record that a submission happened without keeping the password. Material is not retained beyond what that agreement sets, and obtained access is not used beyond the agreed confirmation.You provide any decisions the rules call for about resets, revocation, or disposal. You receive whatever record of handling that agreement sets.
ReportingThe agreed scenarios, how they were handled, business impact, severity, and practical guidance for training, process, and technical controls are documented. Results are reported in aggregate and focus on processes, controls, and patterns. Individual employees are not named or shamed. How any individual-level detail is handled, and who can see it, is agreed in scope.You receive the written report and a readout with your team.
RetestA retest, when included, returns to the original agreed scenarios or confirmed findings, not a second full campaign against every person or location in the organization.Retest terms set in the statement of work. You provide notice that fixes or follow-up are ready when a retest is part of that agreement. You receive whatever that agreement sets.

Illustrative finding, carried through the phases

Illustrative only, not a client or past engagement. Example Corp and example.com are placeholders.

Say Example Corp authorizes a phone pretext test of the IT help desk phone line listed for staff at example.com, with an agreed locked-out staff-member pretext. One finding that can be carried through these phases is a password reset issued after a caller provides only a name and an employee ID. It is the same illustrative help desk finding described in the worked example later on this page.

  1. Scoping and written authorization. Example Corp agrees the help desk line, the locked-out account pretext, named contacts, opt-outs, and written authorization. The testers do not impersonate a real, named person, and they do not use a real third-party brand without permission. Off-limits people and topics are listed in the scope.
  2. Reconnaissance limited to agreed sources. The tester reviews only the sources Example Corp agrees, such as the public staff help information on example.com, and does not research employees' private lives.
  3. Pretext and campaign design. The locked-out staff-member story is approved in writing before any calls are made.
  4. Execution across email, phone and physical as scoped. Within the agreed window, the tester calls the help desk line using that pretext. If a named contact asks to pause, the test stops.
  5. Handling of any credentials or access obtained. If a password reset is issued, the tester confirms that it was issued and does not use the new password beyond what the statement of work allows. Any credential material is handled and retained only as that agreement sets.
  6. Reporting. The finding is written up as a High severity process issue: a caller with a plausible story can be given a password reset after providing only a name and an employee ID, and the verification step in the help desk procedure can be skipped. The report focuses on the procedure, not on the person who took the call.
  7. Retest. Retest terms set in the statement of work. If a retest is included, it would return to this agreed help desk scenario after Example Corp updates the verification steps.

The scope-choice table later on this page shows what email-only, email plus phone, and email plus phone plus physical-access checks can deliberately cover, rather than repeating that comparison here. The worked example that follows it shows a full engagement, from scope to retest.

Our process

  1. 1

    Scope and rules of engagement

    We agree on the scenarios, the targets, and the boundaries before any testing begins.

  2. 2

    Controlled testing

    We run the agreed scenarios in a controlled way and record how they are handled.

  3. 3

    Reporting

    You receive findings with what happened, the impact, severity, and practical guidance.

  4. 4

    Readout

    We walk through the results with your team and answer questions. Retest terms set in the statement of work.

Scoping checklist

These questions define coverage so both sides know what is included. This is about clarity, not a checklist for choosing a vendor.

  • Which scenarios and channels are in scope, such as phishing email, phone calls, or physical access.
  • Who may be targeted and any people or groups that are off limits.
  • What is explicitly out of scope.
  • Rules of engagement and the conditions that stop a test.
  • Who to contact if we confirm a critical-severity issue mid-engagement.

Social engineering testing works best alongside technical testing. If you are also looking at your systems, see our network penetration testing and web application security testing services.

Scope choice: email phishing vs phone pretext vs physical access

Illustrative only, not a client or past engagement. Example Corp and example.com are placeholders.

Say Example Corp wants to know how staff and the help desk handle agreed social engineering scenarios. Before testing, they agree in writing which channels are in scope: email only, email plus a phone pretext, or those plus a physical-access check at a named site. That agreed scope decides which boundaries the test deliberately covers. It does not decide findings in advance. A social engineering test is not a compliance certification. Authorized testing only happens inside the written scope, with named targets or groups, opt-outs, and data handling agreed up front.

Email phishing only

The named email group

Starting point

  • Written authorization; one agreed phishing scenario that does not use a real third-party brand without permission, sent to a named staff group; named contacts who can pause the test; agreed opt-outs and data handling for any submitted credentials.
  • Written authorization has to come from whoever controls each people group in scope.

What you can reach

  • An email-only scope stays on the named email group.
  • Phone verification at the help desk or other teams, and physical access checks at offices or sites, need those channels, named targets or groups, locations, and written authorization. Coverage is only what that email scope names, not every possible public lure.

Deliberately covered

  • Whether the agreed message reaches that named group, how people handle it (report, click, or enter details on the landing page), and how quickly the first report reaches security.
  • Whether email filtering and the report path help, as listed in the statement of work.

Email plus phone pretext

The named email group and help desk line

Starting point

  • Written authorization; the same named email group; the IT help desk phone line listed for staff; one agreed phone pretext that does not impersonate a real, named person; named contacts, opt-outs, and data handling.

What you can reach

  • Email boundaries named in scope, plus the IT help desk phone line listed for staff.
  • Physical access to offices, badge or reception checks, and any phone lines, teams, or pretexts left out of the written scope stay out. If authorized access is obtained during testing, further work follows the agreed rules of engagement; it is not assumed from an email-plus-phone scope.

Deliberately covered

  • Whether the help desk follows its own identity verification steps under the agreed pretext, what information is shared or changed, and whether the call is escalated.

Email, phone, and a physical-access check

A physical-access check at a named site

Starting point

  • Written authorization from whoever controls each people group, phone line, and location in scope, including a building owner or landlord when a physical scenario requires it; named email group; help desk line; one agreed office location; named contacts, opt-outs, and stop conditions.
  • Testers carry the written authorization and an after-hours contact on site.

What you can reach

  • Email and phone boundaries named in scope, plus the agreed office location.
  • Locations, devices, teams, or channels left out of the written scope stay out. Physical coverage is only what that scope names, not every entrance or site. Forced entry, alarm tampering, and any person outside the agreed groups remain out.

Deliberately covered

  • Whether someone without authorization can gain access to the agreed location or device, and whether staff challenge or report them, within the agreed rules of engagement.
The panels compare email phishing only, email plus phone pretext, and email, phone, and a physical-access check for a social engineering test. Each panel shows the starting point, what you can reach, and the checks that choice can deliberately cover. Authorized testing only happens inside the written scope.
Illustrative comparison of email-only, email plus phone pretext, and email plus phone plus physical-access scope for a social engineering test
Scope choiceWhat testers are givenBoundaries this choice can deliberately coverNot deliberately covered without further agreement
Email phishing onlyWritten authorization from Example Corp; one agreed phishing scenario that does not use a real third-party brand without permission, sent to a named staff group at example.com; named contacts who can pause the test; agreed opt-outs and data handling for any submitted credentialsWhether the agreed message reaches that named group, how people handle it (report, click, or enter details on the landing page), how quickly the first report reaches security, and whether email filtering and the report path help, as listed in the statement of workPhone verification at the help desk or other teams, and physical access checks at offices or sites. Those channels need their own named targets or groups, locations, and written authorization. Coverage is only what that email scope names, not every possible public lure
Email plus phone pretextWritten authorization; the same named email group; the IT help desk phone line listed for staff at example.com; one agreed phone pretext that does not impersonate a real, named person; named contacts, opt-outs, and data handlingEmail boundaries named in scope, plus: whether the help desk follows its own identity verification steps under the agreed pretext, what information is shared or changed, and whether the call is escalatedPhysical access to offices, badge or reception checks, and any phone lines, teams, or pretexts left out of the written scope. If authorized access is obtained during testing, further work follows the agreed rules of engagement; it is not assumed from an email-plus-phone scope
Email, phone, and a physical-access checkWritten authorization from whoever controls each people group, phone line, and location in scope (for example Example Corp and, where needed, the building owner or landlord); named email group; help desk line; one agreed office location at example.com's site; named contacts, opt-outs, and stop conditions; testers carry the written authorization and an after-hours contact on siteEmail and phone boundaries named in scope, plus: whether someone without authorization can gain access to the agreed location or device, and whether staff challenge or report them, within the agreed rules of engagementLocations, devices, teams, or channels left out of the written scope stay out. Physical coverage is only what that scope names, not every entrance or site. Forced entry, alarm tampering, and any person outside the agreed groups remain out

After Example Corp agrees the channels in scope, the existing worked example on this page shows one way an email-plus-phone engagement can run from scope to readout. Retest terms set in the statement of work.

Plan the written authorization for an on-site visit

If a physical-access check at a named site is in scope, the written authorization has to record the site-specific details before anyone arrives. The worksheet builds a copy-ready list. It is a planning aid, not itself written authorization, and it does not teach how to run a physical test.

On-site work needs more than a channel being named in scope. The authorization should name the site, who controls it (including a landlord or building owner when needed), the testing window and time zone, in-scope and out-of-scope areas, permitted and forbidden pretext labels, whether testers may take photographs, emergency and verification contacts, and stop conditions. Testers will carry the signed authorization. A social engineering test is not a compliance certification.

On-site authorization worksheet

Fill in the site-specific details to build a copy-ready list of what belongs in the written authorization before anyone arrives. The list is built in your browser. What you enter is not sent or stored. The list is a planning aid, not itself written authorization, and it does not teach how to run a physical test. Example Corp names are placeholders. A social engineering test is not a compliance certification.

Site
Testing window
Areas
Pretext labels

Choose short labels only, not a script. Government, law-enforcement, and real-vendor impersonation are not offered and stay out of the permitted list.

Permitted labels

Forbidden labels

Photographs
Contacts

Someone a staff member or security team can call to confirm the testers are authorized.

Stop conditions

Fill the remaining items before copying. 11 items need attention.

  • Enter the named site.
  • Enter who controls the site.
  • Enter the testing window.
  • Enter the time zone.
  • Enter the in-scope areas.
  • Enter the out-of-scope areas.
  • Choose at least one permitted pretext label, or add a short custom label.
  • Choose whether testers may take photographs.
  • Enter an emergency contact.
  • Enter a verification contact.
  • Choose at least one stop condition, or describe one.
Copy-ready list
On-site authorization list (planning aid)

This list is a planning aid for written authorization. It is not itself written authorization, a statement of work, or permission to begin testing. A social engineering test is not a compliance certification. Authorized testing only happens inside the written authorization.

Pretext labels
- Forbidden labels: Pay, layoffs, health, or personal emergencies; A real, named person
- Pretexts will not impersonate a government or law-enforcement body.
- Pretexts will not use a real vendor or third-party brand without that party's written permission.
- These are labels only. The written authorization should name the approved labels. This list is not a script for how to run a test.

Authorization on site
- Testers will carry the signed written authorization and can present it if challenged.

Before anyone arrives
- The written authorization should include the items above before testers arrive.
- This list does not teach physical testing methods.

An on-site authorization worksheet by The PenTesting Company. Testers will carry the signed authorization. Retest terms set in the statement of work. A social engineering test is not a compliance certification.

What a social engineering test looks like: a worked example

This is an illustrative scenario, not a real client or case study. The organization and results are hypothetical and are here to show how an engagement runs.

Imagine an organization with an office, remote staff, and an IT help desk. It asks for a phishing email test and a phone pretext test against the help desk.

1. Agreed scope and rules of engagement

  • Channels: one phishing email scenario sent to an agreed group of employees, and phone calls to the help desk using an agreed pretext.
  • Off limits: anyone the organization asks us to exclude. We also avoid pretexts that touch pay, layoffs, health, or personal emergencies unless the organization agrees otherwise in the scope.
  • Data handling: we align on how submitted credentials are treated, for example recording that a submission happened without keeping the password.
  • Timing and stop conditions: the testing window, and the conditions that pause or end the test.
  • Contacts: a small number of people who know about the test, and a person to reach if we confirm a critical-severity issue mid-engagement.

2. What is measured

  • Phishing: who opened the message, who clicked, who submitted details on the landing page, and who reported it through the organization's reporting route.
  • Timing: how long it took for the first report to reach the security team, and what happened next.
  • Phone: whether the help desk followed its own identity verification steps, what information was shared, and whether the call was escalated.
  • Controls: whether email filtering, the report button, and call procedures helped or were bypassed.

3. What the report shows

The report describes what was attempted, how each scenario was handled, and what it means for the business, without blame. Hypothetical examples of what it might record:

  • High: A caller with a plausible story was given a password reset after providing only a name and an employee ID, and the verification step in the help desk procedure was skipped.
  • Medium: Some recipients entered details on the landing page, and the first report to the security team arrived well after the first click.
  • Low: The email filter flagged the first message, and a reworded version was delivered, which shows where the filter rules could be tuned.

4. How awareness follow-up works

At the readout we go through the results with security, IT, and the help desk lead. Follow-up is built around what was observed: for example, a short refresher on the verification steps for the help desk, a reminder of how to report a suspicious message, and changes to the call procedure or email controls.

Whether training material is part of the engagement is agreed in scope.

Retest terms set in the statement of work.

A social engineering test is not a compliance certification. It shows how your people and processes responded to the scenarios that were agreed.

Example scope: an authorized phone pretext test

Illustrative only. Example Corp and example.com are placeholder names, not a client. This shows what a written scope for one phone pretext test against a help desk might cover.

  • In scope: the IT help desk phone line listed for staff at example.com, and the help desk team that answers it. No other teams, numbers, or locations.
  • Authorization: written approval from Example Corp, which controls the help desk and its phone line. If the help desk is run by an outside provider, that provider also authorizes the test in writing.
  • Pretext: one agreed story, such as a staff member locked out of their account. Callers use a role agreed in scope and do not impersonate a real, named person.
  • Testing window: agreed business days and hours, with calls only inside that window.
  • Named contacts: a primary and backup contact at Example Corp who know about the test and can pause it. If we confirm a critical-severity issue during testing, the rules of engagement set how and how quickly your named contact is told, rather than waiting for the report.
  • Out of scope: calls to personal phones, pretexts that touch pay, layoffs, health, or personal emergencies, any attempt to use a reset password beyond confirming it was issued, and any system or person not listed above.
  • Report: each call attempted, whether the verification steps were followed, what was shared or changed, severity, and practical guidance for the help desk procedure. Results focus on process, not individuals.

Retest terms set in the statement of work. A phone pretext test is not a compliance certification.

Want a scope like this for your own team? Tell us what you would like to test.

What is included

Beyond the testing itself, you get the deliverables your team needs to prioritize and fix what we find.

  • Scoped social engineering testing of the phishing, vishing, and physical scenarios we agree are in scope.
  • A written report with steps to reproduce, business impact, severity, and remediation guidance.
  • A readout after delivery to walk through findings and answer questions.
  • Retest terms set in the statement of work.

Frequently asked questions

Short answers to common questions about scoping a social engineering test.

Do employees know about the test?

A few named contacts at your organization know about the test, agreed in scope. They can answer questions during testing, pause the test if needed, and be reached if we confirm a critical-severity issue. Keeping the group small lets the results show how people respond day to day.

We test only with written authorization and an agreed scope that sets out the scenarios, targets, exclusions, and timing. For physical scenarios, that authorization has to come from whoever controls each location, such as the building owner or landlord as well as the tenant. Many organizations have their own legal or HR advisors review the scope before testing begins.

What happens to credentials people submit?

How submitted credentials are handled is agreed in scope before testing begins. For example, the test can record that a submission happened without keeping the password.

Will people be named in the report?

Results focus on processes, controls, and patterns rather than individuals. How individual results are handled, and who can see them, is agreed with your organization in scope.

Is a social engineering test the same as the phishing simulations we already run?

No. Automated phishing platforms send recurring simulated messages and track rates over time, which is useful for training. A social engineering test is a time-boxed, authorized engagement with agreed scenarios, rules of engagement, and a written report on how people and processes responded. Many teams use both: the platform for ongoing practice, and a test when they want an independent look at a defined set of scenarios. A social engineering test is not a compliance certification.

Is an email-only social engineering test enough if we already run a phishing platform?

An email-only social engineering test and a phishing platform can both be useful for the named email group agreed in scope. Phone verification at a help desk, and physical access checks at named sites, are not deliberately covered without those channels, named targets or groups, and written authorization in the statement of work. Opt-outs, how any submitted credentials are handled, and stop conditions are agreed before testing begins. If authorized access is obtained during testing, further work follows the agreed rules of engagement. A social engineering test is not a compliance certification. It shows what was found inside the agreed scope and window. Retest terms set in the statement of work.

How often should we test?

It depends on your organization's risk and goals, and on changes such as new staff, new procedures, or recent training. We can help you align a testing schedule with those goals during scoping.

Is a social engineering test a compliance certification?

No. A social engineering test is not a compliance certification. It shows how your people and processes responded to the scenarios that were agreed, and it can be one input to a broader security program.

What methodology does a social engineering test follow?

A social engineering test typically follows scoping and written authorization, reconnaissance limited to agreed sources, pretext and campaign design, execution across the email, phone, or physical channels in scope, handling of any credentials or access obtained under the rules of engagement, reporting, and a retest. Pretexts are approved in advance. Results focus on processes and patterns rather than individuals. Authorized testing only happens inside the written scope. Retest terms set in the statement of work.

Nighttime satellite view of the United States, showing city lights from coast to coast

Scope a social engineering test

Tell us what you want to test and we will follow up with next steps.