No complete track contents (from the magnetic stripe, the equivalent chip data, or another source) may be kept once authorization completes. Applicability: in the ordinary course of business an entity may need to keep only four elements taken from the track: the PAN (primary account number), the cardholder name, the service code and the expiration date, and should store just those it needs, securely. Guidance lists data sources to check, such as inbound transaction feeds, every kind of log (transaction, history, debug and error), history and trace files, schemas of databases, the contents of databases and of on-premise or cloud data stores, and memory or crash dumps. Objective under the customized approach: none, this requirement cannot be met through the customized approach.
This control maps to 25 controls across 8 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.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 25 it maps to, and the evidence behind each claim, over MCP and REST.