CSRMC: the Pentagon's plan to retire the RMF.
The Cybersecurity Risk Management Construct trades snapshot authorizations for continuous, automated defense across five lifecycle phases. What changes, what doesn't, and who's positioned for it.
In late September 2025 the Department of Defense announced the Cybersecurity Risk Management Construct (CSRMC), its plan to retire the Risk Management Framework as the way DoD systems get and keep authorization. The pitch, in the Department's own framing: move from static, checklist-driven, point-in-time assessments to dynamic, automated, continuous risk management, "cyber defense at the speed of relevance." Rollout guidance has been developing through 2026.
Why the RMF is being retired
The RMF's six steps produced authorizations that were snapshots: controls verified once, documented in sprawling packages, then left to decay until reauthorization. Timelines of 12–18 months were normal. The paperwork measured compliance at a moment; adversaries operate continuously.
The construct: five phases, built-in security
| Phase | What security looks like there |
|---|---|
| Design | Requirements and architecture carry security from day one |
| Build | Hardened pipelines; tooling generates the evidence instead of people typing it |
| Test | Continuous validation and adversarial testing in place of a one-time assessment |
| Onboard | Authorization decisions fed by live telemetry |
| Operations | Continuous monitoring as the default posture: the cATO mindset made standard |
Underneath the phases sit tenets the Department has emphasized: automation everywhere evidence is produced, continuous monitoring and authorization, DevSecOps as the delivery model, cyber survivability of fielded systems, and reciprocity: authorize once, use across the enterprise instead of re-adjudicating the same system in every enclave.
What changes for programs, and what doesn't
Changes: the work moves from documents to pipelines. Evidence that regenerates itself (scans, control checks, telemetry) becomes what authorization rests on, and continuous ATO stops being an exotic achievement and becomes the expected end state. Doesn't change: NIST 800-53 controls still sit underneath; existing ATOs don't evaporate; and CSRMC governs DoD systems; it is separate from CMMC, which remains the compliance regime for contractors handling FCI and CUI.
Our take
CSRMC rewards the posture the accelerated-ATO playbook builds: inherited controls, automated evidence collection, and monitoring wired in from the first sprint.
Quick answers
Does CSRMC cancel my current ATO?
Is CSRMC just continuous ATO by another name?
Does CSRMC replace CMMC?
Related reading
Working on this now?
Tell us where your program stands and we'll tell you what we would do next.
Talk to Ausper