Skip to content

Social Engineering

Phishing & Social
Engineering Testing

Starts at $3,600, fixed scope. See all pricing →

Get a fixed quote

Reply in one business day

Senior certified testers, manual-first185+ years combined experienceOnboarding within 24 hoursOur methodology

When you need it

When you need phishing simulation & social engineering testing

The situations that bring teams to this engagement, and where it fits alongside the rest of your program.

  • Your SOC 2, PCI DSS (Requirement 12.6), or HIPAA program needs evidence that security awareness is measured, not just delivered.
  • A cyber-insurance questionnaire asks whether you run phishing simulations and how your click rate is trending.
  • Someone clicked. A real phishing incident happened and leadership wants to know how exposed the rest of the organization is.
  • You onboarded a wave of new hires, opened a new office, or completed an acquisition, and the awareness baseline has changed.
  • You are planning a red team assessment and want the human layer measured first, since it is usually the initial access path.

Definition

What is social engineering penetration testing?

Social engineering penetration testing measures whether your people can be talked into giving an attacker access. It goes beyond a single phishing email to voice (vishing), SMS (smishing), and pretexting, and reports who clicked, who submitted credentials, and who raised the alarm.

Phishing simulation

Channels
Email lures
Goal
Baseline the click and report rate
Result
Metrics by department
Starts at
$3,600

Social engineering test

Channels
Email, voice, SMS, and pretexting
Goal
Measure human risk across every social channel
Result
Metrics plus a tested reporting workflow
Starts at
$3,600, scoped by channels

Red team

Channels
Whatever reaches the objective, including physical entry
Goal
Reach an agreed objective and test detection
Result
An attack narrative and a detection timeline
Starts at
$12,500

When the human layer is one leg of a covert, full-chain operation toward an agreed objective, the engagement is a red team.

What we look for

Social engineering assessment: email, voice, SMS, and pretexting

Your strongest technical controls can be bypassed by one convincing message. We measure how your workforce responds to realistic social engineering across email, voice, and SMS.

Email Phishing

Realistic lures that measure who clicks, who submits credentials, and who reports.

We test for

  • Pretext and lure design
  • Credential-harvesting pages
  • Attachment and link payloads
  • Departmental targeting

Vishing & Smishing

Voice and SMS pretexting that tests staff away from the inbox.

We test for

  • Phone pretexting scenarios
  • SMS lure campaigns
  • Help-desk and reset abuse
  • MFA fatigue and prompt bombing

Awareness & Reporting

How well people recognize, resist, and report an attack in progress.

We test for

  • Report-rate measurement
  • Repeat-clicker analysis
  • Time-to-report tracking
  • Reporting workflow review

Technical Controls

Whether your email defenses stop the message before it lands.

We test for

  • SPF, DKIM, and DMARC review
  • Gateway and filter bypass
  • Spoofing and lookalike domains
  • Link and attachment handling

Pretexting, Physical & MFA Bypass

The scenarios that go beyond a link in an email: a convincing story, a person at the door, or a login page that steals the session after MFA.

We test for

  • Help-desk and password-reset pretexting
  • Adversary-in-the-middle phishing that defeats MFA (Evilginx-style)
  • OSINT-driven executive and finance impersonation
  • Physical pretexting and tailgating, scoped as a physical penetration test or as part of a red team
  • Removable-media and QR-code lures

Metrics

What we measure

A campaign is only useful if the numbers mean something. Every result is broken down by department and role, and benchmarked against your previous campaigns when you have them.

What it tells you

Open rate
How convincing the pretext and sender were, and whether your gateway let the message land at all.
Click rate
The share of recipients who followed the link or opened the attachment. The headline exposure number.
Submission rate
Who entered credentials or approved an MFA prompt on the capture page. The number that maps directly to account takeover.
Report rate
Who used your reporting button or process. High report rates offset high click rates; low report rates mean an attack runs unopposed.
Time to first report
How long a real attack would have run before anyone raised the alarm. In one of our campaigns most interaction happened within the first hours.
Repeat-offender analysis
Who clicked across multiple campaigns, so training is targeted rather than sent to everyone again.

Design

How campaigns are designed

Generic phishing templates measure how well people spot generic phishing. Real attackers research first, so we do too: public job postings, vendor relationships, executive names, seasonal events, and the tools your staff use every day all shape the pretext. The campaign in our higher-education case study used a seasonal pretext and a look-alike single-sign-on domain, and captured credentials from senior staff for exactly that reason.

Every campaign runs under written rules of engagement agreed with you: who is in scope, what the capture page does with anything entered, how long the campaign runs, and who inside your organization knows. Captured credentials are never stored in plaintext, results are reported by department rather than by name unless you ask otherwise, and the objective is measurement and improvement, not blame.

After the campaign

From results to training

  • A debrief with the security team and, where useful, department leads, walking through what worked and why.
  • Targeted awareness recommendations by role: finance and executive assistants for invoice and wire fraud, IT for help-desk pretexting, everyone for credential lures.
  • Reporting workflow review: whether staff can report in one click and whether someone acts on the report quickly.
  • A recommended cadence, typically quarterly or twice yearly, with each campaign benchmarked against the last.
  • Technical follow-ups where the campaign exposed them: email authentication gaps, look-alike domain monitoring, and phishing-resistant MFA.

Methodology

How we test

Full methodology →

Every engagement follows the Penetration Testing Execution Standard and the relevant OWASP guides.

These are the phases your phishing simulation & social engineering testing runs through.

  1. 01

    OSINT & pretext design

    Public footprint researched and scenarios built around how your organization really works.

  2. 02

    Campaign build

    Lures, domains, capture pages, and safety controls prepared and approved with you.

  3. 03

    Delivery

    Email, voice, or SMS campaigns run discreetly under agreed rules of engagement.

  4. 04

    Measurement

    Opens, clicks, submissions, reports, and time-to-report captured by department.

  5. 05

    Debrief & training plan

    Results turned into targeted awareness recommendations and a repeat cadence.

How it works

How your engagement runs

From scope through the final report, your team stays in the loop at every step, with findings tracked live in our platform.

  1. 01

    Scope & kickoff

    Targets, roles, and rules of engagement defined in writing, with a fixed scope and timeline.

  2. 02

    Testing goes live

    Findings post to your live platform dashboard the moment our testers confirm them.

  3. 03

    Track remediation

    Follow every finding from open to fixed, with severity, evidence, and status in one place.

  4. 04

    Report & debrief

    Executive and technical reports land, with clear results and a prioritized remediation plan.

Proof

Proof in the field

Every engagement is confidential, so the work below is anonymized to sector and engagement type.

All case studies →

12,000+

Employees phishing-tested

53%

Phish-prone in one healthcare campaign

2-channel

Email plus voice campaigns run

Fixed

Scope and price, no hourly billing

Healthcare · Imaging

Organization-Wide Phishing Simulation

High risk

Over half the workforce took the bait: roughly a third clicked the link and a quarter entered their credentials on the simulated capture page.

Outcome. Quantified credential-compromise risk across the whole organization and delivered a prioritized program of role-targeted awareness training, recurring simulations, and a faster, simpler reporting workflow.

11,800+

Employees targeted

53%

Phish-prone

24%

Entered credentials

Read the case study

Higher Education

Credential-Harvesting Phishing

Using a seasonal pretext, an SSO look-alike domain, and abuse of a legitimate mail-platform send feature, the campaign reached inboxes and captured SSO credentials.

Outcome. Demonstrated a credible path to SSO account takeover and drove improvements to email authentication, look-alike domain monitoring, password policy, and targeted training.

100+

Staff targeted

20%

Credentials captured

Exec

Accounts affected

Read the case study

FAQ

Frequently asked questions

What teams most often ask before scoping phishing simulation & social engineering testing.

Still have questions? 
01What is a phishing simulation?

A phishing simulation, sometimes called an employee phishing test, is a controlled campaign that sends realistic but harmless phishing emails to your workforce to measure who clicks, who submits credentials, and who reports the attempt. Every click is captured safely and turned into metrics you can act on. It is the fastest way to baseline your human attack surface and to satisfy the security awareness expectations in frameworks like SOC 2 and ISO 27001.

02What is a social engineering penetration test?

A social engineering penetration test is a controlled attack on your people rather than your systems. Testers research your organization, then run email phishing and, where scoped, voice and SMS campaigns and pretexting, to see who can be persuaded to click, hand over a credential, or approve an MFA prompt. The report breaks the results down by department and turns them into targeted awareness recommendations. When a framework or customer asks for social engineering testing services, this is the engagement that answers it.

03What does phishing testing measure?

It measures how your workforce responds to realistic social engineering, including who clicks, who submits credentials, and who reports the attempt, then turns those results into targeted awareness improvements.

04Do you offer more than email phishing?

Yes. Alongside email campaigns we can run voice (vishing) and SMS (smishing) scenarios for a fuller picture of your social engineering risk.

05Will employees know it is a test?

No. Campaigns are run discreetly so results reflect real behavior, with your authorization and clear rules of engagement agreed in advance. The goal is measurement and improvement, not blame.

06How many employees can a campaign cover?

A standard campaign covers your full workforce or a defined set of departments; we size the lures and reporting to your headcount. Very large or multi-region organizations are scoped so results stay meaningful by team rather than a single blended number.

07How often should we run phishing tests?

Most organizations run phishing testing quarterly or twice a year so awareness stays current and you can measure improvement over time. A single baseline campaign is a good starting point, and many teams then move to a recurring cadence.

08How much does phishing testing cost?

A phishing campaign starts at $3,600, fixed before work begins. It is often the easiest first engagement and a natural lead-in to internal network testing or a full red team. Starting prices for every service are on our pricing page.

09Can you phish accounts that are protected by MFA?

Yes. Attackers do, so the test should too. Adversary-in-the-middle phishing kits proxy the real login page, relay the MFA prompt, and capture the authenticated session, which defeats SMS codes and push approvals. We run the same technique in a controlled way, which shows whether your MFA method actually resists phishing and whether your conditional access and session controls catch the stolen session. Our Evilginx explainer describes how the technique works.

10Do you provide the awareness training afterward?

We provide the results, the analysis, and a targeted training plan: which departments and roles need attention, which pretexts worked, and what the reporting workflow should look like. Many clients run the training through their existing platform and use our follow-up campaigns to measure whether it worked. Where you do not have a platform, we advise on options during the debrief.

11How should we compare phishing simulation vendors?

Ask four things. Who designs the pretexts: a template library, or people who research your organization first? Can they run adversary-in-the-middle phishing that defeats MFA, since that is what real attackers use now? Are results reported by department with time-to-first-report, or as a single click rate? And is the price fixed before the campaign starts? Ours is $3,600 for a scoped campaign, and the case study on our case studies page shows what a campaign across a large healthcare workforce produced. One more distinction: managed campaigns, where we design and run the operation and interpret the results, versus self-serve phishing simulation software your team operates. We run managed campaigns, so the pretexts are researched and the results come back with analysis rather than a raw dashboard.

Ready to test your defenses?

Talk to our team about scoping phishing simulation & social engineering testing.

Prefer the full scoping questionnaire? 

Get a Fixed-Scope Quote

Tell us what you need tested. We reply within one business day.