← ClaudeAtlas

mitre-attacklisted

Use for any MITRE ATT&CK work: map incidents/reports to TTPs, validate IDs, detection coverage and gaps, Navigator layers, group profiling, emulation plans, Sigma/Atomic mapping, version migration.
THARAGESHWARAN-SATHYAMOORTHY/mitre-attack-skill · ★ 3 · AI & Automation · score 76
Install: claude install-skill THARAGESHWARAN-SATHYAMOORTHY/mitre-attack-skill
# MITRE ATT&CK skill Baseline: **ATT&CK v20.1** (v20 released 2026-10-13; v20.1 data patch modified 2026-11-05). Facts and the tool below were checked against live STIX data on **2026-11-14**. When live data disagrees with this text (a newer ATT&CK release), trust the live data. ATT&CK ships major releases in April and October plus smaller "Agile" releases (groups/software/campaigns) in between (first: v19.2, Aug 2026). ## Hard rules 1. **State the ATT&CK version** (and domain) in every deliverable. Get it from `attack.py version`. 2. **Verify every ID and name against live data** before output (`get`, or `validate` on the finished draft). Never quote IDs from memory. 3. **Never invent behavior.** Every mapping cites evidence (quote, log line, report page). No evidence, no mapping; inference is marked Low confidence with the reason. 4. **Redact before output.** Strip secrets, API keys, tokens, passwords, hashes of credentials, PII, salary data, and card numbers from any log, ticket, or connector data before it goes into a table, layer comment, or report. Use `[REDACTED-<type>]`. 5. **No weaponization.** Atomic Red Team output is test names, GUIDs, platforms, and executor type only. Do not write exploit code, payloads, or step-by-step attack commands. Emulation plans reference test IDs and are for authorized scope only. 6. Use the most specific sub-technique the evidence supports; otherwise the parent. 7. Enterprise content that says "Defense Evasion" or "14 tactics" is pre