Developers must protect SSN fields in a database, store passwords safely, and show only partial payment card numbers on clerk screens. Which combination of methods is appropriate?
Select an answer to reveal the explanation.
Short Explanation
Different locks for different jobs: encrypt SSNs you may need again, hash passwords you should never need in cleartext, and mask the PAN so clerks see only a peek. Using the wrong tool—like hashing something you must reverse—breaks the workflow or the security.
Full Explanation
Encryption protects confidentiality of stored values that may need reversible access (such as SSNs under controlled key management). Password hashing (with salting/appropriate algorithms) stores credentials non-reversibly. Masking limits display of sensitive values such as payment card PANs. Matching method to goal prevents both weak protection and operational breakage. Shared source-code keys, cleartext PANs, and obscurity naming are inadequate.