Skip to main content

Red Teaming - Adversarial Security Testing

About 2 min read

A red team is a specialized team that examines an organization's security posture from an attacker's perspective. It combines the methods that real attackers use - social engineering, physical intrusion, and technical exploits - to test in a realistic manner how far the organization's defenses actually hold up. The concept originates in military exercises.

The Difference from Penetration Testing

Red team exercises are sometimes confused with penetration testing, but they differ in objective, scope, and duration.

AspectPenetration TestingRed Team Exercise
ObjectiveFinding technical vulnerabilitiesEvaluating the defensive capability of the entire organization
ScopeSpecific systems or networksThe entire organization (people, processes, technology)
DurationRelatively shortRelatively long
MethodsMainly technical testingAlso includes social engineering and physical intrusion
Defenders' awarenessMay be notified in advanceOnly a limited group of people is aware
DeliverablesA list of vulnerabilities and remediation proposalsAttack scenarios and organizational improvement proposals

The Relationship Between Red, Blue, and Purple Teams

Red Team (Offense)

Imitates attackers and exploits gaps in the defenses. Achieving the objective without being detected is the criterion for success.

Blue Team (Defense)

The SOC and incident response teams fall into this category. They are responsible for detecting, containing, and recovering from attacks.

Purple Team (Collaboration)

A collaborative approach in which the red and blue teams share their insights to continuously improve defensive capabilities.

Leveraging the MITRE ATT&CK Framework

Red team exercises may use the MITRE ATT&CK framework as a common language. ATT&CK systematizes the tactics and techniques that real attackers use, and red teams can design attack scenarios from the ATT&CK matrix when formulating their exercise plans. By also using ATT&CK IDs in post-exercise reports, the blue team can identify, technique by technique, where its detection capability falls short. By combining it with threat intelligence, it becomes possible to run exercises focused on the techniques that the attack groups targeting your organization actually use.

An Example Flow of a Red Team Exercise

Define scope and establish rulesReconnaissance via OSINTAttempting initial accessLateral movement inside the networkAchieving the objective (data exfiltration, etc.)Reporting and improvement proposals

Before the exercise begins, the "Rules of Engagement" are defined. Systems out of scope, the range of permitted attack methods, emergency contacts, and so on are documented and approved by management. Omitting this step risks the exercise being mistaken for an actual incident or causing unintended disruptions to business systems.

Cost and Complementary Measures

The cost of a red team exercise varies with its scope, duration, and methods. Between exercises, it can be supplemented with penetration testing and vulnerability scanning.

Examples of Misconceptions

The notion that "if a red team exercise fails to break in, you are safe" is dangerous. Because the exercise is conducted within a limited time and budget, a failure to break in merely means that "we could not break in with those methods." Real attackers are not bound by the duration or scope of an exercise.

A red team exercise can be positioned as part of a comprehensive security program combined with insider threat countermeasures and a security checklist. It can also serve as a means of verifying the effectiveness of a corporate password policy.

Was this article helpful?

Related Terms