Government · Regulation & Compliance
Government: regulation and compliance
What to know now
Each number links to the point's source. Points checked unless the point shows 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
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Sources
- Department of Defense. 32 CFR 170.3, Applicability (CMMC Program). Checked .
- Department of Defense. Defense Federal Acquisition Regulation Supplement: Assessing Contractor Implementation of Cybersecurity Requirements (DFARS Case 2019-D041), 90 FR 43560. Checked .
- 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). Checked .
- National Institute of Standards and Technology. SP 800-63-4, Digital Identity Guidelines. Checked .
- Office of Management and Budget. M-26-05, Adopting a Risk-based Approach to Software and Hardware Security. Checked .
- Cybersecurity and Infrastructure Security Agency. BOD 26-02: Mitigating Risk From End-of-Support Edge Devices. Checked .
- 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). Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the page where needed.
Looking Back
Week of November 10, 2025
CMMC’s first phase priced a signature, not a score
On November 10, 2025, Defense contracts began carrying CMMC cybersecurity requirements. Most eyes went to assessment levels, but the bigger change was a senior executive’s signature, which turned security claims into dated statements to the government with real legal weight.
Week of March 24, 2025
Why the Signal group chat was a channel design failure before it was a leak
A journalist added to a chat of senior officials made the headlines. For agencies at every level, the lasting failure was an approved channel that could not set content limits, confirm who was present and keep the record, all at once.
Week of September 2, 2024
Europe’s AI treaty attached its duties to the public function, not the payroll
Europe’s new AI treaty covers AI used by public authorities and by private companies acting on their behalf. So an agency’s duties follow the service into its contractors, and the fuzzy edge of “on their behalf” is where governance gaps will open.
Week of July 1, 2024
Records over deference: after Loper Bright, an agency’s best defense sat in its files
In five days, four Supreme Court decisions ended deference on what statutes mean, kept old rules open to new challengers, faulted an agency’s explanation and moved penalty cases to juries. What agencies could still defend lived in their records, which most managed badly.
Week of June 27, 2022
A rule’s survival odds belong in the compliance plan
West Virginia v. EPA gave courts a named test for striking down ambitious rules. That turned a rule’s survival into something agencies and regulated organizations must estimate: in writing new rules, defending existing programs and deciding when to spend on compliance.
Week of May 24, 2021
Twelve hours to report: the pipeline directive that set the clock for everyone
Less than three weeks after Colonial Pipeline, regulators gave critical pipelines twelve hours to report a cyber incident, a named coordinator on call around the clock and thirty days to grade themselves. All three ideas spread across sectors, and each needs different preparation.
Week of January 27, 2020
A 90-day declaration that ran for three years
The federal public health emergency declared on January 31, 2020, looked like a precaution. Then other powers, new laws and agency systems came to rest on it. Agencies needed to track what depended on it from day one, not when it ended.
Week of August 27, 2018
OMB’s 2018 rescission list removed reminders, not the controls behind them
M-18-23 retired decades of OMB guidance, including the 2008 order to secure federal DNS, which it said agencies should already have done. Rescission ended an instruction, not a risk: CISA’s January 2019 DNS directive asked for much of the same inventory.
Explainers, checklists and data
Explainer · November 14, 2026
Federal privacy impact assessments, SORNs, routine uses and matching agreements, explained
Before a federal agency builds or buys a system holding personal information, it owes a privacy impact assessment and, for a system of records, a Privacy Act notice with fixed waiting periods. OMB's 2025 Do Not Pay memorandum applies those rules.
Explainer · November 14, 2026
OMB M-25-21 on federal AI use, and the “Super Intelligence” wording of Executive Order 14434, explained
M-25-21 sets how federal agencies govern their own use of AI: Chief AI Officers, governance boards, inventories and minimum practices for high-impact AI. Executive Order 14434 changes the vocabulary agencies use, not the definition behind it.
Explainer · November 14, 2026
The CJIS Security Policy version 6.1, its priority markings and the 2027 zero-cycle end, explained
Version 6.1 of the FBI’s CJIS Security Policy, dated June 25, 2026, incorporates the calendar year 2025 changes to the modernized policy. Existing and Priority 1 requirements are sanctionable now; Priority 2 to 4 requirements sit in a zero-cycle that ends September 30, 2027.
Checklist · November 14, 2026
Checklist: the FISMA annual cycle for an agency CIO and CISO
Fourteen steps for a federal agency’s CIO, CISO and privacy officer through the FISMA year: the program 44 U.S.C. 3554 requires, the quarterly and annual CIO metrics for fiscal years 2026 and 2027, the agency head letter, and the one-hour and seven-day clocks for major incidents in OMB M-25-04.
Explainer · November 14, 2026
The ADA Title II web and mobile accessibility rule (28 CFR part 35, subpart H), explained
The Justice Department’s 2024 rule requires state and local governments to make their web content and mobile apps meet WCAG 2.1 Level AA. An interim final rule effective April 20, 2026 moved the compliance dates to April 26, 2027 and April 26, 2028.