Use whenever tests must prove payment card handling meets PCI DSS v4.0: no stored or logged CVV, full card number (PAN), track data or PIN, card data only over strong TLS, cardholder data environment boundaries and segmentation, key management, SAQ level, scope reduction with hosted fields.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Companion to pci-dss-control-test-author/SKILL.md, Step 7. PCI DSS scope
reduction is the highest-leverage cost saving: every system removed from the
cardholder data environment (CDE) is a system you no longer have to assess.
Prefer tokenization at the storage boundary. The four is_* checks in Step 3's
test_pan_stored_encrypted are an OR because pre-existing systems may already use
encryption, truncation, or hashing, but for new storage paths pick tokenization and
treat encryption / truncation / hashing as escape hatches for when tokenization is
not feasible. This keeps the number of systems that ever hold recoverable PAN as
small as possible, which is the whole point of scope reduction.