Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

NIST SP 800-37: the Risk Management Framework (RMF), explained

Last updated:

NIST SP 800-37, "Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy," defines the Risk Management Framework (RMF) — NIST's own Risk Management project page calls it "a comprehensive, flexible, repeatable, and measurable 7-step process that any organization can use to manage information security and privacy risk." The current version, Revision 2, was published 20 December 2018, superseding Revision 1 (5 June 2014). RMF was built to support compliance with the US Federal Information Security Modernization Act (FISMA), but the step structure and the idea of integrating security, privacy and supply-chain risk into one life-cycle process are referenced well beyond federal agencies.

Key takeaways

  • Each step is further broken into numbered tasks in the full SP 800-37 Rev.
  • Prepare did not exist in Revision 1.
  • The first NIST publication to integrate security and privacy risk management into one methodology, rather than treating privacy as a separate add-on process.
  • SP 800-39, "Managing Information Security Risk," establishes the organization/mission-business-process/system risk-management tiers that the Prepare step operationalizes at each level.

The seven steps

NIST's own About RMF page lays out the sequence:

Step Purpose, per NIST
Prepare "Essential activities to prepare the organization to manage security and privacy risks"
Categorize "Categorize the system and information processed, stored, and transmitted based on an impact analysis"
Select "Select the set of NIST SP 800-53 controls to protect the system based on risk assessment(s)"
Implement "Implement the controls and document how controls are deployed"
Assess "Assess to determine if the controls are in place, operating as intended, and producing the desired results"
Authorize A senior official "makes a risk-based decision to authorize the system (to operate)"
Monitor "Continuously monitor control implementation and risks to the system"

Each step is further broken into numbered tasks in the full SP 800-37 Rev. 2 text — for example, NIST's dedicated Prepare-step page lists outcomes including risk management roles being identified, an organizational risk management strategy and risk tolerance being established, an organization-wide risk assessment, and a continuous-monitoring strategy. This guide describes the seven steps at that level; readers implementing RMF task-by-task should work from the primary SP 800-37 Rev. 2 document itself rather than a secondary summary for the individual task IDs.

Prepare: what step did Revision 2 add?

Prepare did not exist in Revision 1. NIST's About RMF page for this step states its purpose is to "carry out essential activities to help prepare all levels of the organization to manage its security and privacy risks using the RMF," with outcomes spanning the organization, mission/business-process and system levels — not just a single system owner's checklist. Folding in a dedicated preparation step ahead of Categorize is one of the clearest structural differences between Rev. 1 and Rev. 2.

What changed in Revision 2 (2018)

NIST's news post announcing Revision 2 states it was developed in response to Executive Order 13800, "Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure," along with related OMB circulars and memoranda. Beyond adding the Prepare step, NIST describes Rev. 2 as:

  • The first NIST publication to integrate security and privacy risk management into one methodology, rather than treating privacy as a separate add-on process.
  • Incorporating supply chain risk management (SCRM) concepts into the RMF, addressing risks like counterfeit components, tampering and malicious code insertion.
  • Aligning more closely with the NIST Cybersecurity Framework and incorporating systems-engineering concepts from SP 800-160.

How RMF fits with SP 800-53, SP 800-30 and SP 800-39

RMF does not define its own control catalog or risk-assessment methodology from scratch — it calls on companion NIST publications at specific steps:

  • SP 800-53 (our guide) supplies the control catalog: NIST's own description of the Select step is to "select the set of NIST SP 800-53 controls to protect the system based on risk assessment(s)."
  • SP 800-39, "Managing Information Security Risk," establishes the organization/mission-business-process/system risk-management tiers that the Prepare step operationalizes at each level.
  • SP 800-30 (our guide) is the detailed how-to for actually conducting a risk assessment — the activity that feeds both the Prepare step's organization-wide risk assessment and the risk-based control decisions made in Select.

Treated together, SP 800-39 sets the risk-management program, SP 800-30 tells you how to assess risk within it, SP 800-53 supplies the controls to select from, and SP 800-37 is the life-cycle process — Prepare through Monitor — that ties categorization, control selection, implementation, assessment, authorization and ongoing monitoring into one repeatable sequence.

How many tasks does each step contain?

The full SP 800-37 Rev. 2 text numbers its tasks by step. Knowing the count helps size the work and read an agency's documentation requests, which often cite task IDs directly.

Step Task IDs Tasks Example task relevant to a product supplier
Prepare P-1 to P-18 18 (P-1 to P-7 organization level, P-8 to P-18 system level) Identifying the system's components and its boundary
Categorize C-1 to C-3 3 Security categorization of the system and its information
Select S-1 to S-6 6 Choosing and tailoring controls, allocating them to system elements
Implement I-1 to I-2 2 Implementing controls and updating the plans with what was built
Assess A-1 to A-6 6 Assessing controls and preparing remediation actions
Authorize R-1 to R-5 5 The authorizing official's risk determination and decision
Monitor M-1 to M-7 7 Ongoing assessment, risk response and system disposal

How does a connected device enter an RMF system?

The RMF authorizes systems, not products. A device maker never receives an authorization; the agency or contractor that operates the system does. Your device becomes one of the system elements to which controls are allocated in Select and which is assessed in Assess. NIST has published companion documents that bridge the gap between a device and the system controls:

NIST document What it gives the RMF process
FIPS 199 The low / moderate / high impact levels for confidentiality, integrity and availability used in Categorize
SP 800-53 Rev. 5 and SP 800-53B The control catalog and the low, moderate, high and privacy baselines used in Select
SP 800-213 Guidance for federal agencies on establishing IoT device cybersecurity requirements, mapped to SP 800-53 controls
NISTIR 8259A The core device cybersecurity capability baseline: device identification, configuration, data protection, logical access, software update and cybersecurity state awareness
SP 800-161 Rev. 1 Cybersecurity supply chain risk management practices that agencies apply to suppliers
SP 800-137 Information security continuous monitoring, the basis of the Monitor step

For the device side, see our guides to NIST IoT device cybersecurity requirements, SP 800-161 C-SCRM and SP 800-137 continuous monitoring.

Which RMF steps need evidence from the device maker?

The agency runs the steps, but several of them stall without supplier input. The mapping below is our reading of where product evidence is usually requested.

RMF step What the agency is doing Evidence a device maker can supply
Prepare (system level) Identifying system elements and the authorization boundary Product description, network interfaces, data flows, cloud dependencies
Categorize Rating impact for the information the device handles Data types the device stores and transmits, and where
Select Allocating controls to the device Capability statement against NISTIR 8259A, list of configurable security settings
Implement Configuring the device in the system Hardening guide, default-credential handling, update procedure
Assess Testing whether controls work SBOM, known-vulnerability status per firmware version, test reports
Authorize Weighing residual risk Support period, vulnerability disclosure policy, open issues with fix dates
Monitor Tracking change and new risk Security advisories, update notes, notification route for new vulnerabilities

An SBOM is useful at several steps at once: it supports the boundary description, the supply chain questions behind SP 800-161, and the vulnerability evidence in Assess and Monitor. Our firmware SBOM guide covers how to produce one from an image.

Worked example: categorizing a building-sensor gateway

Synthetic example. The agency, product and ratings are invented for illustration.

A hypothetical agency adds an environmental-sensor gateway to its facilities system. The gateway reads temperature and occupancy sensors and forwards data to a building-management server.

  1. Information typesThe agency lists sensor readings and occupancy counts, plus gateway configuration and credentials.
  2. FIPS 199 ratingsConfidentiality: low (no personal data, aggregate occupancy). Integrity: moderate (false readings could drive wrong HVAC or occupancy decisions). Availability: low (data gaps are tolerable for hours). Following FIPS 199's high-water mark, the overall categorization is moderate.
  3. SelectThe agency starts from the SP 800-53B moderate baseline, uses SP 800-213 to identify which controls the gateway itself must support, and asks the maker which capabilities from NISTIR 8259A the product has.
  4. Supplier responseThe maker sends a capability table, a hardening guide, a CycloneDX SBOM for the current firmware with known vulnerabilities and their status, and its update and disclosure process.
  5. GapsThe gateway cannot send logs to a central server. The agency records compensating controls (network monitoring on the gateway's segment) in its plan of action and milestones, and the maker adds remote logging to a dated release.

What are the common pitfalls?

  • Expecting the product to be "RMF certified". There is no such certification; authorization is granted to a system by an agency official.
  • Answering Select with marketing copy. Assessors want a capability-by-capability statement they can test, not a feature list.
  • An SBOM with no vulnerability status. A component list without known-vulnerability results per version leaves the Assess step to do that work, usually slowly.
  • Ignoring Monitor. Authorization is followed by continuous monitoring; a supplier with no advisory channel or update notes becomes a monitoring gap.
  • Treating the cloud backend as out of scope. If the device depends on your cloud service, the agency will ask about it during Prepare boundary work.

A workable starting point

  1. Don't skip PrepareNIST added it specifically because organizations that jumped straight to Categorize without an established risk strategy, defined roles and identified common controls ended up rebuilding the same groundwork for every new system.
  2. Treat Select as a two-input decision, not a static checklist: the SP 800-53 baseline plus the risk assessment from SP 800-30/800-39 together determine which controls actually apply.
  3. Scope Monitor before you need itThe continuous-monitoring strategy is itself a Prepare-step outcome — deciding what "continuous" means for a given system is cheaper to do early than to retrofit after Authorize.
  4. Treat privacy as integrated, not bolted on, per Rev. 2's own stated intent — privacy risk decisions should flow through the same seven steps as security risk decisions, not a parallel process.

SoftWSP helps device and firmware teams produce two pieces of that evidence: a CycloneDX 1.6 SBOM extracted from a firmware image, and its known-vulnerability status from NVD, CISA KEV, FIRST EPSS and CISA ICS advisories, written up as a cited report reviewed by an engineer. See device firmware security.

This guide summarises public NIST publications; it does not constitute legal or compliance advice.

Put this guide to work

Frequently asked questions

What is the NIST Risk Management Framework (RMF)?

The Risk Management Framework is the process NIST Special Publication 800-37 defines for managing security and privacy risk across an information system's life cycle. NIST's own Risk Management project page describes it as "a comprehensive, flexible, repeatable, and measurable 7-step process that any organization can use to manage information security and privacy risk," built to meet the requirements of the Federal Information Security Modernization Act (FISMA) and linked to the broader suite of NIST SP 800-series guidance. The current version is SP 800-37 Revision 2, "Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy," published 20 December 2018, which supersedes Revision 1 (5 June 2014).

What are the 7 steps of the RMF?

Per NIST's own About RMF page: Prepare ("essential activities to prepare the organization to manage security and privacy risks"), Categorize ("categorize the system and information processed, stored, and transmitted based on an impact analysis"), Select ("select the set of NIST SP 800-53 controls to protect the system based on risk assessment(s)"), Implement ("implement the controls and document how controls are deployed"), Assess ("assess to determine if the controls are in place, operating as intended, and producing the desired results"), Authorize (a senior official "makes a risk-based decision to authorize the system [to operate]"), and Monitor ("continuously monitor control implementation and risks to the system"). Each step breaks down further into numbered tasks in the full SP 800-37 Rev. 2 text; this guide describes the steps themselves rather than re-deriving every individual task ID, which is best confirmed against the primary document.

What did Revision 2 (2018) change from Revision 1?

NIST's own news post announcing the revision states it was developed in response to "Executive Order 13800, Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure," along with related OMB circulars and memoranda. The headline changes it lists: the new Prepare step, added to enable "more effective, efficient, and cost-effective security and privacy risk management processes" by linking senior-leadership and system-level activity; integrated privacy risk management, which NIST describes as making Rev. 2 "the first NIST publication to address security and privacy risk management in an integrated, robust, and flexible methodology"; new supply chain risk management (SCRM) concepts folded into the RMF to address counterfeits, tampering and malicious code insertion; and closer alignment with the NIST Cybersecurity Framework and the systems-engineering processes in SP 800-160.

How does RMF relate to SP 800-53, SP 800-30 and SP 800-39?

They are companion documents the RMF steps call on rather than competitors. NIST's RMF overview page states the Select step chooses "the set of NIST SP 800-53 controls to protect the system based on risk assessment(s)" — SP 800-53 (see our [controls guide](/guides/nist-sp-800-53-security-privacy-controls/)) is the control catalog RMF draws from. SP 800-39, "Managing Information Security Risk," sets the organization/mission/system risk-management tiers that the RMF's Prepare step operationalizes; SP 800-30 (see our [risk assessment guide](/guides/nist-sp-800-30-risk-assessment/)) is the detailed how-to for the risk assessment activity that feeds both the Prepare step's organization-wide risk assessment and the Select step's risk-based control decisions.

Sources

  1. NIST CSRC: SP 800-37 Rev. 2, Risk Management Framework for Information Systems and Organizations — final publication page
  2. NIST: Risk Management Framework for Information Systems and Organizations — publication page
  3. NIST CSRC: Risk Management project overview (RMF, 7-step process, FISMA)
  4. NIST CSRC: About RMF — the 7 steps
  5. NIST CSRC: About RMF — Prepare step
  6. NIST CSRC news: RMF Update — NIST Publishes SP 800-37 Rev. 2 (20 December 2018)
  7. NIST SP 800-37 Rev. 2, PDF (task numbering P-1 to M-7)
  8. NIST CSRC: FIPS 199, Standards for Security Categorization
  9. NIST CSRC: SP 800-53 Rev. 5
  10. NIST CSRC: SP 800-53B, Control Baselines
  11. NIST CSRC: SP 800-213, IoT Device Cybersecurity Guidance for the Federal Government
  12. NIST CSRC: NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline
  13. NIST CSRC: SP 800-161 Rev. 1, C-SCRM Practices
  14. NIST CSRC: SP 800-137, Information Security Continuous Monitoring
Was this guide helpful?

In this cluster