Electronic media containing cardholder data must be destroyed once no longer required for business or legal reasons, using one of these methods: the media itself is physically destroyed; or the cardholder data is made unrecoverable so it cannot be reconstructed. The guidance notes that standard operating system deletion usually leaves data recoverable and gives secure wiping to industry standards, degaussing or physical destruction such as shredding or grinding disks as examples. 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. Customized approach objective: no one can retrieve cardholder data from media after it has been wiped or destroyed.
This control maps to 46 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
PCI DSS 4.0 9.4.7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 46 it maps to, and the evidence behind each claim, over MCP and REST.