C5 (Germany)
C5: Compliance

C5 (Germany) C5-COM-02: Policy for planning and conducting audits

Document, communicate and provide audit planning and conduct rules that confine auditors to read only access within the agreed plan, place potentially disruptive activity into maintenance windows or off peak periods, and require audit activity to be logged and monitored.

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

What else in your programme already covers this

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

ISO 27701:2019 · 3 controls

  • 6.15.2 Information security reviews
  • 6.9.7 Information systems audit considerations
  • 8.2.5 Customer obligations

NIST SP 800-53 Rev 5 · 3 controls

APRA CPS 234 · 2 controls

  • CPS234-22 Systematic Control Testing Program
  • CPS234-25 Internal Audit Review of Information Security Controls

FedRAMP High · 2 controls

  • CA-1 Policy and Procedures
  • CA-2 Control Assessments

FedRAMP Moderate · 2 controls

  • CA-1 Policy and Procedures
  • CA-2 Control Assessments

ISO 27001:2022 · 2 controls

  • 5.35 Independent review of information security
  • 8.34 Protection of information systems during audit testing 

ISO 27002:2022 · 2 controls

  • 5.35 Independent review of information security
  • 8.34 Protection of information systems during audit testing
  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions
  • CPS230-P30 Monitoring, Review and Testing of Control Effectiveness
  • CFTC-SS-20 Production of System Safeguards Books and Records

CMMC 2.0 · 1 control

DORA · 1 control

GDPR · 1 control

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

NIS2 Directive · 1 control

  • Art.32 Cooperate with supervision: inspections, security audits, scans and requests for information and evidence
  • 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

PCI DSS 4.0 · 1 control

  • 11.1.1 11.1.1 Requirement 11 policies and procedures managed

SOC 2 · 1 control

  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)

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: Compliance

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

C5 (Germany) C5-COM-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 34 it maps to, and the evidence behind each claim, over MCP and REST.