Cybernion
← Insights

Security

What Is the NIST Risk Management Framework (RMF)?

12 Oct 2026 · Updated 12 Oct 2026

The NIST Risk Management Framework (RMF) is a seven step process, Prepare, Categorize, Select, Implement, Assess, Authorize, Monitor, that US federal agencies and contractors use to manage information system risk under FISMA. It draws on NIST SP 800-53 for controls and ends in an Authority to Operate, a formal, time limited decision that a system’s risk is acceptable.

The RMF is less a single document and more the connective process that ties several NIST publications together into one repeatable path from a new system to an authorised, monitored one.

What is the NIST Risk Management Framework?

The NIST Risk Management Framework is the process, defined in NIST SP 800-37, that US federal agencies use to identify, assess and manage the security and privacy risk of an information system across its life. It was built to satisfy the Federal Information Security Modernization Act (FISMA), which requires agencies to protect the confidentiality, integrity and availability of federal information. Rather than a checklist, the RMF is a life cycle, a system enters it before it is built and stays inside it, through the Monitor step, for as long as it operates.

The RMF matters to contractors and vendors as much as to agencies themselves, because most federal systems today run on commercial cloud platforms and software built by private companies. A vendor selling into the federal market, or a cloud provider seeking FedRAMP authorisation, is effectively being assessed against RMF style controls even when the RMF label is not used directly.

What are the seven steps of the RMF?

Prepare establishes the organisational and system level context before formal risk management activity starts, including identifying key roles, resources and the system’s boundary.

Categorize rates the system’s likely impact if confidentiality, integrity or availability were compromised, typically low, moderate or high, using FIPS 199. This categorisation drives how much control rigour applies later.

Select chooses the security and privacy controls that fit the system’s category, drawing on the NIST SP 800-53 control catalogue and tailoring it to the system’s actual risk.

Implement puts the selected controls in place and documents exactly how each one was applied.

Assess tests whether the implemented controls actually work as intended, usually carried out by an independent assessor, producing a security assessment report.

Authorize is the formal risk decision. An authorising official reviews the assessment and residual risk, then decides whether the system may operate, issuing an Authority to Operate.

Monitor continues for the rest of the system’s operational life, tracking control effectiveness, system changes and emerging risk, and feeding back into reauthorisation when needed.

How does the RMF relate to FISMA and NIST SP 800-53?

FISMA is the law. It obliges federal agencies to run an information security program and protect their systems, but it does not itself describe a step by step method. The RMF is the method agencies use to satisfy that legal obligation, and NIST is the body that publishes it under its statutory role in setting federal information security standards.

Inside the RMF, NIST SP 800-53 supplies the substance. Where the RMF’s Select step asks which controls apply, SP 800-53 is the catalogue those controls are drawn from, organised into families like access control, incident response and system integrity. FIPS 199 and FIPS 200 work alongside it, providing the categorisation method and minimum security requirements respectively. So a practical way to think about it: FISMA sets the obligation, the RMF is the process for meeting it, and SP 800-53 (plus FIPS 199 and 200) supplies the content that gets selected, implemented and assessed along the way.

What is an Authority to Operate and why does it matter?

An Authority to Operate (ATO) is the outcome of the RMF’s Authorize step, a formal statement by an authorising official that a system’s residual risk is acceptable and that it may run in production. It is not a one time certificate. An ATO typically carries a defined period and conditions, and it can be revoked or downgraded if the system’s risk profile changes materially, if a control fails during ongoing assessment, or if a serious incident occurs.

This is where the Monitor step earns its place in the framework rather than being an afterthought. Continuous monitoring keeps the authorising official’s risk picture current between formal reassessments, so an ATO reflects the system’s actual state rather than a snapshot taken once and forgotten. Organisations selling into the federal market often find that maintaining an ATO, not obtaining one, carries the ongoing cost and discipline.

How does the RMF compare to the Australian approach?

Australia does not run the RMF by name, but the ASD’s Information Security Manual describes a comparable cycle for government systems: defining the system and its data, selecting and implementing controls appropriate to its classification, having them independently assessed, and formally authorising the system to operate, generally by an agency’s own authorising officer.

The closest Australian equivalent to the RMF’s Assess step is an IRAP assessment, where an ASD endorsed assessor independently reviews a system’s security posture against the ISM and reports findings that inform the authorisation decision. The assessor does not grant authorisation, the agency’s own authorising officer does, in the same way a US RMF assessor’s report feeds an authorising official’s decision rather than making it. The two systems evolved separately but solve the same underlying problem, giving a decision maker enough independent evidence to accept risk deliberately rather than by default.

Frequently asked questions

What is the NIST Risk Management Framework?

The NIST Risk Management Framework, or RMF, is a structured process US federal agencies and their contractors use to manage cyber security risk in information systems. Set out in NIST SP 800-37, it moves a system through preparation, categorisation, control selection, implementation, assessment, authorisation and ongoing monitoring. It ties together several NIST publications into one repeatable process, and it underpins FISMA compliance across federal agencies.

What are the seven steps of the RMF?

The seven steps are Prepare, Categorize, Select, Implement, Assess, Authorize and Monitor. Prepare sets up the organisation and system context. Categorize rates the system’s impact level. Select chooses the applicable security controls. Implement puts them in place. Assess tests whether they work as intended. Authorize is the formal risk decision to let the system operate. Monitor continues to track the system and its controls for the rest of its life.

How does the RMF relate to FISMA and NIST SP 800-53?

FISMA, the Federal Information Security Modernization Act, is the law that requires federal agencies to protect their information systems, and the RMF is the process agencies use to meet that legal obligation. NIST SP 800-53 supplies the actual catalogue of security and privacy controls that gets selected and implemented during the RMF’s Select and Implement steps, so the RMF is the process and SP 800-53 is the content that fills it.

What is an Authority to Operate?

An Authority to Operate, or ATO, is the formal decision made at the RMF’s Authorize step that a system’s residual risk is acceptable and it may go into production. It is granted by an authorising official after reviewing the system’s security assessment, and it is not permanent, it is reassessed periodically and whenever the system changes materially, which is what the Monitor step exists to support.

Is there an Australian equivalent of the RMF?

Australia does not use the RMF by name, but the ASD’s Information Security Manual sets out a broadly similar cycle for government systems, defining the system, selecting controls, implementing and assessing them, and formally authorising the system to operate. An IRAP assessment plays a role comparable to the RMF’s independent assessment step, feeding into the Australian government’s own authorisation decision.

Sources:

  1. NIST SP 800-37 Rev 2, Risk Management Framework for Information Systems and Organizations, NIST Computer Security Resource Center, 2018
  2. FIPS 199, Standards for Security Categorization, NIST, 2004
  3. Information Security Manual, Australian Signals Directorate, 2026

Last updated: 30 August, 2026

Talk to us about your engagement

A scoped proposal within one business day.