CMMC, the Cybersecurity Maturity Model Certification, is the United States Department of Defense program that verifies whether defense contractors actually implement required cybersecurity controls before they can win or keep contracts. In cybersecurity law, it turns long-standing contract clauses into a condition of eligibility: a company that handles Federal Contract Information (FCI) or Controlled Unclassified Information (CUI) must hold the CMMC status that the solicitation specifies.
The program sits in the Tech regulation landscape next to European instruments such as NIS2 and the CRA, but its legal mechanism differs. It is procurement law, not general regulation: it binds only organizations that choose to do business with the Department of Defense, and it reaches deep into the defense industrial base through mandatory flow-down to subcontractors.
How CMMC turns contract clauses into verified compliance
CMMC closes the gap between self-declared compliance and real security. Since 2017, DFARS clause 252.204-7012 has required contractors to protect CUI with the controls of NIST SP 800-171, yet for years compliance rested largely on unverified self-attestation, and government reviews repeatedly found weak implementation.
The program rests on two rules. The program rule in 32 CFR Part 170, effective in December 2024, defines the levels, assessment procedures and the ecosystem of assessors. The acquisition rule in 48 CFR, which added DFARS clause 252.204-7021, took effect on November 10, 2025 and lets contracting officers require a CMMC status as a condition of award.
The following table shows the main legal building blocks and what each contributes.
| Instrument | Role in the program | Practical effect |
|---|---|---|
| FAR 52.204-21 | Basic safeguarding of FCI | Source of the 15 Level 1 requirements |
| DFARS 252.204-7012 | CUI protection and incident reporting | NIST SP 800-171 controls, 72-hour reporting |
| 32 CFR Part 170 | CMMC program rule | Levels, assessors, scoring, POA&M limits |
| DFARS 252.204-7021 | CMMC contract clause | Status required at award and maintained |
| DFARS 252.204-7019 and 7020 | NIST SP 800-171 assessment rules | Score posted in SPRS |
The three CMMC levels and their assessments
CMMC defines three levels tied to the sensitivity of the information a contractor handles. The original model of 2020 had five levels and its own practice catalog; the revised CMMC 2.0 model, announced in November 2021, reduced them to three and aligned the controls with existing NIST publications instead of inventing new ones.
The table below summarizes what each level covers and how it is verified.
| Level | Information protected | Requirements | Assessment |
|---|---|---|---|
| Level 1 (Foundational) | FCI only | 15 requirements from FAR 52.204-21 | Annual self-assessment |
| Level 2 (Advanced) | CUI | 110 requirements of NIST SP 800-171 Rev. 2 | Self-assessment or C3PAO every 3 years |
| Level 3 (Expert) | CUI in high-priority programs | Level 2 plus 24 from NIST SP 800-172 | Government assessment by DIBCAC |
Most CUI-handling contractors will need a third-party Level 2 assessment performed by a Certified Third-Party Assessment Organization (C3PAO) authorized by the accreditation body known as the Cyber AB. Level 3 requires a final Level 2 certification first, after which the Defense Industrial Base Cybersecurity Assessment Center assesses the additional controls.
Every level also requires an annual affirmation by a senior company official in the Supplier Performance Risk System (SPRS). This affirmation carries legal weight: a false statement can expose the company to liability under the False Claims Act, which the Department of Justice already uses against contractors that misrepresent cybersecurity compliance.
Scoring, POA&M rules and conditional status
Level 2 uses the DoD Assessment Methodology, which starts at 110 points and subtracts 1, 3 or 5 points for each unmet requirement depending on its weight, so the lowest possible score is minus 203. The resulting number is posted in SPRS, where contracting officers can see it.
A contractor that has not met every requirement can obtain conditional status if it reaches a minimum score of 88 and documents the gaps in a Plan of Action and Milestones (POA&M). Only lower-weighted requirements may be deferred, and all open items must be closed within 180 days, verified by a closeout assessment. Otherwise the conditional status expires.
This table lists the status outcomes a contractor can reach.
| Status | Condition | Validity |
|---|---|---|
| Final Level 1 | All 15 requirements met, no POA&M allowed | 1 year, renewed by self-assessment |
| Conditional Level 2 | Score of at least 88 with eligible POA&M items | 180 days to close gaps |
| Final Level 2 | All 110 requirements met or POA&M closed | 3 years with annual affirmation |
| Conditional Level 3 | Allowed POA&M for selected 800-172 items | 180 days to close gaps |
| Final Level 3 | All Level 3 requirements met | 3 years with annual affirmation |
Phased rollout and flow-down to suppliers
The Department of Defense is introducing CMMC through a four-phase rollout over three years, so that the assessor ecosystem can scale. Phase 1 began on November 10, 2025 with self-assessment requirements, Phase 2 from November 10, 2026 adds C3PAO certification for applicable Level 2 contracts, Phase 3 a year later adds Level 3, and Phase 4 in November 2028 brings full implementation across applicable contracts.
Flow-down is mandatory. A prime contractor must ensure that every subcontractor handling FCI or CUI holds the appropriate level for the information that actually flows to it. A prime with Level 2 may therefore require only Level 1 from a machine shop that never receives CUI, which makes scoping of information flows a commercial as well as a security decision.
The table compares CMMC with related regimes from the same Topic, which helps place its legal logic.
| Regime | Who is bound | Enforcement mechanism |
|---|---|---|
| CMMC | US defense contractors and subcontractors | Contract eligibility, False Claims Act |
| NIS2 | Essential and important entities in the EU | Supervision and administrative fines |
| CRA | Makers of products with digital elements | Market surveillance, CE marking |
| DORA | EU financial entities and ICT providers | Financial supervisory authorities |
Common mistakes when preparing for CMMC
Most failed or delayed assessments stem from scoping and documentation problems rather than missing technology. Experienced assessors report recurring patterns:
- Poorly defined CUI boundary: treating the whole network as in scope raises cost, while drawing it too narrowly leaves CUI on unassessed systems.
- Ignoring cloud obligations: cloud services that store CUI must meet FedRAMP Moderate or equivalent requirements.
- Paper policies without evidence: assessors test implementation, so the System Security Plan must match how systems really work.
- Inflated SPRS scores: an optimistic self-score creates legal exposure and collapses under third-party review.
- Late start: remediation of a mid-sized environment commonly takes 12 to 18 months before an assessment is realistic.
Organizations also underestimate the role of External Service Providers. A managed security provider that administers CUI systems falls into the assessment scope, so its own security practices and shared responsibility matrix must be documented and defensible.
A plain-language summary
CMMC is a security check for companies that work for the US military. If a company wants defense contracts and handles sensitive government information, it must prove that it protects that information properly. Saying so is no longer enough: depending on the contract, the company checks itself, or an independent assessor or government team checks it.
Think of it like a building inspection before occupancy. The rules for safe wiring already existed, but now an inspector confirms the work before anyone moves in. No passing result, no contract, and that applies to suppliers down the chain as well.
An example from practice
A precision machining firm with 120 employees supplies parts for a military aircraft program and receives technical drawings marked as CUI. Its first self-assessment produced an SPRS score of 62, mainly because of missing multifactor authentication, incomplete audit logging and engineers sharing drawings through a consumer file-sharing service.
The firm isolated engineering into a dedicated CUI enclave, moved file exchange to a FedRAMP Moderate cloud environment, deployed multifactor authentication and rewrote its System Security Plan. After 14 months its internal score reached 104. A C3PAO assessment found two lower-weighted gaps, granting conditional Level 2 status; the firm closed both within 90 days and received final Level 2 certification, which kept it eligible when the prime contractor’s next solicitation required it.