Skip to content

Offensive · Red & Purple Team

Find out whether your defenses hold against a real attack.

A red team pursues a business objective with the tradecraft of a real adversary. A purple team runs the same techniques with your SOC in the room, so every gap becomes a working detection.

Typical length
4–8 weeks
Method
MITRE ATT&CK, threat-led objectives (TIBER-EU-style)
Formats
Red, purple or assumed breach

Simulated environment, real workflow.

Scope

What we cover.

Pick what matters for this engagement. We help you scope it in the first call.

Objective-based red team

A goal such as reaching payment data or the CEO's mailbox, pursued covertly end to end.

Purple team exercises

Techniques run openly with your analysts, tuned until each one is detected.

Assumed breach

Start from a compromised laptop or account to test internal detection and response.

Social engineering

Phishing, vishing and pretexting campaigns against agreed groups.

Physical intrusion

Badge cloning, tailgating and on-site device drops, where in scope.

Threat-led scenarios

Campaigns modeled on groups that target your sector.

Methodology

How the engagement runs.

  1. 01

    Threat model

    Pick the adversaries and objectives that matter to your business.

    Output: Threat profile

  2. 02

    Plan

    Agree rules of engagement, a control group that knows, and safe stop conditions.

    Output: Rules of engagement

  3. 03

    Operate

    Run the campaign, logging every action with timestamps for later replay.

    Output: Action log

  4. 04

    Replay

    Walk your SOC through the timeline to see what fired, what was missed and why.

    Output: Detection-gap timeline

  5. 05

    Harden

    Build and test new detections together until the gaps close.

    Output: New detections

One path to the crown jewels, then closed.

We chain small weaknesses into the route a real adversary would take, then prove the fix breaks the chain.

Attack path to the customer databaseFive hops from one phishing email; the other assets were reachable but not on the path.
  • Attack path
  • Reachable, not exploited
Attack path to the customer database (Simulated environment, real workflow.)
StepAssetWhat happened
1Phishing emailMacro-enabled invoice opened
2WorkstationPayload runs as the user
3Cached admin credsAdmin token in browser storage
4Domain controllerToken reused for directory admin
5Customer DBTarget: 1.2M customer records

Simulated environment, real workflow.

Findings

Where the chain was weakest.

Every finding is tied to the stage of the attack it enabled, so you fix the links that broke the chain first, not the longest list.

Red-team findings by severity, per attack stageFindings from one objective-based engagement, grouped by the stage of the attack chain they enabled.
  • Critical
  • High
  • Medium
  • Low
0
2
4
6
8
8
6
5
8
3
AccessExecutionEscalationLateralObjective
Red-team findings by severity, per attack stage (Simulated environment, real workflow.)
GroupCriticalHighMediumLowTotal
Access12328
Execution03216
Escalation21205
Lateral12328
Objective11013

Simulated environment, real workflow.

Deliverables

What you walk away with.

Written for the engineers who fix things and the leaders who fund them.

  • Named lead for the whole engagement
  • Critical issues flagged the same day
  • Retest included
How we work
01

Attack narrative

The full campaign as a timeline, with each step mapped to ATT&CK.

02

Detection gap matrix

Which techniques were prevented, detected, logged only or missed.

03

Detection content

Rules and queries built in the purple-team phase, ready for your SIEM.

04

Detections delivered

Every missed technique handed to your SOC, or ours, as a tested detection and a threat-hunting lead.

FAQ

Questions we hear most.

What is the difference between red and purple teaming?

Red teaming is covert and tests your response end to end. Purple teaming is collaborative and builds detections as you go. Many clients run red first, then purple.

Who in our company needs to know?

A small control group, usually the CISO and one or two others, who can stop the exercise and tell real incidents apart.

How do you keep it safe?

Written rules of engagement, no destructive actions, and agreed stop conditions. Every action is logged.

Can our managed SOC take part?

Yes. If our SOC monitors you, the exercise also tests that service, and we report on it openly.

Scope your Red & Purple Team engagement.

A 30-minute call with a senior practitioner. You leave with a scope, a timeline and a fixed quote.