11.1.1 Requirement 11 policies and procedures managed

Every security policy and operational procedure named anywhere in Requirement 11 (security testing of systems and networks) must satisfy four conditions: it is written down, it is maintained so it stays current, it is actually followed in practice, and every affected party is aware of it. In practice these are the documents behind the Requirement 11 topics (wireless detection, vulnerability scanning, penetration testing, intrusion and change detection, payment page monitoring). Guidance (good practice): consider revising the documents soon after a change in processes, technology or business goals, not only on a periodic cycle. Customized approach objective: personnel understand and follow defined expectations, controls and oversight for Requirement 11 work, so that supporting activities are repeatable, consistent and aligned with what management intends.

Source: PCI DSS v4.0.1, 11.1.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.