Cardholder Data and Sensitive Authentication Data
You'll learn the critical distinction between cardholder data (CHD) and sensitive authentication data (SAD), and why this difference determines how (and if) you can store payment information.
Understanding the Two Categories
Under PCI-DSS, payment card information falls into two distinct buckets, each with vastly different security rules.
Cardholder Data (CHD) is information that directly identifies a cardholder:
- Primary Account Number (PAN) – the 14-19 digit card number
- Cardholder name
- Expiration date
- Service code (sometimes)
Think of CHD as the "receipt data" – what you'd see on a printed transaction receipt.
Sensitive Authentication Data (SAD) is used to authenticate cardholders during transactions:
- Full magnetic stripe data or equivalent chip data
- Card verification codes (CVV2, CVC2, CID – the 3-4 digit code on the card)
- PINs and PIN blocks
Think of SAD as the "secret handshake" that proves someone physically possesses the card.
The Critical Retention Difference
Here's where it gets serious: You may NEVER store SAD after transaction authorization is complete. Not encrypted, not hashed, not at all. This is an absolute prohibition. SAD exists only in-flight during the authorization process.
CHD, conversely, may be stored if there's a legitimate business need (recurring billing, returns, chargebacks), but it must be protected through encryption, tokenization, access controls, and other PCI-DSS requirements.
Analogy: SAD is like the one-time passcode sent to your phone – it expires immediately after use. CHD is like your account number – necessary for ongoing business but must be locked in a vault.
Key Takeaway: Sensitive Authentication Data (SAD) must NEVER be stored post-authorization, while Cardholder Data (CHD) may be retained only when necessary and must be rigorously protected according to PCI-DSS controls.