C5 (Germany)
C5: Operations

C5 (Germany) C5-OPS-10: Logging and Monitoring - Concept

Establish written logging and monitoring policies for systems in the provider's area of responsibility that define which events could breach protection goals, how logs are activated, paused and stopped, their purpose and retention, role responsibilities, time synchronisation and legal obligations.

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

What else in your programme already covers this

This control maps to 54 controls across 27 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 SP 800-53 Rev 5 · 5 controls

FedRAMP High · 4 controls

  • AU-1 Policy and Procedures
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • CA-7 Continuous Monitoring

FedRAMP Moderate · 4 controls

  • AU-1 Policy and Procedures
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • CA-7 Continuous Monitoring
  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy
  • LT-3 Enable logging for security investigation
  • LT-5 Centralize security log management and analysis

CIS Controls v8 · 3 controls

  • CIS-8.1 Establish and Maintain an Audit Log Management Process
  • CIS-8.2 Collect Audit Logs
  • CIS-8.9 Centralize Audit Logs
  • NIST-CSF-DE.AE-03 Information is correlated from multiple sources
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

PCI DSS 4.0 · 3 controls

  • 10.1.1 10.1.1 Requirement 10 policies and procedures maintained and in use
  • 10.2.1 10.2.1 Audit logging enabled on all system components
  • 10.3.3 10.3.3 Audit logs promptly backed up to central secure storage
  • ASD37-28 Continuous incident detection and response (Excellent)
  • ASD37-33 Capture network traffic (Limited)

CMMC 2.0 · 2 controls

HIPAA Security Rule · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components

APRA CPS 234 · 1 control

  • CPS234-30 Detection and Response Mechanisms
  • SEC04-BP01 Configure service and application logging

DORA · 1 control

ISO 27001:2022 · 1 control

ISO 27002:2022 · 1 control

ISO 27017:2015 · 1 control

  • 12.4 Logging and monitoring

ISO 27018:2019 · 1 control

  • 12.4 Logging and monitoring

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

NIS2 Directive · 1 control

  • Art.23.4.b Submit an incident notification within 72 hours, with an initial assessment and indicators of compromise

SOC 2 · 1 control

  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies

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

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

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