Purple Teaming & Detection Exercises
Detection and response training alongside the attack side
Find the detections you have been missing, in front of real attack techniques, and fix them on the spot.
Your monitoring, detection and response staff and the attack side look at the same records at the same time, reproducing and checking one technique after another.
When a real attack comes, do our detection and our people catch it and respond?
For each technique: whether it was caught, what was fixed, and where gaps remain.
Expert reviewed
When it fits
- Your team needs to face real attacks
Your monitoring and response staff see first-hand what real attack techniques look like on screen, and practise what to check, and whom to pass it to, when an alert comes in.
- Detection has been built or changed
If you have brought in new detection rules, security tools or a new monitoring set-up, find out by training with your staff whether they catch real techniques.
- Red teaming has shown gaps
Objective-Based Penetration Testing & Red Teaming showed gaps in detection; we check and close them again, technique by technique.
- The monthly report always says ‘nothing to report’
You want to know whether a monthly ‘nothing to report’ really means all is well, by checking technique by technique what you catch and what you do not yet.
The SAFE SQUARE approach
Missed detections, fixed there and then
Straight after a technique is reproduced we look at the defence side's records together; where something was missed, rules and settings are changed and the same technique is run again.
Finding the cause together
The attack and defence sides look at the same records and work out together why something was missed: a session where both sides learn.
Techniques that matter to you first
The techniques to train on are chosen from evidence relevant to your organisation, such as threat intelligence and red team or exposure intelligence results.
What we look at together
For each technique the attack side reproduces, we look together at what the defence side saw and what it missed.
- Detection rules and alerts
Whether an alert fires for each technique, and whether its threshold is right.
- Logs and records
Whether the records needed for detection and investigation are kept, with no gaps in what is collected.
- Security tool settings
Whether tools such as endpoint detection and response (EDR), network detection and response (NDR) and the log platform (SIEM) are set up as intended.
- Alert quality
Misses and false alarms, and places where too many alerts bury the ones that matter.
- The first step of response
The person who receives an alert practises what to check and whom to pass it to.
Scenario exercises (tabletops), in which leadership and the response team walk through who does what in a situation such as a ransomware infection, run in the same format. Held alongside the technical exercise, they rehearse the whole flow from detection to reporting and decisions.
How it runs
Agree techniques and scope
We agree the techniques to train on, the target systems, who takes part and the safety conditions.
Prepare together
With the defence team we check logs, alerts and detection tools, and agree how things will be recorded.
Reproduce and check
The attack side reproduces a technique in a controlled way; the defence side checks detection, alerts and records on the spot and takes the first response steps.
Tune and check again
Where something is missed, we adjust detection rules, alert thresholds and protections together, and run the same technique again.
Write it up
Results by technique, what was changed, and the gaps and next steps that remain.
Techniques reproduced on live systems are prepared to leave traces without doing harm, and their scope is set first. The principles every engagement follows, safe conduct and stop conditions, facts kept apart from assumptions, and how material is kept and destroyed, are set out under How we work.
What you receive
Detection by technique
Detected, partly detected or missed, for each technique checked.
Rules and settings changed
What was changed during the exercise, and why.
Remaining gaps and priorities
What still cannot be detected, and what to address first.
Techniques and criteria to check again
Techniques and criteria to check again after changes, so the next exercise compares on the same scale.
Four techniques with the monitoring and response staff
In scope: office PCs and servers, EDR and SIEM, five monitoring and response staff
| Technique | Result | Record |
|---|---|---|
| A new admin account is created | Detected | An alert fired within two minutes, and the analyst checked straight away who had created it. |
| A scheduled task is registered on a server | Partly | It was logged but nothing raised an alert. An alert was added during the exercise, and the re-run was detected. |
| Passwords pulled from memory | Missed | Detection for that behaviour was switched off in the EDR policy. With it switched on, the same technique was detected on the re-run. |
| Bulk file compression and transfer out | Missed | Network device logs were not being collected, so the defence side could not see it. |
- What changed
- One alert rule was added and one EDR policy switched on. Both techniques were detected when re-run the same way after the fixes.
- Gap that remains
- Until network device logs are collected, bulk transfers out cannot be seen. Once collection is extended, the next exercise checks it again.