EvidenceSheet

9.4.1.1 Secure storage location for offline backups

Offline media backups that contain cardholder data must be kept in a secure location. The guidance describes off-site storage, for instance at a commercial storage provider or an alternate or backup site, as good practice, and notes that backups in a non-secured facility could be lost, stolen or copied. Applicability: entities keeping offline backups with cardholder data. Customized approach objective: unauthorized personnel cannot reach offline backups by unauthorized personnel.

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

4
artefacts
1
held by a system
0
at each review
moderate
to go live
SIEM / log platform
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

  • Tape or disk check-in and check-out logs at the storage site · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Backup media storage procedure naming the secure storage location · Policy repository / GRC workspace
  • Contract and security description for any commercial off-site storage vendor · Vendor register / contract repository
  • Access list for the backup storage room or vault · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); 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

9.4.1 Physical security of all media · 9.4.1.2 Annual review of offline backup location security