PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.4.2.1: 10.4.2.1 Periodic log review frequency set by targeted risk analysis

The frequency for periodically reviewing logs of every other system component (those outside 10.4.1) must be set by the entity's own targeted risk analysis, and that analysis must be carried out in line with every element specified in Requirement 12.3.1. Applies to all entities. The guidance suggests criteria such as how complex the environment is, how many types of systems need evaluating and what those systems do. Objective under the customized approach: reviews of lower-risk components' logs happen often enough to address the entity's risk. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 15 controls across 9 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 · 2 controls

  • RA-3 Risk Assessment
  • SI-4(16) System Monitoring | Correlate Monitoring Information (SI-4(16))

FedRAMP Moderate · 2 controls

  • RA-3 Risk Assessment
  • SI-4(16) System Monitoring | Correlate Monitoring Information (SI-4(16))

HIPAA Security Rule · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)

ISO 27001:2022 · 1 control

  • 5.35 Independent review of information security

ISO 27002:2022 · 1 control

  • 5.35 Independent review of information security

ISO 27701:2019 · 1 control

  • 5.6.2 Information security risk assessment

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.4.2.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.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll PCI DSS 4.0 controls