3.1 Stored account data protection processes and roles
Requirement 3.1 asks for current policies and procedures for protecting stored account data and documented roles for data retention, encryption and key management activities.

Requirement 3 covers protection of stored account data: retention limits, no stored sensitive authentication data, PAN masking and unreadability, and key management. Each page covers one second-level requirement.
Requirement 3.1 asks for current policies and procedures for protecting stored account data and documented roles for data retention, encryption and key management activities.
Requirement 3.2 keeps stored account data to a minimum through retention and disposal policies, defined retention periods with business justification, secure deletion, and a quarterly check that expired data is gone.
Requirement 3.3 forbids keeping sensitive authentication data (full track data, card verification codes, PINs and PIN blocks) after authorization, even encrypted, and sets extra rules for issuers and for SAD held before authorization.
Requirement 3.4 limits who can see full PAN on screens, receipts and reports (masking to at most the BIN and last four digits) and blocks copying or moving PAN through remote-access technologies without authorization.
Requirement 3.5 requires stored PAN to be unreadable wherever it is kept, using keyed hashes, truncation, index tokens or strong encryption, and limits disk-level encryption to removable media unless PAN is also protected another way.
Requirement 3.6 secures the cryptographic keys that protect stored account data: few custodians, key-encrypting keys at least as strong as data keys and stored separately, approved storage forms, and a documented cryptographic architecture for service providers.
Requirement 3.7 defines the key management lifecycle for keys protecting stored account data: generation, distribution, storage, cryptoperiods, retirement and replacement, split knowledge and dual control, and custodian acknowledgment.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.