Neither the PIN (personal identification number) nor the PIN block may be kept after authorization completes. Applicability: although PIN blocks are encrypted during normal transaction processing, re-encrypting a PIN block does not make it acceptable to store once authorization has finished. Guidance lists the data sources to check, including incoming transaction data, all logs, history and trace files, database schemas, database and data store contents, and memory or crash dump files. Customized approach objective: none, this requirement cannot be met through the customized approach.
This control maps to 6 controls across 5 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.3 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 6 it maps to, and the evidence behind each claim, over MCP and REST.