A design stores the master encryption key in the same database it protects. What's wrong, and the fix?

This is one of the most common cryptographic design mistakes, and a good interview tell: the candidate either spots the self-defeating layout immediately, or accepts "but it's encrypted" at face value.

Why co-locating the key defeats encryption

Encryption transforms a confidentiality problem into a key-management problem. The whole security of the scheme now rests on the secrecy of the key. If you store that key in the very database the key protects, then any breach that exposes the data also exposes the key. The attacker steals the ciphertext and the means to decrypt it in one shot. It is a vault whose combination is written on the door — the encryption becomes ceremony, not protection.

The fix: separate, managed keys

Keys belong in a dedicated key-management system (KMS) or, for the highest assurance, a hardware security module (HSM) that can perform crypto operations without ever exporting the key. Layer on:

• Access control — only specific identities can use the key, logged and audited.
• Separation of duties — the people who can read the data are not the people who administer the keys.
• Rotation — keys change on a schedule and after suspected exposure.
• Envelope encryption — data keys are themselves encrypted by a master key in the KMS, so the master key never touches the data store.

Why the wrong answers are wrong

"Nothing, as long as the database is encrypted" misses the point entirely — encryption with a co-located key is no protection. "Hash the key before storing it" is a category error: hashing is one-way, so a hashed key can never decrypt the data; the system breaks. "Store two copies for redundancy" optimizes for availability while doubling the exposure of the most sensitive secret in the system — exactly backwards.

What an interviewer is probing

They want to see that you understand key management is the heart of cryptography, not an afterthought, and that you reach for a KMS/HSM with separation of duties and rotation rather than rationalizing a fatally flawed layout.