C5 (Germany)
C5: Organisation of Information Security

C5 (Germany) C5-OIS-02: Information Security Policy

Top management adopts an information security policy and issues it to internal staff, external personnel and cloud customers, setting out why security matters, the security objectives and target level, the core security strategy, and the security organisation.

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

What else in your programme already covers this

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

APRA CPS 234 · 3 controls

  • CPS234-13 Board Responsibility for Information Security
  • CPS234-19 Information Security Policy Framework
  • CPS234-P19 Policy Direction to All Responsible Parties

FedRAMP High · 3 controls

  • PL-1 Policy and Procedures
  • PL-2 System Security and Privacy Plans
  • SI-1 Policy and Procedures

FedRAMP Moderate · 3 controls

  • PL-1 Policy and Procedures
  • PL-2 System Security and Privacy Plans
  • SI-1 Policy and Procedures

HIPAA Security Rule · 3 controls

  • CPS220-02 Board Responsibility for the Risk Management Framework
  • CPS220-P30 Minimum Contents of the Risk Management Strategy
  • CCM-DSP-01 Security and Privacy Policy and Procedures
  • CCM-GRC-01 Governance Program Policy and Procedures

NIS2 Directive · 2 controls

  • Art.20.1 Management body approves the cybersecurity risk-management measures and oversees their implementation
  • Art.21.2.a Policies on risk analysis and on information system security
  • 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.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

PCI DSS 4.0 · 2 controls

  • 12.1.1 12.1.1 Overall information security policy established and disseminated
  • 12.1.2 12.1.2 Security policy reviewed annually and updated as needed

SOC 2 · 2 controls

  • SOC2-CC1.2 CC1.2 Board independence and oversight of internal control (COSO principle 2)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • GS-1 Align organization roles, responsibilities and accountabilities

CMMC 2.0 · 1 control

DORA · 1 control

ISO 27001:2022 · 1 control

  • 5.1 Policies for information security

ISO 27002:2022 · 1 control

  • 5.1 Policies for information security

ISO 27701:2019 · 1 control

  • 6.2.1 Management direction for information security
  • 161R1-PM-2 Information Security Program Leadership Role

NIST SP 800-218 · 1 control

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-02 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 41 it maps to, and the evidence behind each claim, over MCP and REST.