PCI DSS requirement 12.10: an incident response plan that survives contact
By Sam Rivera, Founder, SentinelPanda · October 24, 2026 · 2 min read · PCI DSS
A plan that has never been tested is a list of good intentions with a version number.
What the plan must contain
- Roles, responsibilities and communication and contact strategies, including notification of the payment brands and acquirers at a minimum.
- Response procedures with specific containment and mitigation steps for different types of incident.
- Business recovery and continuity procedures, and data backup processes.
- An analysis of legal requirements for reporting compromises.
- Coverage of, and responses for, all critical system components.
- Reference to, or inclusion of, the payment brands' own incident response procedures.
Testing, availability and training
The plan is reviewed, updated and tested at least once every 12 months (12.10.2). Specific personnel are available around the clock to respond to suspected incidents (12.10.3). Responders are trained (12.10.4), at a frequency set by a targeted risk analysis (12.10.4.1). And the plan is updated from lessons learned and industry developments (12.10.6), which is easiest to evidence when every test and real incident ends with a short list of changes.
Alerts that must feed it
Requirement 12.10.5 says the plan covers monitoring and responding to alerts from your security monitoring systems, including intrusion detection and prevention, network security controls, change-detection on critical files, detection of unauthorised wireless access points, and — new in 4.0 — the payment-page change-and-tamper mechanism from 11.6.1. If an alert from one of those has no documented path into incident response, the requirement is not met.
12.10.7: PAN where it should not be
- Decide what happens to the data: retrieval, secure deletion, or migration into the defined CDE.
- Determine whether sensitive authentication data is stored alongside it.
- Find out where it came from and how it ended up there.
- Fix the leak or process gap that caused it.
The first hours of a suspected card compromise
Preserve evidence before you clean up — reimaging a server destroys what an investigator needs. Contain without tipping off an attacker who may still be present. Notify your acquirer as your merchant agreement requires; for a confirmed account data compromise, the acquirer or the card brands will often require a PCI Forensic Investigator, and you cannot choose an investigator from outside that programme. Bring in legal counsel early, because breach notification duties under data protection law run on their own clock.
A tabletop that counts
Use a payment-specific scenario rather than a generic ransomware exercise: a skimming script injected into the checkout page, discovered by a customer complaint rather than by your tooling. Walk through who is called, when the acquirer is notified, and how you establish which transactions were exposed. Record the gaps and the changes made, and you have the evidence for 12.10.2 and 12.10.6 in one exercise.