- Subject
- Microsoft 365 & SharePoint
- Filed
- Source
- Rutter Technologies
- Loans
- 346
CMMC Phase II Pause: What Defense Contractors Still Need to Maintain
Phase II assessments are paused, but self-assessment and NIST SP 800-171 Rev. 2 obligations remain. Use the review period to check scope and controls.

The pause in CMMC Phase II does not remove the cybersecurity work defense contractors need to do. As of mid-October 2026, the Department of War had suspended the Phase II transition and its third-party assessment requirements, while self-assessments and existing contract obligations remained in force. For IT teams, the useful response is to treat this period as time to validate scope, controls and evidence before the framework changes again.

What the suspension changes
On July 13, 2026, the Department of War suspended the transition to CMMC Phase II, which had been scheduled for November 10, 2026. During the suspension, program managers may not designate Level 2 C3PAO or Level 3 DIBCAC assessment requirements. The department had launched a 60-day CMMC Reform Task Force review in July, with recommendations due to the DoW CIO. By mid-October, it had not publicly announced a replacement implementation framework.
Several requirements continue during this interim period. Applicable solicitations and contracts may still require Level 1 or Level 2 self-assessments. NIST SP 800-171 Revision 2 remains the technical baseline, enforced through self-assessments and select government-led assessments. DFARS 252.204-7012 safeguarding and cyber incident reporting requirements also remain in effect, including applicable subcontract flow-down obligations.
That combination matters: the formal Phase II transition is paused, but contractors still need to understand which requirements attach to their contracts and handle FCI and CUI appropriately. A change in assessment timing does not, by itself, change those underlying obligations.
Why accurate self-assessment still matters
A self-assessment is a representation of the controls in the organization’s actual environment. Contractors remain responsible for its accuracy, and their systems may be subject to select government-led assessments.
A June 2026 Justice Department announcement described a $507,144 False Claims Act settlement resolving allegations that a defense contractor had failed to meet required NIST SP 800-171 cybersecurity controls. A later assessment produced a score of -170, compared with the contractor’s previously reported self-assessment score of 110. The settlement involved allegations, with no determination of liability. For administrators, the practical point is that a reported score should match how the systems and processes operate in practice.
The pause gives organizations time to check that match. That means identifying where controlled information is handled, confirming technical controls are in place, and keeping evidence through routine operational processes. A folder of screenshots assembled just before an assessment may not show that a control has been applied consistently.
Readiness depends on the working environment
CMMC readiness involves both documentation and the technology that supports the documented controls. Common gaps include unclear paths for where CUI enters, moves through, is stored and leaves the organization; inconsistent multifactor authentication, privileged access and account reviews; and laptops or engineering workstations that are only partly managed.
Logging and recovery need the same operational attention. Logs may exist without being reviewed consistently or retained in a useful form. Backups may be configured but never tested through restoration. Evidence practices can also be improvised, leaving teams unable to show how a control works over time.
These gaps can affect security, self-assessment results and the quality of evidence available to support them. A practical review should connect each requirement to the systems, owners and recurring processes that make it work. That gives IT teams a clearer remediation list than treating readiness as a document editing exercise.
Using the review period
Rutter’s CMMC Readiness Hub organizes resources around common contractor questions, from determining whether CMMC applies to reviewing technical requirements. Its [overview of who needs CMMC](https://www.rutter-net.com/cmmc-readiness-hub/who-needs-cmmc) covers how contract language, FCI, CUI and prime contractor requirements can affect an organization. The [readiness process](https://www.rutter-net.com/cmmc-readiness-hub/cmmc-readiness-process) describes a seven-step, infrastructure-first approach, while the [IT requirements guide](https://www.rutter-net.com/cmmc-readiness/it-requirements) addresses identity, endpoints, logging, backup, remote access and evidence.
For Microsoft environments, Rutter’s [Azure for CMMC resource](https://www.rutter-net.com/azure-for-cmmc) discusses Azure, Azure Arc, Entra ID, Intune and Microsoft 365 as possible parts of a readiness strategy when configured appropriately. No platform makes an organization ready on its own. Teams still need to scope the environment and operate the controls. The [CMMC resources page](https://www.rutter-net.com/cmmc-readiness-hub/cmmc-resources) includes FAQs, guides, case studies and information about the suspension.
Rutter says it is not a C3PAO and does not conduct formal CMMC certification assessments. Its stated role is technical preparation: helping organizations locate FCI and CUI, strengthen identity and access, manage endpoints, improve logging and backup, prioritize remediation, and establish repeatable evidence practices. When a formal third-party assessment is required, an authorized assessment organization must perform it.
Checks for the next 90 days
- Map where FCI and CUI enter, move through, reside and leave the organization.
- Check which CMMC level, DFARS clauses and cybersecurity requirements apply to current contracts, solicitations and subcontract flow-down obligations.
- Review the System Security Plan and open POA&M items, with a named owner and remediation timeline for each.
- Confirm that the current self-assessment reflects the environment as it operates today.
- Set recurring evidence routines for access reviews, device compliance reporting and backup recovery tests.
These steps remain useful as the program evolves: they improve visibility into the environment and make it easier to show whether controls are working. Contractors can start with the [CMMC Readiness Hub](https://www.rutter-net.com/cmmc-readiness-hub), request a [readiness assessment](https://www.rutter-net.com/cmmc-readiness-hub/request-cmmc-readiness-assessment), or review the [Azure CMMC Guide](https://www.rutter-net.com/meeting-cmmc-requirements-with-azure-guide-2026-rutter). Requirements depend on each organization’s contracts, information types and applicable obligations.