Any SAD kept in electronic form before authorization completes must be encrypted with strong cryptography. Guidance suggests using a different key for SAD than the one used for PAN, without needing to separately encrypt PAN embedded within SAD such as track data. Applicability: whether SAD may be stored before authorization at all is decided by the bodies running compliance programmes (for example payment brands and acquirers), who may set further criteria; the requirement covers all SAD storage even where no PAN is present; Requirement 3.2.1 adds retention obligations for pre-authorization SAD; issuers and issuing-service companies with a legitimate, documented business need are exempt and follow 3.3.3; it does not change how PIN blocks are managed nor require a correctly encrypted PIN block to be encrypted again. Objective under the customized approach: none, this requirement cannot be met through the customized approach. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 12 controls across 12 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 3.3.2 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 12 it maps to, and the evidence behind each claim, over MCP and REST.