EvidenceSheet

9.4.1 Media with cardholder data physically secured

All media holding cardholder data is physically secured, so that the data it carries cannot be accessed by unauthorized personnel. Sub-requirements extend this to offline media backups being stored in a secure location a

5
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

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Evidence of secure storage for media (locked cabinets, safes, restricted rooms) · Data governance / DLP tooling
  • Records of the periodic review of the offline backup storage location's security · Backup / DR tooling

governing documentDocuments that govern the control

  • Documented procedures for protecting cardholder data that include controls for physically securing all media · Policy repository / GRC workspace
  • Inventory of media holding cardholder data with storage location · Policy repository / GRC workspace
  • Offsite or offline backup storage arrangements and the facility's security description · Policy repository / GRC workspace

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

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.3.4 Visitor log retention · 9.4.1.1 Offline media backup security