CMMC levels (32 CFR part 170) and the DFARS phase-in, explained
The CMMC program rule sets three levels and four assessment types for defense contractors that handle FCI or CUI. The DFARS rule effective November 10, 2025 puts them into contracts in phases, and a 2026 DFARS class deviation suspends the November 2026 move to Phase 2.
Two rules that work together
The Cybersecurity Maturity Model Certification (CMMC) program checks that defense contractors protect two kinds of unclassified information on their own systems: Federal Contract Information (FCI) and Controlled Unclassified Information (CUI). The program rule, codified at 32 CFR part 170, was published on October 15, 2024 (89 FR 83092) and took effect on December 16, 2024. The acquisition rule, which amends the Defense Federal Acquisition Regulation Supplement (DFARS), was published on September 10, 2025 (90 FR 43560) and took effect on November 10, 2025 [2].
Part 170 defines the levels, the assessments and the phase-in. The DFARS rule adds the solicitation provision at 252.204-7025 and the contract clause at 252.204-7021, and tells contracting officers what to check before award [2]. CMMC assessments validate security requirements contractors already have, and part 170 does not alter separately applicable requirements such as FAR 52.204-21 and DFARS 252.204-7012 [1]. The DFARS rule dropped a proposed duty to report security lapses to the contracting officer, finding that the incident reporting in 252.204-7012 paragraph (c) already gives enough notice [2].
Who is covered
Part 170 applies to Department of Defense contract and subcontract awardees that will process, store or transmit FCI or CUI on contractor information systems in performing the contract. It does not apply to federal information systems that contractors operate on the government’s behalf. Once fully phased in, CMMC requirements apply to solicitations and contracts above the micro-purchase threshold, including commercial items, except those solely for commercially available off-the-shelf (COTS) items [1]. Program managers and requiring activities choose the CMMC status for each procurement, based on the type of information involved, and the requirement flows down to subcontractors that handle FCI or CUI [1].
Three levels, four statuses
Level 1 (Self)
Level 1 covers the safeguarding requirements in FAR 52.204-21(b)(1)(i) through (xv). The contractor assesses itself every year, must meet every requirement, and may not use a Plan of Action and Milestones (POA&M) to defer any of them. Results go into SPRS with an affirmation of compliance [1].
Level 2 (Self) and Level 2 (C3PAO)
Level 2 requirements are identical to NIST SP 800-171 R2. Depending on the solicitation, the contractor either assesses itself or is assessed by an authorized or accredited CMMC Third-Party Assessment Organization (C3PAO). Either way the assessment is repeated every three years, and an affirming official affirms continuing compliance at each assessment and every year after [1].
Level 3 (DIBCAC)
Level 3 adds requirements selected from NIST SP 800-172 (February 2021). A contractor must first hold Final Level 2 (C3PAO) status for the Level 3 scope; the Defense Contract Management Agency’s Defense Industrial Base Cybersecurity Assessment Center (DCMA DIBCAC) then performs the assessment on the government’s behalf. Both assessments are repeated every three years [1].
Conditional status and the POA&M rules
At Levels 2 and 3, a contractor that falls short on a few requirements can reach a conditional status, and the DFARS rule confirms that a contract can be awarded on conditional status [2]. The limits are tight [1]:
- The assessment score divided by the total number of requirements at that level must be at least 0.8.
- At Level 2, no requirement on the POA&M may be worth more than one point, except CUI encryption where encryption is used but not FIPS-validated.
- Some requirements can never be deferred. At Level 2 they include the system security plan, external connections, control of public information and three physical access requirements. At Level 3 they include the security operations center, the cyber incident response team and supply chain risk requirements.
- The POA&M must be closed out by a closeout assessment within 180 days of the conditional status date, or the conditional status expires.
The four phases
Section 170.3(e) sets four phases. Phase 1 begins on the effective date of the DFARS rule; each later phase begins one calendar year after the one before [1]. The DFARS rule took effect on November 10, 2025 [2], so Phase 1 began that day. Part 170 gives no calendar dates for the later phases, and the move to Phase 2 has since been suspended (see below).
- Phase 1 (from November 10, 2025): the Department intends to require Level 1 (Self) or Level 2 (Self) as a condition of award in applicable solicitations, may apply them when exercising options on earlier contracts, and may require Level 2 (C3PAO) instead of Level 2 (Self).
- Phase 2 (one calendar year after Phase 1, under the rule text): the Department intends to add Level 2 (C3PAO) as a condition of award for applicable solicitations and contracts, with discretion to defer it to an option period; Level 3 (DIBCAC) at the Department’s discretion.
- Phase 3 (one calendar year after Phase 2): the Department intends to require Level 2 (C3PAO) for all applicable solicitations and contracts, as a condition of award and of exercising options on contracts awarded after the effective date, and Level 3 (DIBCAC) for all applicable solicitations and contracts as a condition of award, with discretion to defer it to an option period.
- Phase 4, full implementation (one calendar year after Phase 3): CMMC requirements in all applicable solicitations and contracts, including option periods on contracts awarded before Phase 4.
The DFARS rule frames the same change by its clause. For three years after the effective date, the clause is prescribed where program managers and requiring activities decide to apply a CMMC requirement. From three years and one day after the effective date, it is used whenever the contractor will process, store or transmit FCI or CUI on contractor information systems, again excluding awards solely for COTS items [2]. In very limited circumstances, a Service Acquisition Executive or Component Acquisition Executive, or a delegate, may waive inclusion of CMMC requirements in a solicitation or contract; the contractor’s other cybersecurity obligations still apply [1].
The Phase 2 suspension
DFARS Class Deviation 2026-O0025, Revision 3, signed September 3, 2026 (digital signature), supersedes Revision 2 of July 16, 2026 and carries forward its CMMC instruction [4]. Contracting officers are to work with requiring activities to remove or revise CMMC requirements in new and existing solicitations and contracts, in line with a Department of War Chief Information Officer memorandum of July 13, 2026, Suspension of the Advancement to Cybersecurity Maturity Model Certification Phase 2 Requirements. As the deviation describes it, the memorandum suspends the November 2026 CMMC Phase 2 transition; permits Level 1 (Self) or Level 2 (Self) assessments in all procurement requests and requirement documents; requires baseline compliance with NIST SP 800-171 Rev 2 under DFARS 252.204-7012; has active solicitations amended as soon as practicable; and has the requirements removed from existing contracts by modification before the next option period or at the next scheduled administrative modification [4]. The deviation stays in effect until rescinded or incorporated into the FAR, DFARS and DFARS PGI, and its text of DFARS 240.371-5 keeps the clause dates of November 9 and November 10, 2028 [4].
What the contracting officer checks
Offerors give the CMMC unique identifier, a ten-character alphanumeric code assigned to each CMMC assessment and shown in SPRS, for each information system that will handle FCI or CUI on the contract. The contracting officer checks SPRS and may not award a contract, task order or delivery order unless each of those systems has a current CMMC status at the required level or higher. The clause also requires subcontractors to submit their self-assessment results and affirmations in SPRS [2]. Contractors keep the artifacts used as assessment evidence for six years from the CMMC status date [1].
Cloud services and FedRAMP
A contractor at Level 2 may store or process CUI in a cloud service that is FedRAMP authorized at the Moderate baseline or higher, or that meets requirements equivalent to that baseline in accordance with Department of Defense policy [1]. FedRAMP, for its part, states that it does not provide equivalency and refers questions about FedRAMP and CMMC to the Department of War [3]. Contractors relying on a cloud provider’s claim of equivalency may want to check with counsel and the contracting officer which evidence the Department accepts.
Status as checked: part 170 text from the eCFR as of November 12, 2026 (checked November 14, 2026), and the class deviation checked on November 14, 2026. Which level a given contract requires is set in its solicitation.
Moraph’s teams help organizations with work like this: see our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.