Once authorization is complete, sensitive authentication data may not be kept at all, and encrypting it does not make storage acceptable. Any SAD the entity receives must be made unrecoverable when the authorization process ends. Guidance notes that SAD may sit briefly in non-persistent memory (RAM) after authorization only where there is a legitimate business need, it never reaches persistent storage, controls keep the memory non-persistent, and it is cleared once the purpose ends. Guidance also defines authorization as finished when the merchant gets a transaction response such as an approval or decline. Applicability: issuers and companies supporting issuing services that have a legitimate business need, documented, for keeping SAD are exempt and are covered instead by Requirement 3.3.3; SAD comprises the elements in 3.3.1.1 to 3.3.1.3. Objective under the customized approach: none, this requirement cannot be met through the customized approach.
This control maps to 30 controls across 10 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.1 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 30 it maps to, and the evidence behind each claim, over MCP and REST.