A DevOps team wants to move production data into the QA environment for testing. This data contains credit card numbers and expiration dates that are not tied to any individuals. The security…

The correct answer is B. Hashing the card numbers. Hashing is a one-way cryptographic transformation - once card numbers are hashed, the original values cannot be recovered. This makes hashing ideal for moving sensitive PCI data into a QA environment: test processes can still validate operations on consistent hash values…

Technical Integration of Enterprise Security

Question

A DevOps team wants to move production data into the QA environment for testing. This data contains credit card numbers and expiration dates that are not tied to any individuals. The security analyst wants to reduce risk. Which of the following will lower the risk before moving the data?

Options

ARedacting all but the last four numbers of the cards
BHashing the card numbers
CScrambling card and expiration data
DEncrypting card and expiration numbers

How the community answered

(34 responses)

A
3% (1)
B
85% (29)
C
3% (1)
D
9% (3)

Explanation

Hashing is a one-way cryptographic transformation - once card numbers are hashed, the original values cannot be recovered. This makes hashing ideal for moving sensitive PCI data into a QA environment: test processes can still validate operations on consistent hash values without exposing real card numbers. Encryption (D) is reversible with a key, meaning the actual card numbers remain recoverable if the key is exposed. Redacting (A) still exposes partial data (last four digits). Scrambling (C) produces meaningless data that may break test validation logic. Hashing balances data utility with irreversibility, minimizing risk.

Topics

#data masking#tokenization#PCI data protection#test environment security

Community Discussion

No community discussion yet for this question.

Full CAS-003 Practice