PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.7.1: 10.7.1 Service providers detect critical control failures (superseded)

Service providers only (an additional requirement). When a critical security control system fails, the failure must be detected, alerted and addressed promptly, covering at least failures of: IDS/IPS; network security controls; anti-malware solutions; FIM; logical access controls; physical access controls; any segmentation controls in use; and audit logging mechanisms. Applicability: relevant only where the assessed entity is a service provider. This remains a numbered requirement in v4.0.1; Requirement 10.7.2 supersedes it after 31 March 2025. Objective under the customized approach: any failure of a critical security control system is spotted and dealt with promptly.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 64 controls across 16 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-2(12) Account Monitoring for Atypical Usage
  • AU-5 Response to Audit Logging Process Failures
  • IR-1 Policy and Procedures
  • SC-7(8) Route Traffic to Authenticated Proxy Servers
  • SI-4 System Monitoring
  • SI-4(5) System-Generated Alerts
  • SI-5 Security Alerts, Advisories, and Directives
  • SI-6 Security and Privacy Function Verification (SI-6)
  • SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 9 controls

  • AC-2(12) Account Monitoring for Atypical Usage
  • AU-5 Response to Audit Logging Process Failures
  • IR-1 Policy and Procedures
  • SC-7(8) Route Traffic to Authenticated Proxy Servers
  • SI-4 System Monitoring
  • SI-4(5) System-Generated Alerts
  • SI-5 Security Alerts, Advisories, and Directives
  • SI-6 Security and Privacy Function Verification (SI-6)
  • SI-7(7) Integration of Detection and Response

CIS Controls v8 · 7 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-13.11 Tune Security Event Alerting Thresholds
  • CIS-13.7 Deploy a Host-Based Intrusion Prevention Solution
  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-8.11 Conduct Audit Log Reviews
  • CIS-8.9 Centralize Audit Logs

NIST SP 800-53 Rev 5 · 7 controls

ISO 27001:2022 · 6 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.7 Threat intelligence
  • 8.15 Logging
  • 8.16 Monitoring activities

NIST Cybersecurity Framework 2.0 · 5 controls

  • NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
  • NIST-CSF-DE.AE-07 Cyber threat intelligence and other contextual information are integrated into the analysis
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

ISO 27002:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation
  • 5.26 Response to information security incidents
  • 8.15 Logging
  • 8.16 Monitoring activities

CMMC 2.0 · 3 controls

ISO 27701:2019 · 3 controls

  • 5.7.1 Monitoring, measurement, analysis and evaluation
  • 6.13.1 Management of information security incidents and improvements
  • 6.9.4 Logging and monitoring

SOC 2 · 3 controls

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.4 CC7.4 Responding to security incidents

ISO 22301:2019 · 2 controls

  • 10.2 Continual improvement
  • 9.1 Monitoring, measurement, analysis and evaluation

ISO/IEC 42001:2023 · 2 controls

  • 10.2 Nonconformity and corrective action
  • 9.1 Monitoring, measurement, analysis and evaluation

AWS Well-Architected Security Pillar · 1 control

  • SEC04-BP04 Initiate remediation for non-compliant resources

Azure Security Benchmark · 1 control

  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

  • 03.03.04 Response to Audit Logging Process Failures

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

MCP endpointAll PCI DSS 4.0 controls