PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.3.2: 10.3.2 Audit log files protected from modification

Audit log files must be protected so that individuals cannot modify them. The testing procedure looks at physical segregation, network segregation and/or access control mechanisms as the means. Applies to all entities. The guidance advises protecting logs on the originating systems and wherever else they are stored, and keeping them out of publicly accessible locations, because unprotected logs cannot be relied on after a compromise. Objective under the customized approach: personnel cannot alter stored activity records.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

SOC 2 · 4 controls

  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

FedRAMP High · 3 controls

  • AU-9 Protection of Audit Information
  • CP-9(8) System Backup | Cryptographic Protection (CP-9(8))
  • MA-4 Nonlocal Maintenance

FedRAMP Moderate · 3 controls

  • AU-9 Protection of Audit Information
  • CP-9(8) System Backup | Cryptographic Protection (CP-9(8))
  • MA-4 Nonlocal Maintenance

ISO 27002:2022 · 3 controls

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 27001:2022 · 2 controls

ISO 27701:2019 · 2 controls

  • 6.9.4 Logging and monitoring
  • 7.2.8 Records related to processing PII
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved
  • E8-APP-ML2 Application Control (ML2)
  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations

HIPAA Security Rule · 1 control

ISO/IEC 42001:2023 · 1 control

  • 7.5.3 Control of documented information
  • 03.03.08 Protection of Audit Information
  • P1-7.2.5 P1-7.2.5 Audit logs protected from alteration

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