C5 (Germany)
C5: Organisation of Information Security

C5 (Germany) C5-OIS-06: Risk Management Policy

Document, communicate and make available a risk management procedure that covers identification of confidentiality, integrity, availability and authenticity risks with named risk owners, likelihood and impact analysis, evaluation against defined acceptance criteria, treatment with residual risk acceptance, and recording of the activities performed.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 56 controls across 31 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • NIST-CSF-GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
  • NIST-CSF-GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained
  • NIST-CSF-GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated

NIST SP 800-161 Rev 1 · 5 controls

  • CPS230-11 Identification, Assessment and Management of Operational Risk
  • CPS230-15 Operational Risk Elements of the Risk Management Framework
  • CPS230-9 Management of the Full Range of Operational Risks
  • CPS230-P12 Key Principles for Operational Risk, Resilience and Service Providers
  • CPS220-04 Maintenance of a Risk Management Framework
  • CPS220-P28 Minimum Contents of the Risk Appetite Statement
  • CPS220-P35 Required Content of Risk Management Policies and Procedures

HIPAA Security Rule · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • AUCDR-IS-STEP3 Step 3 - Have and maintain an information security capability
  • CFTC-SS-1 Program of Risk Analysis and Oversight
  • CFTC-SS-17 Enterprise Technology Risk Assessment

NIS2 Directive · 2 controls

  • Art.21.1 Take proportionate all-hazards measures calibrated to the entity's own risk exposure
  • Art.21.2.a Policies on risk analysis and on information system security

SOC 2 · 2 controls

  • SOC2-CC3.1 CC3.1 Objectives specified clearly enough to assess risk (COSO principle 6)
  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)

APPI · 1 control

  • APPI-A46 Security and Proper Handling of Anonymized Personal Information

APRA CPS 234 · 1 control

  • CPS234-21 Implementation of Information Security Controls
  • SEC01-BP07 Identify threats and prioritize mitigations using a threat model

CMMC 2.0 · 1 control

DORA · 1 control

FedRAMP High · 1 control

  • RA-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • RA-1 Policy and Procedures

ISO 22301:2019 · 1 control

  • 6.1 Actions to address risks and opportunities

ISO 27001:2022 · 1 control

  • 5.1 Policies for information security

ISO 27701:2019 · 1 control

  • 5.4.1 Actions to address risks and opportunities

ISO/IEC 23894:2023 · 1 control

  • 23894-5.4.2 AI Risk Management Policy

NIST SP 800-172 · 1 control

  • 3.11.4e Security Solution Rationale Document

NIST SP 800-218 · 1 control

PCI DSS 4.0 · 1 control

  • 12.3.2 12.3.2 Targeted risk analysis for each customized-approach requirement

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in C5: Organisation of Information Security

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-OIS-06 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

Query this from an agent

The graph holds this control, the 56 it maps to, and the evidence behind each claim, over MCP and REST.