← PCI DSS 4.0.1 · Req 3 — Protect stored account data
3.3 — Sensitive authentication data is not stored after authorisation
Requirement
Sensitive authentication data — full track data, card verification codes (CVV2/CVC2/CID) and PINs/PIN blocks — is not retained after authorisation, even if encrypted, and is rendered unrecoverable once authorisation completes.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| SOC 2 | P4.1 | Use, retention and disposal of personal information (P4.1–P4.3) | data-minimisation data-deletion |
| GDPR | Art.5(1)(b) | Purpose limitation | data-minimisation |
| GDPR | Art.5(1)(c) | Data minimisation | data-minimisation |
| GDPR | Art.5(1)(e) | Storage limitation | data-deletion |
| GDPR | Art.17 | Right to erasure (“right to be forgotten”) | data-deletion |
| GDPR | Art.25 | Data protection by design and by default | data-minimisation |
| CCPA/CPRA | 1798.100(c) | Purpose limitation and data minimisation | data-minimisation |
| CCPA/CPRA | 1798.105 | Right to delete | data-deletion |