C5 (Germany)
C5: Operations

C5 (Germany) C5-OPS-14: Logging and Monitoring - Storage of the Logging Data

Consolidate log data from every source into a central store in an unchangeable and aggregated form for authorised evaluation, delete it once its purpose expires, authenticate between logging servers and logged assets, and transmit over encryption or a dedicated management network.

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

What else in your programme already covers this

This control maps to 49 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.

FedRAMP High · 4 controls

  • AU-11 Audit Record Retention
  • AU-4 Audit Log Storage Capacity
  • AU-6(1) Automated Process Integration
  • AU-9 Protection of Audit Information

FedRAMP Moderate · 4 controls

  • AU-11 Audit Record Retention
  • AU-4 Audit Log Storage Capacity
  • AU-6(1) Automated Process Integration
  • AU-9 Protection of Audit Information

PCI DSS 4.0 · 4 controls

  • 10.3.2 10.3.2 Audit log files protected from modification
  • 10.3.3 10.3.3 Audit logs promptly backed up to central secure storage
  • 10.3.4 10.3.4 File integrity monitoring on audit logs
  • 10.5.1 10.5.1 Keep logs 12 months, latest three months online

ACSC Essential Eight · 3 controls

  • E8-APP-ML2 Application Control (ML2)
  • E8-MFA-ML3 Multi-Factor Authentication - Maturity Level 3
  • E8-UAH-ML3 User Application Hardening - Maturity Level 3
  • SEC04-BP01 Configure service and application logging
  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations
  • SEC10-BP03 Prepare forensic capabilities

CIS Controls v8 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

  • 03.03.03 Audit Record Generation
  • 03.03.06 Audit Record Reduction and Report Generation
  • 03.03.08 Protection of Audit Information

NIST SP 800-53 Rev 5 · 3 controls

  • ASBv3-LT-6 Configure log storage retention
  • LT-5 Centralize security log management and analysis

CMMC 2.0 · 2 controls

  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

NIST SP 800-161 Rev 1 · 2 controls

  • ASD37-33 Capture network traffic (Limited)

HIPAA Security Rule · 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

NIST SP 800-218 · 1 control

SOC 2 · 1 control

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

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