Skip to main content
CERT-In Empanelled Since 2008

Phishing Simulation and Social Engineering Testing

Phishing, spear phishing and vishing run by the red team that uses them in full adversary simulations. You learn who clicked, who reported it, and whether your controls and your SOC saw the campaign.

6,700+
Assessments
1,000+
Clients
150+
Team
2006
Founded

What a phishing simulation is

A phishing simulation is an authorised attack on your people. Testers send the messages and make the calls a real adversary would, under written rules, and record what happened at each step: delivered, opened, clicked, credentials entered, reported.

Social engineering testing is the wider discipline. It adds the telephone and, where you authorise it in writing, the front door. Both answer the same question: how far a stranger gets by asking.

Five exercises, scoped singly or together

Each has its own objective and its own measure. The scoping call settles which of them your question needs.

Email phishing simulation

Scenarios sent to a whole organisation or to chosen departments, from infrastructure stood up for the engagement. Link, attachment and credential-capture lures, graded from obvious to hard.

Spear phishing

Pretexts written for named roles from open-source reconnaissance: finance approvers, the IT help desk, executive assistants, new joiners. This is the form a targeted attacker uses.

Vishing

Telephone pretexts against the help desk and the switchboard: a password reset, a multi-factor re-enrolment, a supplier changing bank details. The measure is whether the caller was verified.

Physical social engineering

Tailgating, USB drops and badge cloning at named sites. Run only with explicit written authorisation and an escalation contact on call.

Detection and response measurement

What the mail gateway stopped, what the SOC raised, how long the first report took to arrive and how long containment took after it.

Which exercise answers your question

Start from what you need to know. The exercise follows from it.

You need a baseline before an awareness programme starts

An organisation-wide email simulation, repeated after the programme so that the two reporting rates can be compared.

Phishing simulation scoping template →

You want to know whether the help desk would reset a password for a caller

A vishing exercise against the reset and re-enrolment procedures, with the calls logged against the script.

Red team assessment →

Your identity estate is Microsoft 365

Device-code phishing and OAuth consent lures, tested as part of an identity attack-path assessment.

Microsoft 365 red team →

You want to know whether a real campaign would be detected

A red team assessment, where phishing is the initial access and the measure is your detection and response.

Red team assessment →

A Saudi regulator’s awareness control applies to you

NCA ECC control 1-10-3 names phishing emails, and SAMA’s framework asks for the awareness programme to be evaluated.

NCA ECC →

How an exercise runs

The order matters. Nothing is sent until the first step is signed.

  1. Authorisation

    A written scope: who is targeted, who is excluded, who knows, what is done with any credential captured, and whether results name individuals or stop at team level.

  2. Reconnaissance and pretext

    What an outsider can learn about your people, suppliers and systems, turned into scenarios that a real attacker could plausibly send.

  3. Infrastructure and delivery

    Sending domains, landing pages and call scripts built for the engagement. Whether the mail filter allow-lists them is decided by what you want to measure.

  4. Measurement

    Every stage is counted: delivered, opened, clicked, submitted, reported. Reporting rate and time to first report sit beside click rate.

  5. Report and debrief

    Findings pass three-level review (L1 → L2 → L3) and are walked through with the security team and the people who own awareness.

What you receive

Security Brigade was founded in 2006 and has 6,700+ assessments delivered for 1,000+ enterprise clients, with 150+ security professionals and offices in Mumbai, London, New York and Singapore.

  • An executive summary with the rates by department and role, written to be read by a board or an audit committee.
  • The scenarios as sent: message, landing page, call script and the reconnaissance each was built from.
  • A control-by-control account of what the mail gateway, endpoint tooling and the SOC did.
  • Recommendations for the reporting channel, the verification procedures and the next exercise.

Phishing simulation, answered

Request a scoping call
What is the difference between a phishing simulation and awareness training? +
Training tells people what to look for. A simulation measures what they do when a convincing message arrives on an ordinary working day. The two belong together: the simulation gives the training its baseline and shows whether it worked.
Should the simulation emails be allow-listed in the mail filter? +
It depends on the question. Allow-listing measures your people on their own. Sending without it measures the whole chain: filter, user, reporting channel and SOC. Many organisations run one of each.
Will individual employees be named in the report? +
That is decided in scoping and written into the authorisation before anything is sent. Results can name individuals, stop at team level, or name only the roles that were targeted.
Do you test by telephone and in person as well as by email? +
Yes. Phishing and vishing are part of every red team engagement Security Brigade runs. Physical access testing, which covers tailgating, USB drops and badge cloning, runs only with explicit written authorisation.
Which click rate is a pass? +
No framework sets one, and click rate alone is the weaker measure. A scenario can be made easy or hard at will. Reporting rate and the time from first delivery to first report say more about whether an attack would be stopped.

Scope a phishing simulation

Tell us who is in scope and what you want to measure. We reply within one business day.