Requirement 9 · Restrict physical access to cardholder data

9.4 Media with cardholder data is securely stored, accessed, distributed and destroyed

SCOPEEVIDENCERISKEVIDENCETESTEVIDENCEREPORTEVIDENCEAUDIT TRAIL9.4 Audit PathPOLICY / CONTROL / EVIDENCE / REVIEW

How to meet it

Classify, secure, track and securely destroy media holding card data.

Defined requirements

The individual PCI DSS v4.0.1 requirements under 9.4, in plain English.

9.4.1All media containing cardholder data is physically secured.
9.4.1.1Offline media backups holding cardholder data are kept in a secure location.
9.4.1.2The offline backup location security is reviewed at least every 12 months.
9.4.2All media with cardholder data is classified by sensitivity.
9.4.3Media sent outside the facility is logged, sent by trackable secure courier, and recorded in offsite tracking logs.
9.4.4Management approves all media with cardholder data moved outside the facility.
9.4.5Inventory logs of all electronic media with cardholder data are maintained.
9.4.5.1Media inventories are performed at least every 12 months.
9.4.6Hard-copy materials no longer needed are destroyed by cross-cut shredding, incineration, or pulping.
9.4.7Electronic media no longer needed is destroyed or the data rendered unrecoverable.

Policy templates for this control

Use these starting documents to turn the control into evidence. Adapt each template to your scope, systems, legal obligations and actual operating process.

Open the control-to-policy map
Back to Requirement 9, or see PCI DSS templates. To run PCI controls with automation, read how AI manages controls.