Risk Management

NIST SP 800-39

NIST SP 800-39 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
NIST SP 800-39 – Managing Information Security Risk: Organization, Mission, and Information System View
  • Classification
    Category
    Risk Management
    Domain
    Risk Management
    Framework Family
    NIST Special Publications
  • Regulatory Context
    Type
    Guidance
    Legal Instrument
    Guideline
    Sector
    Cross-Sector
    Industry
    Cross-Industry
  • Region / Publisher
    Region
    North America
    Region Detail
    United States
    Publisher
    National Institute of Standards and Technology (NIST)
  • Versioning
    Version
    Initial release (March 2011)
    Effective Date
    March 1, 2011
    Issue Date
    March 1, 2011
  • Adoption
    Adoption Model
    Voluntary
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: Yes

NIST SP 800-39 is a U.S. government publication available free of charge from NIST, and its tiers, components and tasks are included with the platform.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
NIST SP 800-39: Managing Information Security Risk
Defines the management of information security risk in organizational processes.
NIST Risk Management Framework (RMF)
Outlines the process for risk management in federal information systems.
NIST SP 800-53: Security and Privacy Controls
Provides controls to protect organizational operations and assets from cybersecurity risks.
NIST Cybersecurity Framework
Describes common policies to improve cybersecurity risk management.
NIST Risk Management Overview
Describes integration of risk management into organizational processes.
Key takeaways
  • NIST SP 800-39 is the NIST guideline for an integrated, organization-wide program for managing information security risk.
  • Published March 1, 2011, it has not been revised and is called the flagship document in NIST's FISMA series.
  • It defines four components, framing, assessing, responding, and monitoring, applied across three tiers: organization, mission and business processes, and systems.
  • Organizations establish a risk executive function and risk management strategy at Tier 1 and run the Risk Management Framework at Tier 3.
  • Its three tiers and four components are reused by SP 800-30 for risk assessment.

Overview

NIST SP 800-39, Managing Information Security Risk: Organization, Mission, and Information System View, is the NIST guideline for an integrated, organization-wide program for managing information security risk, which Section 1.1 calls the flagship document in the series NIST developed in response to FISMA. It defines four components of risk management, framing, assessing, responding and monitoring (Section 2.1), applied across three tiers: the organization (Tier 1), mission/business processes (Tier 2) and information systems (Tier 3) (Section 2.2).

NIST published it on March 1, 2011 through the Joint Task Force Transformation Initiative, and it has not been revised since. Section 1.1 says it satisfies FISMA and meets or exceeds the OMB Circular A-130, Appendix III requirements for executive agencies, applies to all federal information systems other than national security systems, and is complementary to a broader enterprise risk management (ERM) program; state, local and tribal governments and private sector organizations are encouraged to consider using it. Its purpose is deliberately broad, with the detail of assessing, responding and monitoring left to supporting NIST publications.

Organizations apply SP 800-39 by establishing a risk executive (function) and a risk management strategy at Tier 1 (Sections 2.3.2 and 2.3.3), designing risk-aware mission/business processes and an information security architecture at Tier 2 (Section 2.4), running the Risk Management Framework for systems at Tier 3 (Section 2.5), and carrying out the 14 tasks of Chapter Three, from identifying risk assumptions (Task 1-1) to monitoring systems and environments on an ongoing basis (Task 4-2).

Why does it matter?

SP 800-39 is the publication that gives the rest of the NIST risk management series its shape. Section 2.1 states that managing risk requires the involvement of the entire organization, from senior leaders setting strategic goals to the individuals operating the systems, and that risk-based decision making must be integrated into every aspect of the organization. Its three tiers and four components are reused by SP 800-30 for risk assessment and by SP 800-37 for the Risk Management Framework, so an organization that adopts it has one vocabulary for risk from the boardroom to the system owner.

Key benefits include:

  • Risk framed before it is assessed

Section 2.1 and Task 1-1 to Task 1-4 make the organization state its risk assumptions, constraints, tolerance and priorities and trade-offs before any assessment is run.

  • A named owner for organization-wide risk

Section 2.3.2 establishes the risk executive (function) as the common risk management resource for senior leaders, mission owners, CIOs, CISOs, system owners and common control providers.

  • Three tiers that inform each other

Section 2.2 ties Tier 1 priorities to the Tier 2 enterprise architecture and the Tier 3 allocation of controls, with inter-tier and intra-tier communication and a feedback loop.

  • Five defined risk responses

Section 3.3 and Appendix H cover accepting, avoiding, mitigating, sharing and transferring risk, with the requirement that a decision to accept risk is consistent with the stated tolerance.

  • Governance options stated

Appendix F describes centralized, decentralized and hybrid governance structures and the trade-offs of each.

How does it work?

Chapter Two sets out the fundamentals. Section 2.1 defines the four components: framing risk (establishing the context, which produces the risk management strategy), assessing risk, responding to risk and monitoring risk. Section 2.2 introduces the three-tiered approach: Tier 1 implements risk framing and provides the context for all risk management activities; the missions and business functions defined there shape the Tier 2 processes and the investment and funding decisions that drive enterprise architecture, and Tier 3 allocates and deploys management, operational and technical security controls.

Sections 2.3 to 2.5 describe each tier. The Tier 1 organization view covers governance (2.3.1), the risk executive (function) (2.3.2), the risk management strategy (2.3.3) and investment strategies (2.3.4). The Tier 2 mission/business process view covers risk-aware mission/business processes (2.4.1), enterprise architecture (2.4.2) and information security architecture (2.4.3). The Tier 3 information systems view is where the Risk Management Framework of SP 800-37 operates (2.5). Sections 2.6 to 2.8 then address trust and trustworthiness, including trust among organizations and the trustworthiness of systems, organizational culture, and the relationships among governance, risk tolerance, trust and culture.

Chapter Three is the process, with 14 tasks summarized in Appendix E. Framing (Section 3.1): identify risk assumptions (Task 1-1), constraints (1-2), risk tolerance (1-3) and priorities and trade-offs (1-4). Assessing (3.2): identify threats and vulnerabilities (2-1) and determine risk (2-2). Responding (3.3): identify alternative courses of action (3-1), evaluate them (3-2), decide (3-3) and implement (3-4). Monitoring (3.4): develop a risk monitoring strategy (4-1) and monitor systems and environments on an ongoing basis (4-2). Appendix H adds strategies for each of the five response types.

Key Elements

  • Four components (Section 2.1)

Frame, assess, respond and monitor, carried out as a holistic, organization-wide activity from the strategic to the tactical level with a feedback loop for continuous improvement.

  • Three tiers (Section 2.2)

Tier 1 organization, Tier 2 mission/business process and Tier 3 information system, with traceability and transparency of risk-based decisions across tiers.

  • Risk executive (function) (Section 2.3.2)

A functional role, not necessarily one person, that coordinates with senior leaders to establish risk management roles and responsibilities and an organization-wide approach to risk.

  • Risk management strategy (Section 2.3.3)

The Tier 1 output of risk framing: how the organization intends to assess, respond to and monitor risk, including its risk tolerance.

  • Enterprise and information security architecture (Sections 2.4.2 and 2.4.3)

Tier 2 structures that embed security into mission/business processes and allocate common, hybrid and system-specific controls.

  • Trust and trustworthiness (Section 2.6 and Appendix G)

How organizations establish trust with one another and judge the trustworthiness of systems, with trust models in Appendix G.

  • Process tasks (Chapter Three and Appendix E)

Tasks 1-1 to 4-2 with inputs, activities and outputs for framing, assessing, responding to and monitoring risk.

  • Governance and response strategies (Appendices F and H)

Centralized, decentralized and hybrid governance models; risk acceptance, avoidance, sharing and transfer, and mitigation strategies.

What does it cover?

SP 800-39 applies to managing information security risk to organizational operations (mission, functions, image and reputation), organizational assets, individuals, other organizations and the Nation arising from the operation and use of federal information systems (Section 1.1). It applies to all federal information systems other than national security systems, which may use it with the approval of officials exercising policy authority, and it is offered to state, local and tribal governments and the private sector. It is a strategic-level guide: it contains no security controls and no assessment procedures, and Section 1.1 says it is not intended to replace other risk-related programs the organization runs under other legislation, directives or policies.

What are its objectives?

Section 1.1 and Chapter Two set out what the publication is for:

Provide guidance for an integrated, organization-wide program for managing information security risk (Section 1.1).

Give a structured yet flexible approach that is intentionally broad-based, with the specifics of assessing, responding and monitoring supplied by other NIST publications (Section 1.1).

Sit within, and complement, a more comprehensive enterprise risk management program (Section 1.1).

Integrate risk-based decision making into every aspect of the organization, from senior leaders to those operating systems (Section 2.1).

Carry the risk management process across the three tiers with effective inter-tier and intra-tier communication (Section 2.2).

Establish the risk executive (function), the risk management strategy and the governance structure that give risk decisions an owner (Section 2.3).

Framework in Context

SP 800-39 is the top of the NIST risk management series. SP 800-30 Rev. 1 amplifies its assessing component with a detailed risk assessment method, and SP 800-37 Rev. 2 is the Tier 3 process named in Section 2.5 for individual systems; both reuse the three tiers and the frame, assess, respond and monitor components defined here. The CSRC record lists CSWP 3 as a related publication and no revision since 2011, so the March 2011 text remains current. Section 1.1 positions the guidance as complementary to an enterprise risk management program rather than a replacement for one.

Common Framework Mappings

NIST SP 800-39 is commonly mapped to the NIST publications that implement its tiers and to the governance and risk management frameworks that describe the same organization-wide process.

Mapped frameworks include:

CIS Controls v8.1

COBIT 2019

FedRAMP Rev. 5

ISO 27001:2022

ISO 27005:2022

NIST CSF 2.0

NIST 800-53 Rev.5

SOC 2

SMARTSUITE

How SmartSuite Supports NIST SP 800-39

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Enterprise Risk Management to hold the Tier 1 risk frame, the risk management strategy and the organization-wide risk register, and Cyber & IT Risk to record Tier 2 and Tier 3 risks, their responses and the monitoring that Tasks 4-1 and 4-2 require, so each tier can see the others.

Risk Frame Record (Tasks 1-1 to 1-4)

Record the organization's risk assumptions, constraints, risk tolerance and priorities and trade-offs as governed records that every assessment references.

Risk Management Strategy (Section 2.3.3)

Hold the Tier 1 strategy that states how the organization assesses, responds to and monitors risk, with the risk executive (function) as its owner.

Three-Tier Risk Register (Section 2.2)

Register organization, mission/business process and information system risks with links between tiers, so Tier 1 priorities trace to Tier 3 control decisions.

Risk Response Decisions (Tasks 3-1 to 3-4)

Capture alternative courses of action, the evaluation, the decision to accept, avoid, mitigate, share or transfer, and the implementation tasks with owners and dates.

Risk Monitoring Strategy (Tasks 4-1 and 4-2)

Define the purpose, type and frequency of monitoring and schedule the ongoing monitoring of systems and environments of operation.

Governance and Trust Records (Appendices F and G)

Document the governance model in use and the basis for trust relationships with other organizations and providers of common controls.

Related frameworks

COSO ERM 2017

COSO ERM (2017) sets five components and 20 principles for integrating risk management with strategy and performance. It is voluntary guidance from COSO, not a regulation.

ISO 31000:2018

ISO 31000:2018 gives guidelines on managing risk through eight principles, a framework and a process for any organization. It is not certifiable. ISO published it on February 14, 2018.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-37 Rev.2

NIST SP 800-37 Rev. 2 is the NIST Risk Management Framework: seven steps from Prepare to Monitor, with the tasks, roles and authorization decisions federal agencies apply under OMB A-130.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

FAQ

Frequently Asked Questions For NIST SP 800-39 (Managing Information Security Risk)

Section 2.1 defines them: frame risk (establish the context for risk-based decisions, producing the risk management strategy), assess risk, respond to risk once determined, and monitor risk on an ongoing basis. Chapter Three turns them into 14 tasks, Task 1-1 to Task 4-2, summarized in Appendix E.

Section 2.2 describes Tier 1, the organization level, which implements risk framing and sets the context; Tier 2, the mission/business process level, where enterprise architecture and information security architecture are designed; and Tier 3, the information system level, where the Risk Management Framework of SP 800-37 is applied (Section 2.5). Activities at Tier 1 directly affect Tiers 2 and 3.

Section 2.3.2 defines it as a functional role established within the organization to provide an organization-wide approach to risk management. It is the common risk management resource for senior leaders, mission/business owners, chief information officers, chief information security officers, system owners, common control providers and architects, and it coordinates with senior leaders to establish risk management roles and responsibilities.

Five: accepting, avoiding, mitigating, sharing and transferring risk (Sections 2.1 and 3.3). Appendix H gives strategies for each and says an overall risk response strategy specifies who is responsible, the effectiveness criteria, dependencies, the implementation timeline, monitoring plans and triggers; a decision to accept risk must be consistent with the organization's stated risk tolerance.

Section 1.1 says the publication satisfies FISMA and the OMB Circular A-130, Appendix III requirements for executive agencies and applies to all federal information systems other than national security systems; other organizations are encouraged to use it. NIST published it in March 2011 and the CSRC record lists no later revision, so the 2011 text is current.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.