CIS Controls v8 covers 53.8% of NIST Cybersecurity Framework 2.0
57 of the 106 controls in NIST Cybersecurity Framework 2.0 are already satisfied by evidence you collected for CIS Controls v8. 49 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.
What this leaves you to do
NIST Cybersecurity Framework 2.0 has 106 controls. Holding CIS Controls v8 already evidences 57 of them, so the work in front of you is 49 controls, not 106, which is 46% of the standard rather than all of it.
That is the whole claim. We do not know your hourly rate, how long a control takes you, or how many people you have, so there is no figure here in dollars or weeks. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.
This number is directional. It says how much of NIST Cybersecurity Framework 2.0 your CIS Controls v8 evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.
207 candidate mappings were examined and 79 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.
Where the gaps are
Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.
Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.
Claims that held
A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.
Audit log reviews are how potentially adverse events get analysed.
Centralised security event alerting surfaces adverse events for analysis.
Centralised logging is what makes correlation across sources possible.
Central alerting correlates events from host, network and application sources.
Central alerting routes adverse event information to authorised staff.
Defined communication mechanisms deliver event information to the right people.
Defined incident thresholds are the declaration criteria this outcome names.
DNS query logs monitor a network service commonly abused by attackers.
Claims that did not hold
78 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at medium confidence before it was rejected.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at medium confidence before it was rejected.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at low confidence before it was rejected.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at medium confidence before it was rejected.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at medium confidence before it was rejected.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at medium confidence before it was rejected.
Held back 2026-08-19. Generated by the retired metered path, refuted at 56 percent wherever re-judged. Pair pulled from sale pending a rebuild on the Max plan.
Claimed at high confidence before it was rejected.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at medium confidence before it was rejected.
The full report
Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.
Buy this crosswalk