Found Where It Shouldn't Be: Unexpected Cardholder Data Turns Up
Retail tabletop exercise scenario · PCI Cardholder Data Discovery
A data scan surfaces something that shouldn't exist: actual card numbers sitting where they were never supposed to be — a log file, a spreadsheet, an app's debug output, a backup outside the card environment. No attacker, no exfiltration — but a serious failing, because cardholder data escaped the protected environment and has been sitting unprotected and unmonitored, for an unknown length of time.
This beginner-friendly scenario runs card-handling organizations through finding cardholder data where it doesn't belong — the quiet, common, consequential problem payment-security programs must be able to handle. Grounded in the real defined response: confirming what was found (and whether sensitive authentication data is with it), containing without destroying evidence, tracing how the data got there, and the decision of whether it's a one-off stray file or a systematic leak scattering card data across the org. Then proper deletion or migration, fixing the source, and the data-minimization reckoning. Designed to support PCI DSS-aligned data-discovery and incident-response readiness.
1 hrBeginner
Retail & ConsumerPCI DSS
What this scenario tests
- Whether you confirm what was found and contain it without destroying the evidence
- Whether you trace how the data escaped the environment to its source
- Whether you tell a one-off stray file from a systematic leak
- Whether your reckoning strengthens data-discovery and keeps card data where it belongs
Who it's for
IT & Security Team · Operations Team · Legal & Compliance