PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.7.1: Critical security control failure detection (SP)

Additional requirement for service providers: failures of critical security control systems are detected, alerted, and addressed promptly, including responses documented.

What else in your programme already covers this

This control maps to 78 controls across 19 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. a. Verify the correct operation of [Assignment: organization-defined security and privacy functions]; b. Perform the verification of the functions specified in SI-6a [Selection (one or more): [Assignment: organization-defined system
  • 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. a. Verify the correct operation of [Assignment: organization-defined security and privacy functions]; b. Perform the verification of the functions specified in SI-6a [Selection (one or more): [Assignment: organization-defined system
  • 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

  • NIST800-AU-13 Monitoring for Information Disclosure. Monitor [organization-defined] [organization-defined] for evidence of unauthorized disclosure of organizational information; and If an information disclosure is discovered: Notify [organization-defined] ; and Take the following additional actions: [organization-defined]
  • NIST800-AU-5 Response to audit logging process failures
  • NIST800-CA-7 Continuous monitoring
  • NIST800-IR-4 Incident handling
  • NIST800-RA-10 Threat hunting
  • NIST800-SI-4 System monitoring
  • NIST800-SI-6 Security and Privacy Function Verification. Verify the correct operation of [organization-defined]; Perform the verification of the functions specified in SI-6a [organization-defined]; Alert [organization-defined] to failed security and privacy verification tests; and [organization-defined] when anomalies

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 SP 800-53 Revision 5.1 HIGH · 6 controls

  • AC-2(12) Account Monitoring for Atypical Usage
  • AU-5 Response to Audit Logging Process Failures
  • IR-1 Policy and Procedures
  • SI-4 System Monitoring
  • SI-5 Security Alerts, Advisories, and Directives
  • SI-6 Security and Privacy Function Verification. a. Verify the correct operation of [Assignment: organization-defined security and privacy functions]; b. Perform the verification of the functions specified in SI-6a [Selection (one or more): [Assignment: organization-defined system

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

NIST SP 800-53 Rev 5 LOW · 4 controls

  • AU-5 Response to Audit Logging Process Failures
  • IR-1 Policy and Procedures
  • SI-4 System Monitoring
  • SI-5 Security Alerts, Advisories, and Directives

NIST SP 800-53 Rev 5 MODERATE · 4 controls

  • AU-5 Response to Audit Logging Process Failures
  • IR-1 Policy and Procedures
  • SI-4 System Monitoring
  • SI-5 Security Alerts, Advisories, and Directives

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 Detection and monitoring procedures for security events are in place
  • SOC2-CC7.2 Monitors system components for anomalies indicating malicious acts
  • SOC2-CC7.4 Responds to identified security incidents through defined procedures

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 249 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202255.8% covered · 110 gapsIf you hold FedRAMP Moderate55.4% covered · 111 gapsIf you hold NIST SP 800-53 Rev 553.4% covered · 116 gapsIf you hold ISO 27002:202248.6% covered · 128 gapsIf you hold CIS Controls v843% covered · 142 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.141% covered · 147 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 78 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls