Requirement 3: Protecting Stored Cardholder Data
What you'll learn: How PCI-DSS Requirement 3 mandates the use of encryption, truncation, and retention policies to protect stored payment card data while prohibiting the storage of sensitive authentication data.
The Core Protection Challenge
After securing your network and configurations (Requirements 1 and 2), PCI-DSS focuses on what happens to cardholder data at rest. Think of this like a bank vault: it's not enough to have guards and locked doors—you must also protect what's inside the vault itself.
Three Pillars of Data Protection
Encryption
All stored Primary Account Numbers (PAN) must be rendered unreadable through strong cryptographic methods. This includes full-disk encryption, database-level encryption, or file/column-level encryption using industry-standard algorithms (AES-256, RSA 2048+).
Truncation and Masking
When full PAN storage isn't necessary, truncation displays only the first six and last four digits (e.g., 123456******7890). This minimizes exposure while maintaining business functionality for customer service and transaction tracking.
Retention Policies
Store cardholder data only as long as business or legal requirements demand, then securely delete it. This is your data minimization strategy—the less you store, the less you risk.
The Absolute Prohibition
Sensitive Authentication Data (SAD) from the magnetic stripe or chip—including full track data, CVV2/CVC2 codes, and PIN blocks—must never be stored after authorization, even if encrypted. This is non-negotiable; there are no exceptions.
The Analogy
Imagine stored cardholder data as confidential documents. Encryption is your locked filing cabinet, truncation is redacting all but essential information, and retention policies are your document shredder schedule. SAD? Those are documents you burn immediately after reading—no copies, ever.
Key Takeaway: PCI-DSS Requirement 3 mandates strong encryption for stored PANs, truncation where appropriate, minimal retention periods, and absolute prohibition of storing sensitive authentication data post-authorization.