control-coverage-mapping
Use when you need to answer "which attacker techniques do our controls actually stop, and how well?", "what controls should I have for this threat?", or "what telemetry should I collect to detect it?" — joining a customer's or your own security control baseline to ATT&CK techniques using a public, versioned evidence base of 9,545 control-to-technique mappings from six sources. Produces four ranked lists (addressed strongly, addressed weakly, real gaps, and techniques no control anywhere addresses). Use for control gap analysis, security programme prioritisation, board reporting on coverage, or the Resistance Strength side of a FAIR risk assessment. Invoke after /threat-actor-profiling or /lookup-liberty91 has produced a technique list.
Liberty91LTD · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Liberty91LTD/cti-skills --skill control-coverage-mapping技能说明
name: control-coverage-mapping description: Use when you need to answer "which attacker techniques do our controls actually stop, and how well?", "what controls should I have for this threat?", or "what telemetry should I collect to detect it?" — joining a customer's or your own security control baseline to ATT&CK techniques using a public, versioned evidence base of 9,545 control-to-technique mappings from six sources. Produces four ranked lists (addressed strongly, addressed weakly, real gaps, and techniques no control anywhere addresses). Use for control gap analysis, security programme prioritisation, board reporting on coverage, or the Resistance Strength side of a FAIR risk assessment. Invoke after /threat-actor-profiling or /lookup-liberty91 has produced a technique list. user-invocable: true metadata: version: 1.0.0 tags: [analysis, controls, mitre-attack, gap-analysis, fair, risk]
Control Coverage Mapping
Answers one question with evidence instead of opinion: which attacker techniques does this control set actually address, and at what strength?
The usual way to answer it is to put people in a room and negotiate a percentage. This skill replaces that with a join against a public, versioned table that both sides can read and challenge. Where the evidence rates a control's strength, that rating is carried through unchanged. Where it does not, the output says so rather than inventing a number.
When to invoke
- The user asks what their controls cover, where the gaps are, or how to prioritise security spend
- The user asks what controls they should have for a given threat, campaign or sector, with no baseline in hand
- A threat profile has produced a technique list and the next question is "so are we covered?"
- A FAIR or risk-quantification workflow needs the Resistance Strength input
- Board or audit reporting needs a defensible coverage statement with citations
- A vendor claims a product "stops" a technique and you want the public evidence
- A detection team asks what telemetry to collect for a given threat (
--telemetry)
Do NOT invoke for: deciding whether a control is correctly configured in a specific environment (that is a testing question, not a mapping question), or for producing a single vulnerability percentage (see Limits).
Four modes
Be clear which question you are answering, because the inputs and the honest wording differ.
| Question | Mode | Needs a baseline? |
|---|---|---|
| "What does my current control set cover?" | --controls baseline.csv | yes |
| "What controls should I have for this threat?" | omit --controls | no |
| "What do I actually implement?" | --mitigations | no |
| "What do I collect and correlate?" | --telemetry | no |
# COVERAGE — gap assessment against what they actually run
python3 tools/clis/map_controls.py --controls baseline.csv --techniques techs.json
# RECOMMEND — no baseline needed
python3 tools/clis/map_controls.py --techniques T1566,T1190,T1078 --top 15
# ACTIONABLE — ATT&CK mitigations and telemetry, combinable
python3 tools/clis/map_controls.py --techniques techs.json --mitigations --telemetry
Stdlib only, no install, no API key. Bundled data lives in data/attack-control-mapping/.
When "SI-04 System Monitoring" is not a useful answer
It usually is not, and this is a limit of the evidence base rather than of the question. The NIST half of the workbook carries a control id and a control name and nothing else: no control text, no enhancements, no protect/detect/respond split. SI-04 maps to 52 techniques in a real run, so as advice it means "monitor things". There is no field to expand it from, and paraphrasing NIST from memory into a customer deliverable is not sourcing, it is bluffing.
Two modes exist to answer the question properly, both carrying MITRE's own text unchanged:
--mitigations returns ATT&CK M-codes ranked by coverage of the supplied techniques, each with its published definition. On a real 79-technique set: M1047 Audit (19 techniques), M1026 Privileged Account Management (17), M1018 User Account Management (21), M1017 User Training (13). Narrower than a NIST family and each one arrives with a definition the reader can act on.
--telemetry resolves "monitoring" into named log sources and concrete detection logic, ranked by how much of the supplied technique set each covers, down to channel level: WinEventLog:Sysmon EventCode=1, auditd:SYSCALL execve, WinEventLog:Security 4688. Per technique it returns MITRE's detection strategy, e.g. for T1562 Impair Defenses: "unusual service stop events, termination of AV/EDR processes, registry modifications disabling security tools ... correlate process creation with service stop requests and registry edits."
Prefer these two whenever the output has to be acted on. Keep the NIST list for customers who must report in that language, and say plainly that the family label is doing a lot of work.
Both read pre-extracted files in data/attack-control-mapping/, not the full ATT&CK bundle, because mitre-attack/*.json is gitignored and absent on a fresh clone. Regenerate after an ATT&CK refresh with python3 data/attack-control-mapping/build_attack_extract.py.
Do not brief the basic hygiene: the distinctive/baseline split
An analyst does not put "user awareness training" in a threat briefing. It applies to everyone, everywhere, always, so it says nothing about the threat just analysed. But a naive ranking surfaces exactly those controls every time, because breadth is what it ranks on: M1018 User Account Management maps to 20% of every technique MITRE publishes, and SI-04 System Monitoring to most of the NIST-mapped universe. They top any list for any input.
The tool separates them by lift: the share of your techniques a control covers, divided by the share of all ATT&CK techniques it covers.
- lift ≈ 1.0 — covers your set a