An e-commerce merchant processes payment card transactions through its internal application servers and stores transaction history in an on-premises database. To align with Payment Card Industry Data Security Standard (PCI-DSS) requirements and minimize compliance audit costs, the chief information security officer (CISO) wants to reduce the overall scope of the Cardholder Data Environment (CDE). Which of the following technical controls will most effectively reduce the organization's PCI-DSS compliance scope?
- Implementing tokenization to replace Primary Account Numbers (PAN) with non-sensitive surrogate values prior to internal storageCevap
- BApplying AES-256 field-level symmetric encryption to cardholder data while storing the cryptographic keys on the database server
- CMandating annual security awareness training for all staff who interact with payment processing workflows
- DDeploying an automated vulnerability scanner to conduct weekly network scans against external web endpoints
Cevap
Implementing tokenization to replace Primary Account Numbers (PAN) with non-sensitive surrogate values prior to internal storage is the correct control for scope reduction.
Tokenization replaces sensitive cardholder data with non-sensitive reference tokens. When internal applications and databases store only tokens rather than actual Primary Account Numbers (PAN), the underlying infrastructure no longer stores or processes Cardholder Data (CHD), effectively removing those systems from the PCI-DSS audit boundary and reducing compliance scope.
Adım Adım Çözüm
Anahtar Kavram
PCI-DSS Scope Reduction via Tokenization