Section 20
Borrowed practices
| Source | Where it does work |
|---|---|
| Palantir Alerting and Detection Strategy Framework | ads.md section names per detection, plus a Retirement record section this framework adds, so a record has 11 sections |
| Sigma rule status field | stage marker on every rule file; the Sigma rule itself is the single source each query language is generated from |
| MITRE CTID Summiting the Pyramid | robustness input, 5 levels (anchor wording paraphrased) |
| MITRE ATT&CK | technique field in score.yml, validated by lint, which also accepts ATLAS ids; tactic derived by metrics.py from the pinned map. The coverage app on the site tracks Enterprise, ICS, and Mobile separately and follows MITRE's releases. Pinned 20.0 (Enterprise) and 20.0 (ICS) on 2026-10-16. |
| MITRE ATLAS | technique ids for attacks on AI systems, accepted in score.yml beside ATT&CK ids; the ATLAS and D3FEND page lists the techniques ATLAS ties to a mitigation that detects. Release 2026.09, read through tools/atlas_extract.py into attack/atlas-2026.09.json. |
| MITRE D3FEND | the defensive techniques D3FEND links to each Enterprise and ICS technique, listed in the coverage map's technique detail by the artifact each one analyzes. Release 1.6.0, read through tools/d3fend_extract.py into attack/d3fend-1.6.0.json. |
| MITRE CTID Top ATT&CK Techniques | threat_relevance anchor 3 |
| SAFe Weighted Shortest Job First | formula shape: value over cost |
| Elastic Security Labs, Cloud Threat Emulation methodology | The emulation section: start modes, scope layers, plan-before-execute, foothold realism, telemetry verification, coverage outcomes, teardown. Part 1, published 21 September 2026, Terrance DeJesus and Bryan Porras Blanch. |
| MITRE Center for Threat-Informed Defense, Adversary Emulation Library | The plan-first shape of an emulation, and the micro and full scope layers. Public repository, read September 2026. |
Sigma's status field does the work of a stage label from build on, with deploy and tune sharing stable. Section 17 lists the status and the CI jobs for each stage.
20.1Open items
These get checked against their primary sources before each release:
- MITRE ATT&CK: re-run tools/attack_pin.py on each ATT&CK release and review the map diff; v19.2 renamed Defense Evasion to Stealth and added Defense Impairment; v20.0 added nine techniques, among them direct and indirect prompt injection, and moved none, and ICS techniques now include T16xx ids
- MITRE ATLAS: re-run tools/atlas_extract.py and the kit's tools/attack_pin.py --atlas-only on each ATLAS release and review the diff. The five mitigations the extract counts as detecting are named in the script and need checking against each release
- MITRE D3FEND: re-run tools/d3fend_extract.py on each D3FEND release. Release 1.6.0 maps to ATT&CK 19.0, so check which revoked ids moved to their replacements and whether a later release maps the techniques ATT&CK 20.0 added
- MITRE CTID Summiting the Pyramid: verify level wording and current version against the CTID primary source
- MITRE CTID Top ATT&CK Techniques: verify current list and calculator inputs against the CTID primary source
- Sigma rule status field: verify the status value list against the current Sigma specification
- Detection Engineering Maturity Matrix: map stages to dimensions from the primary source; unmapped until verified
- ACSC and CISA priority logs for SIEM ingestion (2025): map the 14 source categories to the telemetry inventory template