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.
This control maps to 25 controls across 15 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.6 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 25 it maps to, and the evidence behind each claim, over MCP and REST.