Purple team & adversary emulation playbook
Plan tabletop exercises and adversary emulation: pair ATT&CK v20.0 techniques with D3FEND 1.6.0, map against detections, and identify coverage gaps systematically.
What purple teams get from this view
Purple-team work sits between offense and defense. You need a shared map of adversary behavior (ATT&CK v20.0), what you can detect (telemetry and analytics), and what you can prevent (mitigations and D3FEND 1.6.0 countermeasures).
ATT&CK Intelligence View supports that conversation in one session: filter a technique set, open each technique's Detections and D3FEND 1.6.0 tabs, compare against your detection inventory, and export evidence for workshops.
Adversary emulation planning workflow
- Define the adversary profile — Filter by Threat Actor for the group or affiliate you are emulating. Add Platform and Tactic filters so the technique set matches your environment and exercise objectives.
- Build the technique scope — Use Filtered only mode for a clean exercise list. Export JSON to save the scope or Excel for facilitators with Detections, Mitigations, and D3FEND 1.6.0 sheets.
- Pair offense with defense — For each priority technique, review Detections (what blue should see) and D3FEND 1.6.0 + Mitigations (what should be harder for red). Note gaps where D3FEND 1.6.0 has no mapping.
- Map against actual detections — During planning, upload your documented rule list via Compare TIDs with Current Filter against actor-scoped filters. After BAS or emulation, use Compare Two TID Sheets (coverage catalog vs executed TIDs) to prioritize post-exercise backlog items.
- Run the tabletop or emulation — Walk tactic columns left to right. For each technique ask: Can red simulate it safely? Can blue detect it with current logs? Can architecture prevent it?
- Capture outcomes — Export PNG with comparison highlights for slides. View report or Export → Framework Gap PDF / Two-Sheet Comparison PDF for backlog grooming. Share JSON layer so the team reopens the same scope next quarter.
Tabletop exercise structure
- Opening — scope the adversary — Show filtered matrix PNG. Confirm actor, platform, and tactics in scope. Align red and blue on rules of engagement.
- Technique walk — offense — Red describes how each technique would be executed. Blue notes expected telemetry from the Detections tab.
- Technique walk — defense — Blue states current detections and gaps. Open D3FEND 1.6.0 for preventive controls. Discuss mitigations for short-term vs long-term fixes.
- Gap review — coverage — Present TID comparison results using the four categories: In file & current view, In file only (yellow), In view only (blue), and Invalid IDs. Prioritize In view only (blue) backlog items.
- Close — export and owners — Assign owners for detection, logging, and hardening gaps. Export Excel for tracking.
Using D3FEND 1.6.0 in purple-team sessions
The D3FEND 1.6.0 tab answers: If red succeeds at this ATT&CK v20.0 technique, which defensive techniques does MITRE associate with countering or detecting it?
Combine D3FEND 1.6.0 with the D3FEND 1.6.0 artifact filter when you want to group exercises by artifact class (process, file, account, network connection) for architecture-heavy table tops.
Example — Credential access emulation — Filter Tactic = Credential Access and Platform = Windows. Export technique set. For T1003 and related techniques, the red team plans LSASS-style paths while the blue team reviews Detections telemetry and D3FEND 1.6.0 countermeasures for credential stores. After the exercise, use Compare Two TID Sheets: Sheet 1 = documented credential-access use cases, Sheet 2 = BAS executed credential TIDs. Yellow (only in Sheet 2) = emulated paths missing from your framework; blue (only in Sheet 1) = documented rules BAS never exercised.
Systematic coverage gap identification
| Gap type | How to find it | What to do next |
|---|---|---|
| Detection gap (no rule) | Technique in exercise scope; In view only (blue) has no matching TID in comparison file | Detection engineering backlog from Detections tab analytics |
| Telemetry gap (no logs) | Detections tab shows data sources you do not ingest | Logging or sensor project before rule design |
| Scope mismatch | In file only (yellow) — rule exists but outside the current view | Clarify parent vs sub-technique mapping or adjust filter scope |
| Prevention gap | Mitigations or D3FEND 1.6.0 weak or missing for priority technique | Architecture or hardening sprint from D3FEND 1.6.0 tab |
| Untested technique | In view only (blue) — in scope but not in detection inventory | Add to next emulation cycle or purple-team test plan |
Exports purple teams use most
- JSON intelligence layer — reopen the same actor-scoped view for quarterly exercises.
- Excel workbook — facilitators get Techniques, Detections, Mitigations, and D3FEND 1.6.0 in one file.
- A4 PNG matrix — slide-ready visual for tabletop openings.
- Framework Gap PDF (A4) or Excel comparison report — Matched TIDs, Missing TIDs, and In View Not In File sheets for coverage evidence.
- Two-Sheet Comparison PDF (A4) — BAS executed vs documented coverage after emulation.
- PNG with Comparison — workshop slides showing red, yellow, and blue gap highlights.