Test whether an organisation can detect and respond to a realistic attack: adversary emulation, purple teaming, breach and attack simulation, and control validation, all under strict authorisation.
Estimated time: 13–26 months · At about 10 hours a week.
Offensive skills are for authorised testing only: your own lab, a practice platform, or a system whose owner has given you written permission. Testing anything else is a crime in most countries.
Learning path
Click a topic to see what to learn and where. Mark topics as you go; your progress is saved in this browser only.
Explain red teaming and its place among testing types.
Use MITRE ATT&CK fluently.
Set up a detection lab.
Explain the authorisation red teaming requires.
Hands-on projects and labs
Build a detection lab with logging and a SIEM.
Map a public threat report's behaviour to ATT&CK techniques.
Done when you can…
Explain the difference between pentesting, red teaming and BAS.
Map adversary behaviour to ATT&CK.
Beginner
What red teaming is
Objective-based, threat-realistic testing of detection and response, not a vulnerability hunt. Learn how it differs from penetration testing and when each fits.
Red teaming needs explicit, senior authorisation, a legal agreement, clear objectives and strict rules, including who knows and how to stand down. This comes first.
Run techniques openly with defenders watching, fixing detections as you go. It improves security faster than a closed red team and is often the better choice.
Regulated frameworks such as TIBER-EU and CBEST run intelligence-led red teams against live financial systems under strict governance. Learn how they work.
Report what defenders detected, how fast they responded, and which controls and detections to improve, with ATT&CK coverage. Outcomes, not war stories.
Red teaming goes beyond finding vulnerabilities: it tests whether an organisation can detect, respond to and recover from a realistic attack. An authorised team emulates the techniques of a chosen threat actor, under tight rules, to exercise the defenders and the controls.
This roadmap is a learning path for authorised, objective-based testing and, increasingly, for purple teaming, where offence and defence work together to improve detection. It centres on MITRE ATT&CK, emulation planning and measuring defensive outcomes. Every engagement needs written authorisation and a clear objective agreed with leadership.
Why it matters
Organisations that pass vulnerability scans still fall to real attacks because detection and response fail. Red and purple teams measure and improve that, and the demand for people who can run them constructively, not just break in, is high.
Typical job roles
Mid-levelRed team operatorExecutes emulation under a lead.
SeniorRed team leadPlans and runs engagements.
Mid-levelPurple team engineerRuns emulation with defenders to improve detection.
LeadAdversary emulation leadOwns the programme and threat alignment.
Prerequisites
Solid penetration testing and identity attack skills.
Strong understanding of detection and defensive operations.
Deep knowledge of MITRE ATT&CK.
Mature judgement and the law and ethics of authorised testing.