PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.4.1.1: Automated mechanisms used for audit log review

What does 10.4.1.1 require?

Audit log reviews must be carried out using automated mechanisms. Applies to all entities. The guidance gives log collection, parsing and alerting tools, central log management, event log analyzers and SIEM solutions as examples, and recommends a baseline of normal activity and periodic tuning of tool settings. Objective under the customized approach: a consistent, repeatable mechanism picks up activity that may be suspicious or anomalous. 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 45 controls across 17 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 · 9 controls

  • AC-17(1) Monitoring and Control
  • AC-2(4) Automated Audit Actions
  • AU-6(1) Automated Process Integration
  • AU-7 Audit Record Reduction and Report Generation
  • AU-7(1) Automatic Processing
  • IR-6(1) Automated Reporting
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
  • SI-4(16) System Monitoring | Correlate Monitoring Information (SI-4(16))
  • SI-4(2) Automated Tools and Mechanisms for Real-Time Analysis

FedRAMP Moderate · 9 controls

  • AC-17(1) Monitoring and Control
  • AC-2(4) Automated Audit Actions
  • AU-6(1) Automated Process Integration
  • AU-7 Audit Record Reduction and Report Generation
  • AU-7(1) Automatic Processing
  • IR-6(1) Automated Reporting
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
  • SI-4(16) System Monitoring | Correlate Monitoring Information (SI-4(16))
  • SI-4(2) Automated Tools and Mechanisms for Real-Time Analysis

CMMC 2.0 · 5 controls

NIST SP 800-53 Rev 5 · 3 controls

  • ASBv3-LT-1 Enable threat detection capabilities
  • LT-5 Centralize security log management and analysis

C5 (Germany) · 2 controls

  • C5-OPS-13 Logging and Monitoring - Identification of Events
  • C5-OPS-16 Logging and Monitoring - Configuration

CIS Controls v8 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • 03.03.05 Audit Record Review, Analysis, and Reporting
  • 03.03.06 Audit Record Reduction and Report Generation

SOC 2 · 2 controls

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • ASD37-28 Continuous incident detection and response (Excellent)

ISO 27001:2022 · 1 control

  • 8.16 Monitoring activities

ISO 27002:2022 · 1 control

  • 8.16 Monitoring activities

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

NIST SP 800-172 · 1 control

  • 3.11.3e Advanced Automation and Analytics Capabilities

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