PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.3.1: 10.3.1 Audit log read access limited to job need

Read access to audit log files must be limited to people whose job requires it. Applies to all entities. The guidance adds that this covers log files on the originating systems and anywhere else they are kept, and recommends need-to-know access control plus physical or network segregation as good practice. Customized approach objective: unauthorized personnel cannot reach stored activity records.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

SOC 2 · 3 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-P5.1 P5.1 Data subject access

CMMC 2.0 · 2 controls

FedRAMP High · 2 controls

  • AU-9 Protection of Audit Information
  • AU-9(4) Access by Subset of Privileged Users

FedRAMP Moderate · 2 controls

  • AU-9 Protection of Audit Information
  • AU-9(4) Access by Subset of Privileged Users

ISO 27001:2022 · 2 controls

ISO 27002:2022 · 2 controls

  • 8.15 Logging
  • 8.3 Information access restriction

ISO 27701:2019 · 2 controls

  • 6.6.2 User access management
  • 6.9.4 Logging and monitoring
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle

C5 (Germany) · 1 control

  • C5-OPS-12 Logging and Monitoring - Access, Storage and Deletion
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
  • 03.03.08 Protection of Audit Information

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