3.5.1 PAN rendered unreadable wherever stored
PAN is rendered unreadable anywhere it is stored using one of: one-way hashes, truncation, index tokens with secure pads, or strong cryptography with key management.
5
artefacts
2
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Encryption configuration · Cloud console / configuration management
- Sample database extracts showing rendered output · Document repository
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Inventory of PAN storage locations with method per location · Policy repository / GRC workspace
- Tokenisation vendor SAQ · Vendor register / contract repository
- Hash algorithm and salt documentation · Document repository
First move
Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Cleartext PAN in backups
- Reversible hash without keyed function
- Mixed methods inconsistent
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet3.4.2 Technical controls prevent unauthorized PAN copy · 3.5.1.1 Hashes of PAN use keyed cryptographic functions