PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.4.3: 10.4.3 Exceptions and anomalies from log review addressed

Exceptions and anomalies found while reviewing logs must be addressed. Applies to all entities. As good practice, the guidance suggests the process consider how review work is recorded, how exceptions are ranked and prioritized, how they are reported and escalated, and who investigates and carries out remediation. Customized approach objective: suspicious or anomalous activity is acted on.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 61 controls across 24 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 · 6 controls

  • AC-2(12) Account Monitoring for Atypical Usage
  • AU-6 Audit Record Review, Analysis, and Reporting
  • CA-7 Continuous Monitoring
  • IR-4 Incident Handling
  • SI-4 System Monitoring
  • SI-4(4) Inbound and Outbound Communications Traffic

FedRAMP Moderate · 6 controls

  • AC-2(12) Account Monitoring for Atypical Usage
  • AU-6 Audit Record Review, Analysis, and Reporting
  • CA-7 Continuous Monitoring
  • IR-4 Incident Handling
  • SI-4 System Monitoring
  • SI-4(4) Inbound and Outbound Communications Traffic

NIST Cybersecurity Framework 2.0 · 5 controls

ISO 27001:2022 · 4 controls

  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.35 Independent review of information security
  • 8.16 Monitoring activities

ISO 27002:2022 · 4 controls

  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.35 Independent review of information security
  • 8.16 Monitoring activities

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents

CIS Controls v8 · 3 controls

  • CIS-13.11 Tune Security Event Alerting Thresholds
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-8.11 Conduct Audit Log Reviews

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

AWS Well-Architected Security Pillar · 2 controls

  • SEC04-BP03 Correlate and enrich security alerts
  • SEC04-BP04 Initiate remediation for non-compliant resources

Azure Security Benchmark · 2 controls

  • ASBv3-IR-3 Detection and analysis - create incidents based on high-quality alerts
  • ASBv3-IR-4 Detection and analysis - investigate an incident

HIPAA Security Rule · 2 controls

ISO 27701:2019 · 2 controls

  • 5.8.1 Nonconformity and corrective action
  • 6.13.1 Management of information security incidents and improvements

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.11.2e Threat Hunting
  • 3.14.2e Monitor Organizational Systems with Specialized Capabilities

NIST SP 800-66 Rev 2 · 2 controls

ACSC Essential Eight · 1 control

  • E8-APP-ML2 Application Control (ML2)

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-31 Hunt to discover incidents (Very Good)

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

ISO 22301:2019 · 1 control

  • 10.2 Continual improvement

ISO/IEC 42001:2023 · 1 control

  • 10.2 Nonconformity and corrective action

NIST SP 800-161 Rev 1 · 1 control

PCI 3DS Core Security Standard · 1 control

  • P2-5.5.2 P2-5.5.2 Anomalous transaction activity investigated promptly

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

MCP endpointAll PCI DSS 4.0 controls