# Government: regulation and compliance

**In short:** The DFARS rule that puts CMMC requirements into Defense contracts took effect on November 10, 2025, and 32 CFR part 170 phases the requirements in; a DFARS class deviation now carries forward a July 13, 2026 Department of War memorandum suspending the November 2026 move to Phase 2. NIST issued SP 800-53 Release 5.2.0 in August 2025 and SP 800-63-4 in July 2025, which supersedes SP 800-63-3. OMB memorandum M-26-05 of January 23, 2026 rescinded M-22-18 and M-23-16 and tells agencies to set software and hardware assurance policies that match their risk determinations. CISA’s February 2026 edge device directive tells agencies planning device refreshes to keep in mind the zero trust requirements of OMB memorandum M-22-09.

Government · Regulation & Compliance. Last reviewed November 14, 2026.

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. <https://creativecommons.org/licenses/by/4.0/>. Attribution: "Moraph Insights", <https://insights.moraph.com/sector/government/lens/regulation-and-compliance>.

## What to know now

Each point ends with the number of its source in "Sources". Points were checked on November 14, 2026 unless the point gives another date.

- Under 32 CFR 170.3(e), as in force on November 1, 2026, DoD phases CMMC requirements into solicitations and contracts over four phases. Phase 1 begins on the effective date of the 48 CFR part 204 CMMC acquisition rule, when DoD intends to require Level 1 (Self) or Level 2 (Self) status as a condition of award. Phase 2 begins one calendar year after Phase 1, when DoD intends to add Level 2 (C3PAO) status as a condition of award for applicable contracts. [1]
- The DFARS rule that puts CMMC into DoD contracts (DFARS Case 2019-D041) was published on September 10, 2025 (90 FR 43560) and took effect on November 10, 2025. Contracting officers must check the Supplier Performance Risk System and not award to an offeror without a current CMMC status at the required level; offerors also need a current affirmation of continuous compliance in that system. [2]
- DFARS Class Deviation 2026-O0025, Revision 3, signed September 3, 2026 (digital signature), tells contracting officers to remove or revise CMMC requirements in new and existing solicitations and contracts, following a Department of War CIO memorandum of July 13, 2026 that suspends the November 2026 CMMC Phase 2 transition, permits Level 1 (Self) or Level 2 (Self) assessments in all procurement requests, and requires baseline NIST SP 800-171 Rev 2 compliance under DFARS 252.204-7012. The deviation stays in effect until rescinded or incorporated into the FAR, DFARS and DFARS PGI. [7]
- On August 27, 2025, NIST issued SP 800-53 Release 5.2.0, a minor release. It adds SA-15(13), SA-24 and SI-02(07), revises SI-07(12), and updates the discussion text of controls including SA-04, SA-05, SA-08 and SI-02. [3]
- SP 800-63-4 replaced SP 800-63-3 in July 2025 as NIST's Digital Identity Guidelines, with companion volumes SP 800-63A-4, 800-63B-4 and 800-63C-4 for identity proofing, authentication and federation. A planning note NIST added on October 6, 2026 points to a new implementation resource hub. [4]
- OMB memorandum M-26-05 (January 23, 2026) rescinds M-22-18, on secure software development practices, and its companion M-23-16. Agencies must still keep a complete inventory of software and hardware and develop assurance policies that match their risk determinations and mission needs. They may still use the Secure Software Development Attestation Form, and may adopt contract terms requiring a current software bill of materials on request. [5]
- CISA’s Binding Operational Directive 26-02 (February 5, 2026) tells agencies planning technical refreshes of edge devices to keep in mind OMB memorandum M-22-09, Moving the U.S. Government Toward Zero Trust Cybersecurity Principles. It lists the M-22-09 actions on multifactor authentication, asset management, isolation of critical workloads and encryption of data in transit. [6]

## Sources

1. Department of Defense. 32 CFR 170.3, Applicability (CMMC Program). <https://www.ecfr.gov/current/title-32/section-170.3> Checked November 14, 2026.
2. Department of Defense. Defense Federal Acquisition Regulation Supplement: Assessing Contractor Implementation of Cybersecurity Requirements (DFARS Case 2019-D041), 90 FR 43560. <https://www.federalregister.gov/documents/2025/09/10/2025-17359/defense-federal-acquisition-regulation-supplement-assessing-contractor-implementation-of> Checked November 14, 2026.
3. National Institute of Standards and Technology. SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations (Release 5.2.0 planning note). <https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final> Checked November 14, 2026.
4. National Institute of Standards and Technology. SP 800-63-4, Digital Identity Guidelines. <https://csrc.nist.gov/pubs/sp/800/63/4/final> Checked November 14, 2026.
5. Office of Management and Budget. M-26-05, Adopting a Risk-based Approach to Software and Hardware Security. <https://www.whitehouse.gov/wp-content/uploads/2026/01/M-26-05-Adopting-a-Risk-based-Approach-to-Software-and-Hardware-Security.pdf> Checked November 14, 2026.
6. Cybersecurity and Infrastructure Security Agency. BOD 26-02: Mitigating Risk From End-of-Support Edge Devices. <https://www.cisa.gov/news-events/directives/bod-26-02-mitigating-risk-end-support-edge-devices> Checked November 14, 2026.
7. Department of War, Defense Pricing, Contracting, and Acquisition Policy. Class Deviation 2026-O0025, Revision 3: Revolutionary FAR Overhaul Part 40, DFARS Part 240 (memorandum and attachments), signed September 3, 2026 (digital signature). <https://www.acq.osd.mil/dpap/dars/classdev/DFARS_RFO/Part-240/2026-O0025_Rev3_TAB_A_Deviation_Memo.pdf> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/sector/government/lens/regulation-and-compliance>
Publisher: Moraph Insights
