Purple Team
One Team.
Sharper Defenses.
Red Siege operators run real attacker techniques alongside your defenders, so your team learns what it detects, how it responds, and where to improve.
The Goal Isn’t to Stop Everything
A purple team isn’t a contest your defenders win by blocking every attack. It’s a working session between offense and defense. Red Siege runs real-world attacker techniques, your team checks what it saw, and together we find the gaps: the alert that never fired, the detection that only works on some systems, the response that stalls. Your team tunes, we run it again. You finish with detections you’ve proven, not assumed.
Real Attacker Techniques
A suite of real attacker techniques, such as Kerberoasting and AD CS abuse, built with input from your defenders.
Shot Validation
As we run each technique, your team checks detections and protections, tunes them, and we test again.
Detection Measured by ACE
Detections judged on Automation, Coverage, and Effectiveness: how fast they fire, how far they reach, how accurate they are.
Proof of Progress
Results documented to show gains in detection and response, and to justify investment in tools and training.
Our Approach
How We Run a Purple Team
Every engagement is built around your defenders, their tools, and how involved they want to be.
-
Start with what would hurt
We ask which data or process would hurt most if it were lost, stolen, compromised, or destroyed, and which attacks your defenders most want to test. We also check the basics: central logging, endpoint event logs, and alerting. Without them, a purple team has little to teach.
-
Choose how involved you’ll be
With no in-house red team, Red Siege plays the attacker, either working with your defenders daily or holding a full debrief until the end for more advanced teams. With an in-house red team, we facilitate instead, helping design scenarios and build communication between your teams.
-
Run it, check it, tune it
We run each technique in the suite while your team watches for it. If an alert stays quiet, fires too late, or drowns in noise, your team tunes the detection and we run it again. Sometimes we raise the noise level until you see us, then work from there.
-
Document and measure progress
We document every action so your team can trace the evidence, and rate each detection on Automation, Coverage, and Effectiveness. Findings come with short- and long-term fixes and a validation section to confirm each one. Next time, we measure you against yourself.
A Miss Is Where Learning Starts
A blocked attack tells you one control worked once. A missed one tells you exactly what to fix: which log you aren’t collecting, which alert needs tuning, which step in the runbook slows your responders down. The point isn’t a clean scorecard. It’s finding out what your defenses can detect, how your team responds, and where to improve, while the operator who ran the attack is still on hand to help,
because real attackers don’t offer a rematch.
Get Offensive Now
“Red and Blue aren’t opposing swords; they are a sword and a whetstone.”
Details on Purple Team
Tim Medin’s “On Purple” lays out the three ways an outside firm can run a purple team, the ACE model for measuring detection, the logging questions to answer before you start, and why offense and defense get the most out of each other when they stop acting like opponents.
Learn More