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

3.4.1 PAN masked on display except for authorized roles

Whenever PAN is shown, it must be masked so that no more than the BIN and the last four digits appear, and only staff with a legitimate business need may view more digits than that. Guidance advises showing only as many digits as each business function requires (for example only the last four, or only the BIN for routing), and stresses that masking (hiding digits on display while the full number may remain stored) differs from truncation (digits removed and unrecoverable). Applicability: stricter legal or payment brand rules for displays, such as POS receipt requirements, still apply; this covers PAN on screens, paper receipts, printouts and similar, and is separate from Requirement 3.5.1 on protecting PAN in storage, processing or transmission. Customized approach objective: PAN displays show the smallest number of digits needed for a defined business need.

Source: PCI DSS v4.0.1, 3.4.1. 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.

5
artefacts
2
held by a system
1
at each review
moderate
to go live
Identity provider / directory
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

  • Application role configuration showing masking rules by role · Identity provider / directory
  • Masking and truncation standard referencing payment brand receipt rules · Identity provider / directory

periodic reviewEvidence produced at each review

  • Sample printed receipts and reports showing masked PAN · Identity provider / directory

governing documentDocuments that govern the control

  • Documented list of roles permitted to see more than BIN and last four digits, with business need per role · Policy repository / GRC workspace
  • Screenshots of PAN displays for authorized and unauthorized users · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

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.3 Issuer SAD storage limited, justified and encrypted · 3.4.2 Remote access blocks copying or relocating PAN