PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.5.1: 10.5.1 Keep logs 12 months, latest three months online

Audit log history must be kept for at least 12 months, and at least the latest three months must be ready for immediate analysis. Applies to all entities. The guidance explains that compromises often stay undetected for a long time, and gives storing logs online, archiving them or restoring them quickly from backup as examples of keeping logs immediately available. Customized approach objective: historical activity records can be used straight away to support incident response and are held for at least 12 months.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

CIS Controls v8 · 4 controls

  • CIS-3.4 Enforce Data Retention
  • CIS-8.1 Establish and Maintain an Audit Log Management Process
  • CIS-8.10 Retain Audit Logs
  • CIS-8.3 Ensure Adequate Audit Log Storage

ISO 27701:2019 · 4 controls

  • 7.2.8 Records related to processing PII
  • 7.4.3 Accuracy and quality
  • 7.4.5 PII de-identification and deletion at the end of processing
  • 7.4.7 Retention

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC6.5 CC6.5 Protecting data on assets until disposal
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-P4.2 P4.2 Retaining personal information
  • SOC2-PI1.1 PI1.1 Quality information about processing objectives, data definitions and specifications

FedRAMP High · 3 controls

  • AU-11 Audit Record Retention
  • AU-4 Audit Log Storage Capacity
  • SI-12 Information Management and Retention

FedRAMP Moderate · 3 controls

  • AU-11 Audit Record Retention
  • AU-4 Audit Log Storage Capacity
  • SI-12 Information Management and Retention

C5 (Germany) · 2 controls

  • C5-OPS-12 Logging and Monitoring - Access, Storage and Deletion
  • C5-OPS-14 Logging and Monitoring - Storage of the Logging Data

CMMC 2.0 · 2 controls

ISO 27002:2022 · 2 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • ASD37-33 Capture network traffic (Limited)
  • CFTC-SS-20 Production of System Safeguards Books and Records

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

  • 7.5.3 Control of documented information

ISO 27001:2022 · 1 control

  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring
  • P1-7.2.6 P1-7.2.6 Log retention of one year, three months at hand

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 Req 10: Logging and Monitoring

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 10.5.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 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. 415 were rejected on the ISO 27001:2022 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.