Skip to content

PCI DSS requirement 10.4.1.1: why log review must now be automated

By Sam Rivera, Founder, SentinelPanda · October 24, 2026 · 3 min read · PCI DSS

No one reads ten million log lines a day. Version 4.0 stopped pretending they did.

What the requirements say

Requirement 10.4.1 asks for a review, at least daily, of all security events, the logs of every component that stores, processes or transmits account data or could affect its security, the logs of critical system components, and the logs of components that perform security functions such as firewalls, intrusion detection and authentication servers. Requirement 10.4.1.1, assessed since 31 March 2025, adds that the review is performed by automated mechanisms.

Logs from other components are reviewed periodically, at a frequency set by a targeted risk analysis (10.4.2 and 10.4.2.1), and exceptions found in any review must be followed up (10.4.3).

Automation is more than ingestion

  • Coverage: every in-scope log source is actually sending, and you can prove it.
  • Detection: rules that turn raw events into alerts worth a person's time.
  • Routing: each alert reaches someone who is expected to act on it.
  • Disposition: each alert ends with a recorded outcome — false positive, investigated, escalated.
  • Tuning: changes to rules are recorded, so a suppressed alert can be explained later.

10.7.2: noticing when a control stops working

Requirement 10.7.2 used to apply only to service providers. It now applies to everyone. You must detect, alert on and promptly address failures of critical security control systems, including network security controls, intrusion detection or prevention, change-detection mechanisms, anti-malware, physical and logical access controls, audit logging, audit log review, segmentation controls if you use them, and automated security testing tools if you use them.

Requirement 10.7.3 then sets out the response: restore the control, find the cause, document how long it was down, fix the underlying issue, decide whether further action is needed, and resume monitoring.

The silent source problem

The most common real failure is not a missed attack. It is a log source that quietly stopped sending — an agent that crashed, a credential that was rotated, a firewall rule that changed. Nothing alerts, because nothing arrives. A "no events in the last N hours" rule for every critical source closes that gap, and it is simultaneously evidence for 10.4.1.1 and for 10.7.2.

Retention

Requirement 10.5.1 asks you to keep audit logs for at least 12 months, with the most recent three months immediately available for analysis. Check that your SIEM's hot and cold tiers actually match that, because the default retention on many plans is shorter.

What assessors sample

  • The list of in-scope components compared with the list of sources the SIEM is receiving.
  • A sample of alerts and the tickets or notes that closed them.
  • At least one control-failure event and the record of the response.
  • Retention settings.
PCI DSS Requirement 10 explained The PCI DSS compliance calendar SOC 2 logging and monitoring

Run your compliance program in one workspace.