TL;DR
- PCI DSS Requirement 12 is the governance layer of v4.0.1, covering policy, targeted risk analysis, scope validation, awareness training, vendor oversight, and incident response.
- Controls that started as future-dated best practices, such as targeted risk analyses and PAN discovery response, have been fully assessed since 31 March 2025.
- Assessors look for dated, owned, repeatable evidence, so Requirement 12 works best as an annual operating calendar.
PCI DSS Requirement 12, titled “Support Information Security with Organizational Policies and Programs,” sets governance expectations for organizations that store, process, or transmit cardholder data or can affect its security. PCI DSS v4.0.1, published by the PCI Security Standards Council (PCI SSC) in June 2024, is the version referenced throughout this article.
Its reach is wider than many teams expect. The standard states that incident response requirements apply to all entities, and that vendor management under 12.8 applies whenever a provider handles account data on an entity’s behalf. Some items, including 12.4, 12.5.2.1, 12.5.3, and 12.9, apply to service providers only. Organizations with distributed environments will find useful scoping context in Ampcus Cyber’s analysis of PCI DSS at scale.
What Does PCI DSS Requirement 12 Require?
Requirement 12 has ten sections, 12.1 to 12.10. The table summarizes each one and the evidence an assessor typically expects.
| Section | What It Requires | Typical Evidence |
| 12.1 | Security policy reviewed every 12 months, with assigned roles and an executive owner | Policy, review records, acknowledgments |
| 12.2 | Acceptable use policies for end-user technologies | Policy, approved product list |
| 12.3 | Targeted risk analyses, plus annual reviews of cryptography and technology | TRAs, cipher inventory, end-of-life plan |
| 12.4 | Executive accountability and quarterly reviews (service providers only) | Charter, review sign-offs |
| 12.5 | In-scope inventory and scope confirmation every 12 months | Data-flow diagrams, inventory |
| 12.6 | Awareness training at hire and annually, including phishing | Training records, acknowledgments |
| 12.7 | Personnel screening before CDE access | HR confirmation |
| 12.8 | Vendor list, agreements, due diligence, annual monitoring, responsibility records | Vendor register, AOCs, matrix |
| 12.9 | Providers support customer compliance (service providers only) | Agreements, AOC, matrix |
| 12.10 | Incident response plan, annual test, 24/7 coverage, training, PAN discovery | Plan, tabletop report, logs |
Most activities repeat every 12 months, so a shared compliance calendar with named owners prevents missed cycles. PCI DSS tolerates a late activity only where a documented process detected the miss, found the cause, and restored the schedule.
How Does Targeted Risk Analysis Work Under Requirement 12.3?
A targeted risk analysis (TRA) is a documented analysis tied to a specific PCI DSS requirement that justifies a flexible control frequency. Requirement 12.3.1 requires each TRA to identify the assets protected, the threats addressed, the factors affecting likelihood and impact, and a justified conclusion, followed by a review at least every 12 months.
A TRA differs from an enterprise risk assessment, which PCI DSS recommends but does not require. Requirements that call for a TRA include 5.2.3.1, 10.4.2.1, 11.6.1, and 12.10.4.1. As a hypothetical example, a merchant that sets its own payment page change-detection frequency under 11.6.1 would document the pages and scripts at risk, the skimming threats, exposure factors such as third-party scripts, and the reasoning behind the chosen interval. The PCI SSC publishes targeted risk analysis guidance and a sample template for this purpose.
How Should Organizations Manage Third-Party Service Providers Under 12.8?
Organizations must keep a list of every third-party service provider (TPSP) and its services, hold written agreements containing the provider’s acknowledgment of responsibility, complete due diligence before engagement, monitor each provider’s PCI DSS compliance status at least every 12 months, and record which requirements the provider, the entity, or both manage.
Two points cause repeated confusion. A compliant provider does not make its customer compliant. A provider’s PCI AOC also differs from the written acknowledgment required under 12.8.2, so both are needed. A responsibility matrix closes the gap where each party assumes the other owns a control, and the PCI SSC’s Third-Party Security Assurance supplement includes a sample. The PCI SSC FAQ on TPSP evidence explains what providers are expected to supply. Customers should confirm that an AOC covers the specific services they use and ask whether the provider relies on other providers. A modern TPRM program with risk scoring helps turn this annual check into a continuous one.
What Should an Incident Response Plan Include Under 12.10?
Requirement 12.10.1 requires a plan that is ready to activate and includes:
- Roles, responsibilities, and contact strategies, including notification of payment brands and acquirers.
- Containment and mitigation procedures for different incident types.
- Business recovery, continuity, and data backup processes.
- Analysis of legal reporting requirements.
- Coverage of all critical system components, with reference to payment brand procedures.
Other sub-requirements extend the plan. Organizations must review and test it every 12 months (12.10.2), designate 24/7 responders (12.10.3), train responders at a frequency set by a TRA (12.10.4.1), and respond to alerts from monitoring tools, including payment page tamper detection (12.10.5). Plans must also evolve from lessons learned (12.10.6) and include procedures for PAN found where it should not be (12.10.7). Reliable alerts depend on sound logging, which Ampcus Cyber covers in PCI DSS Requirement 10.
Where Do Organizations Struggle With Requirement 12?
Most findings trace to evidence that is outdated, unowned, or inconsistent with how the environment operates. Common gaps include:
- Policy reviews done informally, with no dated sign-off for 12.1.2.
- TRAs that are missing or generic, with no justification for the chosen frequency.
- Vendor registers without responsibility matrices, or AOCs never checked against the services in use.
- Scope confirmations (12.5.2) completed without updated data-flow diagrams or a search for PAN outside the CDE.
- Incident response plans tested once on paper, with stale contact lists and unclear 24/7 coverage.
- Awareness training that omits phishing, social engineering, and acceptable use (12.6.3.1 and 12.6.3.2).
What Should Organizations Do Next?
Test Requirement 12 against v4.0.1 one sub-requirement at a time, then build the annual calendar and assign an owner to each recurring activity:
- Inventory existing evidence and mark what is dated, owned, and current.
- Document a TRA for every requirement that allows a flexible frequency.
- Rebuild the vendor register with AOC scope checks and responsibility matrices.
- Run an incident response tabletop that includes PAN discovery and payment page alerts.
- Confirm scope with refreshed data-flow diagrams.
Ampcus Cyber’s PCI QSA team supports this work through PCI DSS compliance services, covering gap assessment, remediation guidance, vendor AOC review, and certification support.
Conclusion
Requirement 12 gives every other PCI DSS control its ownership, cadence, and accountability. Policies, targeted risk analyses, vendor oversight, and a tested incident response plan show an assessor that security operates continuously. Organizations that treat Requirement 12 as a calendar of owned, evidenced activities reduce audit friction and respond faster when incidents occur.
| Book a PCI DSS Requirement 12 gap assessment with Ampcus Cyber’s QSA team to test your policies, targeted risk analyses, vendor oversight, and incident response evidence against v4.0.1 before your next assessment. |
People Also Ask
How many PCI DSS requirements are there, and what does Requirement 12 cover?
There are 12 principal requirements under six goals, and Requirement 12 covers policies, risk analysis, scope, training, vendor management, and incident response.
Is PCI DSS mandatory, and who must comply?
It is an industry standard, not a statute. Payment brands and acquirers decide who must comply or validate, and it applies to anyone handling cardholder data or affecting its security.
What is a PCI DSS responsibility matrix?
It shows which requirements the entity, its provider, or both own, as required by 12.8.5.
Do you need an incident response plan for PCI DSS?
Yes, it applies to all entities, with an annual test and 24/7 responders under 12.10.
How often is security awareness training required?
At hire and every 12 months, plus an annual policy acknowledgment (12.6.3).
Enjoyed reading this blog? Stay updated with our latest exclusive content by following us on Twitter and LinkedIn.










