Security
Red Team vs Penetration Test: What's the Difference?
30 Aug 2026 · Updated 30 Aug 2026
A penetration test is scoped and time-boxed to find and validate vulnerabilities in defined systems. A red team exercise emulates a real adversary against the whole organisation to reach a goal, testing an organisation’s people and, above all, whether its defenders detect and respond. Purple teaming runs both sides together to improve detection. Start with penetration testing; move to red teaming once defences are mature enough to test.
These terms are often used interchangeably, and they should not be. A penetration test and a red team exercise answer different questions and suit organisations at different stages of maturity. Choosing the wrong one wastes money.
What is the difference between a penetration test and a red team exercise?
The difference is scope and objective. A penetration test is scoped and time-boxed: it aims to find and validate as many vulnerabilities as possible within a defined set of systems, answering the question “what vulnerabilities exist here, and can they be exploited?” A red team exercise is goal-oriented and organisation-wide: it pursues a realistic objective, such as reaching a specific set of critical data or a domain administrator account, using whatever means a real attacker would, and it answers a different question, “can an attacker reach our critical assets, and will we detect and stop them?”
That difference cascades into everything else. A penetration test is thorough within its scope but limited to that scope. A red team is narrow in objective but broad in the means it can use, people, process, physical and technical, and it treats stealth and evading detection as core aims rather than afterthoughts. Most importantly, a red team tests the defenders, whether the security team notices and responds, which a standard penetration test usually does not. In short, a penetration test tests an organisation’s systems, a red team tests the whole organisation.
What is a red team exercise?
NIST defines a red team exercise as an exercise, reflecting real-world conditions, conducted as a simulated adversarial attempt to compromise an organisation’s missions or business processes, providing a full assessment of the security capabilities of the organisation and its systems. The key words are simulated adversary and full assessment of capabilities, not a list of flaws.
In practice, a red team is given a goal and left to find its own route, the way a real attacker would. It may use social engineering to trick staff, attempt physical intrusion to reach a network, and chain technical exploits, and it commonly emulates the tactics, techniques and procedures of a specific real-world adversary. MITRE’s ATT&CK knowledge base and its adversary emulation plans are widely used for exactly this, giving red teams a structured way to model how a known adversary behaves. Because a red team operates with stealth, the exercise also tests the blue team, the defenders, revealing whether they detect the activity and how well they respond. This is why red teaming is considered a more advanced engagement than a penetration test: it assumes the obvious vulnerabilities have already been dealt with, and it goes after the harder question of detection and response.
What is purple teaming?
Purple teaming is the collaborative middle ground. Instead of the red team operating in stealth against an unaware blue team, the two work together in the same exercise: each attack technique the red team runs is paired with a check of whether the blue team detects it, and the detection rule or response is tuned on the spot.
The name captures the idea, red and blue working together produce purple. It is typically a full-knowledge engagement, the opposite of a red team’s stealth, because the point is not to test whether defenders get caught out but to improve their detection and response as fast as possible. MITRE ATT&CK is commonly used as the shared language, mapping each emulated technique to the detection it should trigger. Purple teaming is especially valuable for an organisation building up its detection capability, because it turns every simulated attack into a concrete improvement rather than just a pass or fail. Purple team, unlike red team, is not a term with a single canonical definition from a standards body. It is a widely used industry practice, but the collaborative red-plus-blue meaning is consistent across the field.
When is a red team needed versus a penetration test?
Match the engagement to security maturity. Use a penetration test to find and fix vulnerabilities in specific systems, when launching or changing an application, or when a compliance framework or client requires testing. This is the right choice for most organisations most of the time, and it is where the majority should focus.
Use a red team exercise when security is already mature, when the basics a penetration test would surface have been addressed, and to test the harder question of whether the organisation can detect and respond to a determined, realistic attacker across the whole organisation. Running a red team against an organisation that has not done the fundamentals is poor value: it will simply confirm that the organisation is easy to breach, which a cheaper penetration test would have shown. A red team earns its cost when there is a real detection and response capability worth testing. Purple teaming falls between the two and is a strong choice when the priority is building detection. The progression for most organisations is penetration testing first, then, as maturity grows, purple teaming and red teaming.
Which does an organisation need, a red team or a penetration test?
For most organisations, the answer is penetration testing first. It finds and fixes the vulnerabilities that a real attacker would exploit, it satisfies compliance and client requirements, and it is the foundation on which more advanced testing is built. Only once an organisation has actually addressed those findings and stood up a security monitoring and response capability does a red team exercise become worthwhile.
The useful test is to ask what the organisation would learn. If the answer is that it has exploitable vulnerabilities, it needs a penetration test. If the systems are already reasonably hardened and the real question is whether the team would catch and stop a real intrusion, it is ready for red teaming or purple teaming. Spending on a red team before the basics are in place is a common and expensive mistake. To work out which engagement fits a given maturity, or to commission either, we offer penetration testing and broader advisory.
Frequently asked questions
What is the difference between a penetration test and a red team exercise?
A penetration test is scoped and time-boxed to find and validate as many vulnerabilities as possible in defined systems, answering what vulnerabilities exist. A red team exercise is a goal-oriented adversary emulation with organisation-wide scope, pursuing a realistic objective such as reaching critical data, and it deliberately tests whether the organisation detects and responds. A penetration test tests systems, a red team tests the whole organisation including its people and defenders.
What is a red team exercise?
NIST defines a red team exercise as a simulated adversarial attempt to compromise an organisation’s missions or business processes, providing a full assessment of its security capabilities. Rather than listing vulnerabilities, a red team pursues a defined goal using whatever realistic means an attacker would, including social engineering and physical intrusion, often emulating a specific adversary’s tactics, and it operates with stealth to test detection and response.
What is purple teaming?
Purple teaming brings the red team attackers and the blue team defenders into the same exercise, collaborating in real time. Each simulated attack technique is paired with a check of whether the defenders detect it, and the detection or response is tuned on the spot. It is usually a full-knowledge engagement, unlike the stealth of a red team, and its goal is to improve detection and response quickly by working the two sides together.
When is a red team needed versus a penetration test?
Use a penetration test to find and fix vulnerabilities in specific systems, or to satisfy a compliance or client requirement. Use a red team exercise when security is already mature and the aim is to test whether the organisation can detect and respond to a realistic, determined attacker across the whole organisation. A red team is a more advanced engagement that assumes the basics a penetration test would find have already been addressed.
Which does an organisation need, a red team or a penetration test?
Most organisations should start with penetration testing to find and fix vulnerabilities, and only move to red teaming once their defences and detection capabilities are mature enough to be worth testing. Running a red team against an organisation that has not done the basics simply confirms it is easy to breach, which a penetration test would show more cheaply. Match the engagement to the organisation’s maturity.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Glossary: red team exercise (NIST SP 800-53 Rev. 5), NIST CSRC, 2020
- NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, National Institute of Standards and Technology, September 2008
- Adversary emulation and red teaming, MITRE ATT&CK, 2026
- MITRE ATT&CK, MITRE, 2026
Last updated: 30 August, 2026
