CIS Controls v8
CIS Control 8: Audit Log Management

CIS Controls v8 CIS-8.1: Establish and Maintain an Audit Log Management Process

Set up and keep a process for managing audit logs that sets out what the enterprise needs to log and, as a minimum, how logs from enterprise assets are gathered, reviewed and kept. Revisit the documentation each year, or sooner when a major change in the enterprise could affect this Safeguard.

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 7 controls

HIPAA Security Rule · 5 controls

NIST SP 800-66 Rev 2 · 5 controls

CMMC 2.0 · 4 controls

FedRAMP High · 4 controls

  • AU-1 Policy and Procedures
  • AU-5 Response to Audit Logging Process Failures
  • AU-7 Audit Record Reduction and Report Generation
  • SA-1 Policy and Procedures

FedRAMP Moderate · 4 controls

  • AU-1 Policy and Procedures
  • AU-5 Response to Audit Logging Process Failures
  • AU-7 Audit Record Reduction and Report Generation
  • SA-1 Policy and Procedures
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • 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-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

PCI DSS 4.0 · 4 controls

  • 10.3.2 10.3.2 Audit log files protected from modification
  • 10.5.1 10.5.1 Keep logs 12 months, latest three months online
  • 12.4.1 12.4.1 Executive responsibility for a PCI DSS compliance program
  • 4.1.1 4.1.1 Requirement 4 policies and procedures maintained and communicated

SOC 2 · 4 controls

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-P4.2 P4.2 Retaining personal information
  • SEC04-BP01 Configure service and application logging
  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations

C5 (Germany) · 2 controls

  • C5-OPS-10 Logging and Monitoring - Concept
  • C5-OPS-16 Logging and Monitoring - Configuration

ISO 27701:2019 · 2 controls

  • 5.6 Operation
  • 6.9.4 Logging and monitoring
  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment
  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy

ISO 22301:2019 · 1 control

ISO 27001:2022 · 1 control

ISO 27002:2022 · 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 CIS Control 8: Audit Log Management

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-8.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 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. 240 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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