CMMC Phase 2 Suspended: What Defense Contractors Still Owe Without the November 10 Deadline
CMMC Phase 2 was set for November 10, 2026, until DoW suspended it. What contractors still owe on NIST SP 800-171, SPRS, and 72-hour incident reports.
- Author
- Ackatec
- Published
- Reading time
- 7 min read
- CMMC
- NIST SP 800-171
- DFARS
- Defense industrial base
- Compliance readiness
- Security assessments
November 10, 2026 was supposed to be the day CMMC Level 2 third-party certification started showing up as a condition of award in Department of War (DoW) contracts. On July 13, 2026, the Department suspended that step, Phase 2, and set up a CMMC Reform Task Force to review the program, according to the DoD CIO's CMMC page (opens in a new tab). It is tempting to read the date as gone and the pressure as off.
The short answer: the certification deadline is paused; the security obligations are not. Contractors handling controlled unclassified information (CUI) still have to implement NIST SP 800-171 Revision 2, keep a current assessment score in the Supplier Performance Risk System (SPRS), affirm compliance where CMMC applies, and report cyber incidents within 72 hours. The pause is time to get ready, not time off.
What is CMMC Phase 2?
The Cybersecurity Maturity Model Certification (CMMC) program verifies that defense contractors protect federal contract information (FCI) and CUI. It was designed to roll out in four phases. Phase 1 began on November 10, 2025 and put Level 1 and Level 2 self-assessment requirements into new solicitations and contracts. Phase 2 would have required, for applicable contracts, a Level 2 certification from a Certified Third-Party Assessment Organization (C3PAO) as a condition of award. Pillsbury notes (opens in a new tab) that the final program rule estimated those assessments would affect about 76,000 businesses, at $104,670 to $117,768 each.
What exactly did the suspension change?
Under the July 13 memoranda, as summarized by Peckar & Abramson (opens in a new tab) and Pillsbury:
- Agencies may only require CMMC Level 1 (Self) or Level 2 (Self) as a condition of award.
- Level 2 (C3PAO) and Level 3 (DIBCAC) requirements are suspended until further notice.
- Solicitations that include those requirements must be amended to remove them, and existing contracts must be modified to remove them before the next option exercise or scheduled administrative modification.
On September 3, 2026, DoW turned that direction into acquisition guidance with Class Deviation 2026-O0025, Revision 3, listed on the DPCAP class deviations page (opens in a new tab). Dentons explains (opens in a new tab) that the revised DFARS Part 240 keeps the requirement to provide "adequate security" for covered defense information and to "rapidly report" cyber incidents within 72 hours, and that contracting officers must check SPRS before award and before option exercises when a CMMC level is required.
What do defense contractors still owe during the pause?
NIST SP 800-171 Revision 2, all 110 requirements
DFARS 252.204-7012 still requires contractors that handle covered defense information to implement NIST SP 800-171. The DoD CIO page states that the suspension "does not eliminate the requirement for companies to protect information" under that clause, and that DoW will enforce compliance through self-assessments and "select government-led assessments."
A current score in SPRS
Under DFARS 252.204-7019 (opens in a new tab), an offeror required to implement NIST SP 800-171 must have a current assessment, not more than 3 years old unless the solicitation says otherwise, with summary level scores posted in SPRS to be considered for award. A stale or inflated score is still a problem.
Self-assessments and annual affirmations
The DoD CIO page sets the current cadence:
- Level 1 (Self): the 15 requirements in FAR 52.204-21, self-assessed annually with results entered in SPRS, an affirmation after each assessment, and no plan of action and milestones (POA&M) permitted.
- Level 2 (Self): the 110 requirements in NIST SP 800-171 Revision 2, self-assessed every three years with results entered in SPRS, an affirmation after each assessment and annually thereafter, and POA&Ms permitted but closed out within 180 days.
A Level 2 (Self) status lapses if the annual affirmation is missed. The affirming official is signing a statement the government relies on.
72-hour incident reporting
DFARS 252.204-7012 (opens in a new tab) defines "rapidly report" as within 72 hours of discovery of a cyber incident, and requires preserving images of affected systems and relevant monitoring data for at least 90 days after the report.
Why is the pause not a reason to slow down?
Three reasons stand out.
- Self-attestation carries its own risk. Pillsbury warns that failing to meet these requirements could result in contract termination and False Claims Act liability. A score or affirmation that the environment does not support is exposure, with or without a third-party assessor.
- The next version is being decided now. The task force was given 60 days to review the program, a window that closed in September. As of October 26, 2026, DoW has not published its recommendations or a replacement schedule, and the DoD CIO page still describes the program as paused in Phase 1. Any reformed program is likely to start from NIST SP 800-171, because DFARS 252.204-7012 and the proposed CUI rule below both rest on it.
- The CUI rules are moving government-wide. Dentons reports that a June 23, 2026 proposed FAR rule would require NIST SP 800-171 Revision 3, add direct subcontractor reporting, and set a 72-hour period to report unmarked or mismarked CUI. The CUI case is slated to be implemented through FAR Case 2026-001, which Dentons reports is in comment review and draft final rule stage, with a report due November 18, 2026.
How should contractors use the time?
Verify the score you already posted
Re-test the controls behind your SPRS score instead of re-reading the System Security Plan. Confirm that multifactor authentication, logging, access control, and boundary protections work as written for every system in scope. A security assessment scoped to your CUI environment gives you a credible baseline before an affirmation is due.
Read your contracts, not the headlines
Pillsbury cautions that implementing the memos will likely bring delays and ambiguity, and that contractors and subcontractors should make sure their solicitations and contracts are formally amended where necessary. List every active contract and solicitation with CMMC or 7012 language, note the next option date, and ask your primes in writing whether their expectations of you have changed. Contract-specific questions belong with your counsel.
Close POA&Ms and keep evidence current
Treat open POA&M items as dated commitments with owners. Keep the evidence behind each requirement, such as configurations, access reviews, and training records, current enough that you could show it next month. Compliance readiness work connects each requirement to an owner and an evidence cadence so the program survives the next schedule change.
Start a Revision 3 gap view
Keep Revision 2 as your current baseline, as Dentons advises, while mapping where Revision 3 would add work. Sequencing those gaps now avoids a rushed effort once a final rule sets the date.
Make the affirmation a governed decision
Decide who signs the annual affirmation, what evidence they review first, and how exceptions reach leadership. A virtual CISO can own that rhythm when the organization does not have a full-time security executive. Ackatec supports readiness; assessors and the government determine outcomes, and readiness work does not guarantee a result.
CMMC pause readiness checklist
- Is our SPRS score current, less than 3 years old, and backed by controls we have recently tested?
- Who signs our annual affirmation, and what evidence do they review before signing?
- Have we listed every contract and solicitation with CMMC or DFARS 252.204-7012 language and its next option date?
- Have our primes confirmed in writing what they expect from us during the pause?
- Are open POA&M items owned, dated, and on track to close within 180 days?
- Could we report a cyber incident within 72 hours and preserve images for 90 days?
- Do we know where NIST SP 800-171 Revision 3 would add work?
If several answers are uncertain, start a conversation while the timeline is still yours to set.
References
- DoD CIO, About CMMC (opens in a new tab)
- DPCAP, DFARS Revolutionary FAR Overhaul Class Deviations (opens in a new tab) (Class Deviation 2026-O0025, Revision 3, September 3, 2026)
- Acquisition.gov, DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (opens in a new tab)
- Acquisition.gov, DFARS 252.204-7019, Notice of NIST SP 800-171 DoD Assessment Requirements (opens in a new tab)
- Pillsbury, The Department of Defense Abruptly Suspends Implementation of CMMC Phase II (opens in a new tab) (July 15, 2026)
- Peckar & Abramson, DoD Suspends Rollout of CMMC Program (opens in a new tab) (July 14, 2026)
- Dentons, CMMC Phase II Follow-Up: New FAR Part 40, CUI and Contractor Action Items (opens in a new tab) (October 21, 2026)
