EvidenceSheet

9.4.6 Destruction of hard-copy materials

Hard-copy materials containing cardholder data must be destroyed once they are no longer required for legal or business purposes, in this way: they are shredded with a cross-cut shredder, burned or pulped so the cardholder data cannot be reconstructed; and while awaiting destruction they are kept in secure storage containers (the guidance suggests, for example, locked to-be-shredded bins). Applicability: these media destruction rules are separate from Requirement 3.2.1, which deals with securely deleting cardholder data once it passes the entity's retention period. Objective under the customized approach: no one can retrieve cardholder data from media once destroyed, or from media still awaiting destruction.

Source: PCI DSS v4.0.1, 9.4.6. 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
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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

none for this control

periodic reviewEvidence produced at each review

  • Certificates of destruction from a shredding vendor · Vendor register / contract repository
  • Observation of locked shred consoles and their key custody · Data governance / DLP tooling

governing documentDocuments that govern the control

  • Media destruction policy specifying cross-cut shredding, incineration or pulping · Policy repository / GRC workspace
  • Shredder specifications showing cross-cut operation · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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

9.4.5.1 Annual inventories of electronic media · 9.4.7 Destruction of electronic media