EvidenceSheet
PCI DSS v4.0.1 · Req 3: Protect Stored Account Data

3.3.1.3 PIN and PIN block not retained after authorization

Neither the PIN (personal identification number) nor the PIN block may be kept after authorization completes. Applicability: although PIN blocks are encrypted during normal transaction processing, re-encrypting a PIN block does not make it acceptable to store once authorization has finished. Guidance lists the data sources to check, including incoming transaction data, all logs, history and trace files, database schemas, database and data store contents, and memory or crash dump files. Customized approach objective: none, this requirement cannot be met through the customized approach.

Source: PCI DSS v4.0.1, 3.3.1.3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

4
artefacts
2
held by a system
1
at each review
easy
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Discovery scan output covering PIN block formats in data stores and logs · Vulnerability scanner / patch tooling
  • Configuration of HSM or switch logging excluding PIN block fields · Key management / PKI

periodic reviewEvidence produced at each review

  • Review of trace files and crash dumps from PIN-accepting systems · Document repository

governing documentDocuments that govern the control

  • Transaction message flow showing PIN block is discarded after the authorization response · Document repository

First move

Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.

Common gaps auditors find

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 sheet

3.3.1.2 Card verification code not retained after authorization · 3.3.2 Pre-authorization SAD stored electronically is strongly encrypted