A enterprise payment processing organization needs to protect sensitive credit card Primary Account Numbers (PAN) stored within a centralized relational database. The security architecture team must ensure that if an unauthorized user or database administrator queries the storage tables, the sensitive numerical data is not exposed. Additionally, downstream analytics applications must be able to process database records without altering the underlying database schema length or data format. Which of the following storage data protection mechanisms best meets these architectural requirements?
- Tokenization of sensitive data fieldsAnswer
- BAsymmetric RSA bulk encryption of database storage volumes
- CCryptographic hashing of storage records for non-repudiation
- DStateful network firewall filtering between application and storage tiers
Answer
Tokenization of sensitive data fields is the most appropriate control because it substitutes sensitive values with non-sensitive tokens while preserving data format and length for database compatibility.
Tokenization replaces sensitive numbers with non-sensitive surrogate tokens that match the original data type and format. This prevents unauthorized users and database administrators from viewing raw sensitive data while allowing existing application schemas and analytics jobs to function without structural modifications.
Step-by-Step Solution
Key Concept
Data Tokenization and Format-Preserving Protection