CMMC 2.0CIS Controls v8

CMMC 2.0 covers 40.5% of CIS Controls v8

62 of the 153 controls in CIS Controls v8 are already satisfied by evidence you collected for CMMC 2.0. 91 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.

40.5%
of the target already covered
62
controls evidenced
91
genuine gaps
47
claims rejected in review

This number is directional. It says how much of CIS Controls v8 your CMMC 2.0 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.

171 candidate mappings were examined and 47 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.

CIS Control 6: Access Control Management6 of 8 evidenced, 2 to do
CIS Control 7: Continuous Vulnerability Management5 of 7 evidenced, 2 to do
CIS Control 4: Secure Configuration of Enterprise Assets and Software8 of 12 evidenced, 4 to do
CIS Control 17: Incident Response Management6 of 9 evidenced, 3 to do
CIS Control 5: Account Management4 of 6 evidenced, 2 to do
CIS Control 3: Data Protection6 of 14 evidenced, 8 to do
CIS Control 10: Malware Defenses3 of 7 evidenced, 4 to do
CIS Control 2: Inventory and Control of Software Assets3 of 7 evidenced, 4 to do
CIS Control 8: Audit Log Management5 of 12 evidenced, 7 to do
CIS Control 13: Network Monitoring and Defense4 of 11 evidenced, 7 to do
CIS Control 14: Security Awareness and Skills Training3 of 9 evidenced, 6 to do
CIS Control 12: Network Infrastructure Management2 of 8 evidenced, 6 to do
CIS Control 16: Application Software Security3 of 14 evidenced, 11 to do
CIS Control 1: Inventory and Control of Enterprise Assets1 of 5 evidenced, 4 to do
CIS Control 11: Data Recovery1 of 5 evidenced, 4 to do
CIS Control 18: Penetration Testing1 of 5 evidenced, 4 to do
CIS Control 9: Email and Web Browser Protections1 of 7 evidenced, 6 to do
CIS Control 15: Service Provider Management0 of 7 evidenced, 7 to do

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.

CM.L2-3.4.1CIS-1.1argued against and upheld
Establish and Maintain Detailed Enterprise Asset Inventory

Baseline configuration practice explicitly requires hardware, software and firmware inventories of systems.

SI.L2-3.14.2CIS-10.1argued against and upheld
Deploy and Maintain Anti-Malware Software

Providing protection from malicious code at workstations and servers is anti malware deployment.

SI.L2-3.14.4CIS-10.2argued against and upheld
Configure Automatic Anti-Malware Signature Updates

Updating malicious code protection mechanisms as new releases arrive is signature updating.

SI.L2-3.14.5CIS-10.4argued against and upheld
Configure Automatic Anti-Malware Scanning of Removable Media

Real time scanning of files from external sources when opened covers removable media.

MP.L2-3.8.9CIS-11.3argued against and upheld
Protect Recovery Data

Protecting the confidentiality of backup CUI at storage locations is protecting recovery data.

SC.L2-3.13.2CIS-12.2argued against and upheld
Establish and Maintain a Secure Network Architecture

Architectural designs and systems engineering principles promoting security is secure architecture.

SC.L2-3.13.1CIS-12.2argued against and upheld
Establish and Maintain a Secure Network Architecture

Controlling communications at external and key internal boundaries is the segmented network architecture.

AC.L2-3.1.14CIS-12.7argued against and upheld
Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise’s AAA Infrastructure

Routing remote access through managed access control points is the AAA infrastructure requirement.

Claims that did not hold

47 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.

SI.L2-3.14.7CIS-1.2
Address Unauthorized Assets

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.

RA.L2-3.11.2CIS-12.1
Ensure Network Infrastructure is Up-to-Date

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.

CM.L2-3.4.6CIS-12.2
Establish and Maintain a Secure Network Architecture

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.

AC.L2-3.1.5CIS-12.2
Establish and Maintain a Secure Network Architecture

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.

SC.L2-3.13.6CIS-12.2
Establish and Maintain a Secure Network Architecture

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.

AU.L2-3.3.4CIS-13.1
Centralize Security Event Alerting

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.

AU.L2-3.3.3CIS-13.1
Centralize Security Event Alerting

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.

AT.L2-3.2.2CIS-14.1
Establish and Maintain a Security Awareness Program

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.

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