A3.3.1 Prompt detection and alerting of critical security control failures

Failures of critical security control systems must be detected, alerted on and addressed promptly, covering, as a minimum, failures of: IDS/IPS; network security controls; anti-malware solutions; FIM; logical access controls; physical access controls; any segmentation controls in use; audit logging mechanisms; tools that automatically review audit logs; and tools that automatically review code, where used. Related PCI DSS requirements: all twelve. Guidance: a typical failure is a control stopping or not working as intended, such as a firewall losing its rules or going offline. Applies only to designated entities. Objective under the customized approach: not eligible for the customized approach; only the defined approach can be used. Future-dated (bullets on automated audit log review mechanisms and on automated code review tools, where used): treated as a best practice up to 31 March 2025 and mandatory since then; the other bullets are already required.

Source: PCI DSS v4.0.1, A3.3.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.