What is the difference?

DisciplineObjectiveStealthWho takes partTypical output
Penetration testFind exploitable weaknesses in a defined scopeNot requiredTester, system ownerFindings with severity and fixes
Red teamTest whether a realistic adversary reaches a goal, and whether defenders noticeHighRed team, a small control groupAttack narrative and detection gaps
Blue teamPrevent, detect and respondNot applicableSOC, incident responseMonitoring, rules, playbooks
Purple teamTest and tune detection and response with both sides presentNone; actions are shared as they happenAttacker side and the client’s defendersTuned detections, updated playbooks, a gap report

Is purple better than a pen test?

No, because the output differs. A penetration test answers whether something can be broken into. A purple team exercise answers whether you would see it, and what you would change so that you do. Mandiant’s datasheet draws the same line: a purple team does not assume that security operations work as intended, unlike a penetration test that looks for misconfigurations and unpatched systems.

When choose a pen test instead?

When you have not yet scoped or fixed the weaknesses an attacker would use first, or when a rule or contract asks for one. Fix what the test finds, then test detection.

Do I need red and blue first?

You need a defender who can change detections during the exercise. The Paranoid Security profile describes a specialist coordinating with a dedicated SOC employee of the client. Some providers describe separate red team and blue team services instead of a joint exercise, so confirm which one is on offer.

Where the lines blur

Providers use the words loosely. A red team engagement may assess SOC readiness at the end, which is not the same as working with defenders live. Ask who watches, who changes rules and when. The methodology page treats live joint execution as its own criterion for this reason.

For the basics, read what purple team cyber security is.