Selecting a Risk Methodology and NIST SP 800-39's Multitier Approach
ISACA CDPSE · Privacy Risk Management · Bởi Super Admin
Organizations choose risk methodologies for regulatory, alignment, or convenience reasons, and NIST SP 800-39 structures risk management across organization, mission, and information systems tiers through framing, assessment, response, and monitoring.
Several established methodologies exist for organizations that want to manage risk using a formal standard, and understanding why organizations choose one over another, along with how the foundational NIST framework structures risk across an enterprise, is essential to applying risk management consistently.
Selecting a Risk Management Methodology
Organizations select a specific standard for a variety of reasons: they might be required to use it to address regulatory or contractual terms, believe it better aligns with their overall information risk program or the business as a whole, or want to start with a known standard process rather than creating one from scratch. NIST Special Publication 800-39, Managing Information Security Risk, describes the overall risk management process; NIST SP 800-37, the Risk Management Framework, is a lifecycle risk management process; and NIST SP 800-30, Guide for Conducting Risk Assessments, is a detailed standard describing the steps for conducting risk assessments.
NIST SP 800-39: Multitier Risk Management
NIST SP 800-39 defines how risk management fits within overall organizational governance and enterprise risk management through multilevel risk management at the information systems level, the mission/business process level, and the overall organization level. Communications flow up and down these tiers so risks are communicated upward for overall awareness while risk awareness and decisions are communicated downward. Although this might appear to be a discussion of cybersecurity risk, the methodology has wide application across operationally critical information systems, manufacturing, biomedical laboratory operations, or the protection and use of personal information, since the methodologies of identifying, analyzing, and treating risk are the same. Tier 1, the organization view, focuses on governance, the activities of the risk executive, and development of risk management and investment strategies. Tier 2, the mission/business process view, concerns enterprise architecture and enterprise security architecture, ensuring business processes are risk-aware. Tier 3, the information systems view, focuses on tactical aspects such as system configuration and hardening specifications, vulnerability management, and detailed steps in the systems development lifecycle. Other concepts discussed include trust, system trustworthiness, and organizational culture.
The NIST SP 800-39 Risk Management Steps
The overall process consists of four steps. Step 1, risk framing, establishes the assumptions, scope, tolerances, constraints, and priorities forming the business context considered before later steps take place. Step 2, risk assessment, is where threats and vulnerabilities are identified and assessed to determine the levels and types of risk. Step 3, risk response, analyzes each risk and develops strategies to reduce it through appropriate risk treatment options of accept, mitigate, avoid, and transfer. Step 4, risk monitoring, is the process of performing periodic and ongoing evaluation of identified risks to determine whether conditions and risks are changing.
Key takeaways
- Organizations select a risk standard due to regulatory requirements, program alignment, or preference for a known process.
- NIST SP 800-39 manages risk across three tiers: organization, mission/business process, and information systems.
- Risk management methodology applies broadly, not just to cybersecurity, including to personal information protection.
- NIST SP 800-39's four steps are risk framing, risk assessment, risk response, and risk monitoring.
Thảo luận / Bình luận (0)
Chưa có thảo luận nào cho bài viết này. Hãy gửi bình luận đầu tiên nhé!
Vui lòng Đăng nhập để tham gia thảo luận.