Skip to main content

RSK-04.1: Risk Register

RSK 10 — Critical Identify

Mechanisms exist to maintain a risk register that facilitates monitoring and reporting of risks.

Control Question: Does the organization maintain a risk register that facilitates monitoring and reporting of risks?

General (30)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC4.2-POF3
COBIT 2019 APO12.03 APO12.05
COSO 2017 Principle 7
CSA CCM 4 A&A-06 CEK-07 TVM-09
CSA IoT SCF 2 GVN-08
ISO/SAE 21434 2021 RQ-09-05 RQ-09-06.a RQ-09-06.b
ISO 31000 2009 5.6 5.7
ISO 31010 2009 4.3.6 5.5
ISO 42001 2023 6.1.2 9.3.2(a) 9.3.2(b)
MPA Content Security Program 5.1 OR-2.0
NIST AI 100-1 (AI RMF) 1.0 GOVERN 1.5 MANAGE 1.4 MEASURE 3.0 MEASURE 3.1 MEASURE 3.2
NIST Privacy Framework 1.0 ID.DE-P1
NIST 800-39 3.4
NIST 800-171 R3 (source) 03.12.02.a.01 03.12.02.a.02
NIST CSF 2.0 (source) GV.RM-06 ID ID.RA-01
PCI DSS 4.0.1 (source) 12.3.1 12.3.2
PCI DSS 4.0.1 SAQ A-EP (source) 12.3.1
PCI DSS 4.0.1 SAQ C (source) 12.3.1
PCI DSS 4.0.1 SAQ D Merchant (source) 12.3.1 12.3.2
PCI DSS 4.0.1 SAQ D Service Provider (source) 12.3.1
SWIFT CSF 2023 7.4A
TISAX ISA 6 1.4.1
UL 2900-1 2017 7.1.2
UN R155 7.3.3
UN ECE WP.29 7.3.3
SCF CORE Fundamentals RSK-04.1
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) RSK-04.1
SCF CORE ESP Level 1 Foundational RSK-04.1
SCF CORE ESP Level 2 Critical Infrastructure RSK-04.1
SCF CORE ESP Level 3 Advanced Threats RSK-04.1
US (8)
Framework Mapping Values
US C2M2 2.1 RISK-2.E.MIL2 RISK-2.F.MIL2 RISK-3.F.MIL2
US DHS ZTCF DEV-05
US FCA CRM 609.930(a)
US GLBA CFR 314 2023 (source) 314.4(c)(2)
US IRS 1075 2.E.5
US SEC Cybersecurity Rule 17 CFR 229.105(a) 17 CFR 229.105(b)
US - NV NOGE Reg 5 5.260.3
US - NY DFS 23 NYCRR500 2023 Amd 2 500.9(a)
EMEA (10)
APAC (4)
Framework Mapping Values
APAC India SEBI CSCRF GV.RM.S4
APAC Japan ISMAP 4.4.7.2 4.5.5
APAC New Zealand HISF 2022 HHSP65 HML64
APAC Singapore MAS TRM 2021 4.1.3 4.1.4(d) 4.5.2 4.5.3
Americas (4)
Framework Mapping Values
Americas Bermuda BMACCC 5.5
Americas Canada CSAG 6.24
Americas Canada OSFI B-13 1.3 3.1.1
Americas Canada ITSP-10-171 03.12.02.A.01 03.12.02.A.02

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to maintain a risk register that facilitates monitoring and reporting of risks.

Level 1 — Performed Informally

Risk Management efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • IT personnel use an informal process to identify, assess, remediate and report on risk.
  • Data/process owners are expected to self-manage risks associated with their systems, applications, services and data, based on the organization's published policies and standards, including the identification, remediation and reporting of risks.
  • Risk management processes (e.g., risk assessments) focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
Level 2 — Planned & Tracked

Risk Management efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Identify cybersecurity and data protection controls to address applicable statutory, regulatory and contractual requirements for risk management. o Implement and maintain a form of Risk Management Program (RMP) that provides operational guidance on how risk is identified, assessed, remediated and reported.

  • Risk management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • Data/process owners are expected to self-manage risks associated with their systems, applications, services and data, based on the organization's published policies and standards, including the identification, remediation and reporting of risks.
  • Data/process owners work with IT/cybersecurity personnel and Data Protection Officers (DPOs) to ensure applicable statutory, regulatory and contractual obligations are properly addressed, including the storage, transmission and processing of sensitive/regulated data.
  • IT/cybersecurity personnel:
  • Risk management processes (e.g., risk assessments) and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
Level 3 — Well Defined

Risk Management efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Analyzes the organization's business strategy to determine prioritized and authoritative guidance for Risk Management (RM) practices. o Develops a security-focused Concept of Operations (CONOPS) that documents management, operational and technical measures to apply defense-in-depth techniques across the enterprise for RM. o Provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data with regards to RM. o Maintains a common taxonomy of risk-relevant terminology to minimize assumptions and misunderstandings. o Enables data/process owners to conduct annual risk assessment of their operations that includes the likelihood and magnitude of harm, from unauthorized access, use, disclosure, disruption, modification or destruction of the organization's systems and data. o Assists users in making informed risk decisions to ensure data and processes are appropriately protected. o Enables the documentation of risk assessments, risk response and risk monitoring to support statutory, regulatory and contractual obligations for risk management practices. o Maintains a centralized risk register to reflect an active recording and disposition of identified risks. The risk register identifies and assigns a risk ranking to vulnerabilities and risks that is based on industry-recognized practices and facilitates monitoring and reporting of those risks. o Governs supply chain risks associated with the development, acquisition, maintenance and disposal of systems, system components and services.

  • A formal Risk Management Program (RMP) provides enterprise-wide guidance on how risk is to be identified, framed (e.g., risk appetite, risk tolerance, risk thresholds, etc.) assessed, mitigated/remediated and reported.
  • Criteria to define materiality for risk management decisions is defined.
  • A steering committee is formally established to provide executive oversight of the cybersecurity and data privacy program, including appropriately resourcing risk management operations.
  • A formally-documented Cybersecurity Supply Chain Risk Management (C-SCRM) plan exists to identify, assess and mitigate supply chain-related risks and threats;
  • The Chief Information Security Officer (CISO), or similar function with technical competence to address cybersecurity concerns,
  • A Governance, Risk & Compliance (GRC) function, or similar function:
  • An IT Asset Management (ITAM) function, or similar function, categorizes assets according to the data the asset stores, transmits and/ or processes, applying the appropriate technology controls to protect the asset and data.
Level 4 — Quantitatively Controlled

Risk Management efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
  • Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
  • Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
  • Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
  • Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
  • Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving

Risk Management efforts are “world-class” capabilities that leverage predictive analysis (e.g., machine learning, AI, etc.). In addition to CMM Level 4 criteria, CMM Level 5 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions.
  • Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes.

Assessment Objectives

  1. RSK-04.1_A01 a risk register is maintained to facilitate the monitoring and reporting of risks.

Evidence Requirements

E-RSK-03 Plan of Actions & Milestones (POA&M) / Risk Register

Documented evidence of a POA&M, or risk register, that tracks control deficiencies from identification through remediation.

Risk Management

Technology Recommendations

Micro/Small

  • Risk Management Program (RMP)
  • Risk register
  • Plan of Action & Milestones (POA&M)

Small

  • Risk Management Program (RMP)
  • Risk register
  • Plan of Action & Milestones (POA&M)

Medium

  • Risk Management Program (RMP)
  • Risk register
  • Plan of Action & Milestones (POA&M)

Large

  • Risk Management Program (RMP)
  • Risk register
  • Plan of Action & Milestones (POA&M)

Enterprise

  • Risk Management Program (RMP)
  • Risk register
  • Plan of Action & Milestones (POA&M)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.