CMMC 2.0: what defence suppliers must prove, level by level
The Cybersecurity Maturity Model Certification is the US Department of Defense’s way of verifying that contractors actually implement the safeguards they have been required to self-attest to for years. With the programme rule in force and CMMC requirements now appearing in contracts, this guide sets out the levels, the assessment routes and a practical path to Level 2.
CMMC does not invent new controls. Level 2 is NIST SP 800-171 Rev 2, all 110 requirements, assessed against the 320 assessment objectives in SP 800-171A. What changes is verification: a certified third-party assessment organisation (C3PAO) tests the objectives, the result is recorded in SPRS, and a senior company official affirms compliance annually, with False Claims Act exposure for getting it wrong.
Plans of action are allowed only for a limited set of lower-weighted requirements, must leave the score at 80 percent or above, and must be closed within 180 days. The era of running a defence contract on an open POA&M is over.
The 14 requirement families behind Level 2
Access Control (22 requirements)
Who can reach CUI, on what devices, with what privileges; remote access, wireless, mobile and session controls.
Awareness and Training (3)
Role-based security training, including insider threat awareness.
Audit and Accountability (9)
Logging, log review, protection of audit records, time synchronisation.
Configuration Management (9)
Baselines, change control, least functionality, software restrictions.
Identification and Authentication (11)
Unique identities, MFA for network and privileged access, password rules, replay resistance.
Incident Response (3)
Capability to detect, report and respond; incident tracking; testing of the response plan.
Maintenance (6)
Controlled maintenance, sanitised equipment, supervised remote maintenance.
Media Protection (9)
Marking, access, transport, sanitisation and encryption of media holding CUI.
Personnel Security (2)
Screening before CUI access; access removal on termination or transfer.
Physical Protection (6)
Physical access limits, escorts, visitor logs, control of physical devices.
Risk Assessment (3)
Periodic risk assessment, vulnerability scanning, remediation.
Security Assessment (4)
Assess controls, maintain a plan of action, monitor continuously, keep a system security plan.
System and Communications Protection (16)
Boundary protection, encryption in transit, CUI separation, session authenticity, FIPS-validated cryptography.
System and Information Integrity (7)
Flaw remediation, malicious code protection, monitoring of alerts and traffic.
Who it applies to
Every company in the defence supply chain that handles Federal Contract Information (Level 1) or Controlled Unclassified Information (Level 2 and 3), including subcontractors several tiers down. Requirements flow down through prime contractors, so a machine shop or engineering firm with no direct DoD contract can still need Level 2 to keep its largest customer. Non-US suppliers to US defence primes are in scope too.
From scope to evidence, in one system
All 110 requirements with their assessment objectives
GRCorb assesses Level 2 the way a C3PAO does: per requirement, per 800-171A objective, with evidence attached to the objective, not just the requirement. Gaps become findings with owners and due dates, which is the material a POA&M is built from.
Evidence from the environments CUI actually lives in
Adapters for Microsoft 365 and Entra ID, Intune, Defender, AWS and Azure collect the configuration that proves access control, authentication, logging and integrity requirements, and re-validate it so the position holds between the assessment and the annual affirmation.
Self-hosted or air-gapped for CUI enclaves
For organisations that keep CUI in an isolated enclave, GRCorb deploys inside it, with a local AI model, so compliance data never leaves the boundary.
Crosswalk to 800-53, ISO 27001 and SOC 2
Suppliers that also hold ISO or SOC 2 reuse that evidence through the unified crosswalk rather than running parallel programmes.
Policies and the system security plan narrative
The AI Policy Builder generates the policy set 800-171 expects, scoped to the enclave, and the control-by-control status exports as the basis of the SSP an assessor reads first.
Frequently asked questions
Which level do we need?
Read your contracts and ask your prime. If you only ever receive Federal Contract Information, Level 1. If you receive, create or store CUI, Level 2. Level 3 is reserved for a small number of programmes handling the most sensitive CUI.
When does this actually hit our contracts?
The contract clause took effect on 10 November 2025 and is phased in: self-assessments first, then C3PAO certifications in an increasing share of solicitations over the following years, until all applicable contracts require it. Because the assessment itself takes months to prepare for, waiting for the clause to appear is too late.
What is SPRS and the score?
The Supplier Performance Risk System is where your 800-171 assessment score (from a maximum of 110, and potentially negative) and CMMC status are recorded. Primes check it before awarding work.
Rev 2 or Rev 3 of 800-171?
CMMC Level 2 is assessed against Rev 2, by DoD class deviation, even though NIST published Rev 3 in May 2024. Track Rev 3 for the future, assess against Rev 2 today.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.