SOC 2 Readiness
24/7 Security Monitoring
Canadian-Based SOC
Back to Glossary
Assessment & Testing

What Is Red Team?

Definition

A red team is a group of security professionals who simulate real-world attacks against an organization to test its defenses. Unlike penetration testing, red team exercises assess the entire security posture including people, processes, and technology across an extended engagement.

People Also Ask

Common questions about Red Team answered by our security experts.

Red Team in Practice

A red team engagement asks a different question from a penetration test, and buying the wrong one is an expensive way to learn that. A penetration test asks what is vulnerable across a defined scope. A red team asks whether a determined adversary can reach a specific objective, and whether anyone would notice.

Coverage is the goal of one; realism is the goal of the other.

What makes an engagement a red teamA defined objective, stealth, uninformed defenders, organisation-wide scope and a narrative deliverable rather than a findings list.ObjectiveReach a defined goal, not enumerate weaknessesStealthCentral to the exercise, and the main cost driverDefenders uninformedOnly a small control group knowsWhole-organisation scopeTechnical, physical and socialOutput is a narrativeThe path taken and what was detected
Stealth is what multiplies the cost: moving slowly to avoid detection takes time.

Why most organisations should not buy one yet

A red team engagement against an organisation with known, unremediated basics produces a predictable report: they got in through the thing you already knew about, quickly, and nobody noticed. You paid a premium for information a penetration test would have produced at a fraction of the cost.

Readiness signals worth checking honestly:

  • Vulnerability management is operating and findings are actually remediated
  • Penetration tests are no longer producing critical findings routinely
  • You have monitoring you believe works, and people who would respond to it
  • Segmentation exists, so lateral movement is not trivial
  • There is a specific claim you want tested — a detection capability, a response process

Purple teaming is often the better purchase

Purple teaming runs the attack collaboratively: the attacker executes a technique, the defenders look for it, and both sides learn immediately whether it was visible. It sacrifices realism and gains enormously in learning rate.

For an organisation building detection capability, that feedback loop improves things faster than a report arriving weeks later. See penetration testing.


Rules of engagement to fix in advance

TermWhy it matters
Named control groupWho knows, and how they are reachable at any hour
Stand-down procedureSo the exercise can be halted if it affects operations
Out-of-bounds systemsParticularly anything touching safety
Social engineering limitsWhich pretexts are acceptable; whether staff are named
Deconfliction pathSo a defender can check whether activity is the exercise
Deconfliction is the one that gets forgotten
Without a way for defenders to check whether suspicious activity is the exercise, someone who spots the red team may escalate to law enforcement or trigger a genuine incident response. That is expensive and embarrassing for everyone.

Cost and duration, honestly

A red team engagement typically runs several times the cost of a penetration test of the same estate, and the driver is time rather than rate. Moving slowly enough to avoid detection, waiting for an opportunity and working through a long chain consumes weeks that a scoped test would not.

Penetration testRed team
DurationDays to weeksWeeks to months
ScopeDefined systemsOften the whole organisation
Success measureCoverage of the scopeObjective reached, and whether detected
DeliverableFindings with severitiesAn attack narrative and a detection assessment

The most valuable section of the report is not the path taken. It is the account of what the defenders saw at each step — where telemetry existed but no alert fired, and where an alert fired and was dismissed. Those are two different failures with two different fixes.


What to do with the result

A red team report is only worth its cost if it changes detection. Replay each technique with the defenders watching until it is reliably caught, write the missing detections, fix the response failures — an alert that fired and was dismissed is a process problem, not a tooling one — and re-run the same objective in six months to measure whether the path is now visible.

See red team versus penetration test for the full comparison, and penetration testing.

Need Help With Red Team?

Our certified security professionals can help you implement the right red team strategy for your organization. Get a free assessment today.

Book a Free Consultation