An organization wants to limit potential impact to its log-in database in the event of a breach. Which of the following options is the security team most likely to recommend?

Question

Options

• ATokenization
• BHashing
• CObfuscation
• DSegmentation

• A
  7% (4)
• B
  89% (54)
• C
  2% (1)
• D
  3% (2)

Explanation

Hashing is the right choice because login databases store passwords, and one-way cryptographic hashing (e.g., bcrypt, Argon2) ensures that even if the database is breached, attackers cannot recover the original plaintext passwords - the stored values are mathematically irreversible. Tokenization (A) replaces sensitive data with a reversible token mapped to a vault, which is useful for payment card data but doesn't fit the password storage use case. Obfuscation (C) merely obscures data in a way that can be reversed or decoded, providing no real cryptographic protection. Segmentation (D) isolates network zones to limit breach spread, but does nothing to protect the data within the database if it is compromised.

Memory tip: Think "passwords get hashed, not stashed" - hashing is the irreversible lock that makes stolen password databases useless to attackers.

No community discussion yet for this question.