Encryption at rest concept in MongoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Encryption at Rest in MongoDB?

Encryption at Rest means that data stored on disk is encrypted to protect it from unauthorized access, even if someone gets physical access to the storage.

beginner

Why is Encryption at Rest important?

It protects sensitive data from being read by attackers if the storage device is stolen or accessed without permission.

intermediate

How does MongoDB implement Encryption at Rest?

MongoDB uses a feature called WiredTiger Encryption, which encrypts data files on disk using a key managed by the database or an external key management system.

intermediate

What is a Key Management System (KMS) in the context of Encryption at Rest?

A KMS securely stores and manages encryption keys used to encrypt and decrypt data, ensuring keys are protected and only accessible to authorized systems.

beginner

Does Encryption at Rest protect data when it is being used or transferred?

No, Encryption at Rest only protects data stored on disk. Data in use or in transit needs other protections like TLS or application-level encryption.

What does Encryption at Rest protect in MongoDB?

A Data in application memory

B Data stored on disk

C Data being sent over the network

D User passwords only

Encryption at Rest protects data stored on disk, not data in transit or in memory.

Which MongoDB storage engine supports Encryption at Rest?

A WiredTiger

B MMAPv1

C In-Memory

D None

WiredTiger supports Encryption at Rest in MongoDB.

What is the role of a Key Management System (KMS) in Encryption at Rest?

A Stores and manages encryption keys securely

B Encrypts data in transit

C Manages user authentication

D Backs up database files

A KMS securely stores and manages encryption keys used for encrypting data at rest.

Does Encryption at Rest protect data when it is being queried?

A Only for admin users

B Yes, always

C Only if TLS is enabled

D No, it only protects data on disk

Encryption at Rest protects data on disk, not data in use during queries.

What happens if someone steals the physical disk without Encryption at Rest?

A The data is automatically deleted

B They cannot access the data

C They can read the data easily

D The database locks itself

Without Encryption at Rest, stolen disks can be read by attackers.

Explain in your own words what Encryption at Rest means and why it is important in MongoDB.

Think about what happens if someone gets your database files physically.

Describe how MongoDB uses encryption keys and what role a Key Management System plays in Encryption at Rest.

Consider how keys are kept safe and used to lock/unlock data.

Practice

1. What does encryption at rest mean in MongoDB?

easy

A. Data is encrypted only in the application memory.

B. Data is encrypted when stored on disk to protect it from unauthorized access.

C. Data is encrypted only during query execution.

D. Data is encrypted only when it is sent over the network.

Solution

1. Step 1: Understand encryption at rest meaning

   Encryption at rest means data is protected by encoding it while stored on disk, not just during transfer or processing.

2. Step 2: Identify correct option

   Only Data is encrypted when stored on disk to protect it from unauthorized access. correctly describes encryption at rest as protecting stored data on disk.

3. Final Answer:

   Data is encrypted when stored on disk to protect it from unauthorized access. -> Option B

4. Quick Check:

   Encryption at rest = Data encrypted on disk [OK]

Hint: Encryption at rest means data is safe on disk, not just in transit [OK]

Common Mistakes:

• Confusing encryption at rest with encryption in transit
• Thinking encryption happens only during queries
• Assuming encryption applies only in memory

2. Which of the following is the correct way to enable encryption at rest in MongoDB?

easy

A. Run a query like db.enableEncryption() in the shell.

B. Use encrypt() command on collections.

C. Configure the MongoDB server with encryption options in the config file.

D. Set encryption flags in the client application code.

Solution

1. Step 1: Know how encryption at rest is enabled

   Encryption at rest is enabled by configuring the MongoDB server settings, not by running queries or client code.

2. Step 2: Match correct method

   Only Configure the MongoDB server with encryption options in the config file. correctly states enabling encryption via server config file.

3. Final Answer:

   Configure the MongoDB server with encryption options in the config file. -> Option C

4. Quick Check:

   Encryption at rest enabled via server config [OK]

Hint: Encryption at rest is a server setting, not a query command [OK]

Common Mistakes:

• Trying to enable encryption using shell queries
• Assuming client code controls encryption at rest
• Confusing encryption at rest with field-level encryption

3. Given MongoDB is configured with encryption at rest enabled, what will happen if the encryption key is lost?

medium

A. Only new data is encrypted; old data remains readable.

B. Data can still be read normally without the key.

C. MongoDB automatically regenerates the key and decrypts data.

D. Data becomes inaccessible and cannot be decrypted.

Solution

1. Step 1: Understand role of encryption key

   The encryption key is essential to decrypt data stored on disk. Losing it means data cannot be read.

2. Step 2: Evaluate options

   Data becomes inaccessible and cannot be decrypted. correctly states data becomes inaccessible without the key. Other options are incorrect because data cannot be read or auto-decrypted without the key.

3. Final Answer:

   Data becomes inaccessible and cannot be decrypted. -> Option D

4. Quick Check:

   Lost key = no data access [OK]

Hint: Without the key, encrypted data is unreadable [OK]

Common Mistakes:

• Assuming MongoDB can recover data without the key
• Thinking only new data is encrypted
• Believing data remains readable without key

4. A MongoDB admin tries to enable encryption at rest by running db.enableEncryption() in the shell but gets an error. What is the likely cause?

medium

A. Encryption at rest cannot be enabled via shell commands; it requires server config changes.

B. The shell command syntax is incorrect; it should be db.enableEncryption(true).

C. Encryption at rest is enabled by default and does not require commands.

D. The admin lacks permissions to run shell commands.

Solution

1. Step 1: Understand how encryption at rest is enabled

   Encryption at rest is a server-level feature enabled via configuration files, not shell commands.

2. Step 2: Identify cause of error

   Trying to enable it via db.enableEncryption() causes error because this command does not exist.

3. Final Answer:

   Encryption at rest cannot be enabled via shell commands; it requires server config changes. -> Option A

4. Quick Check:

   Enable encryption via config, not shell [OK]

Hint: Encryption at rest needs config file, not shell commands [OK]

Common Mistakes:

• Trying to enable encryption with shell commands
• Assuming encryption is on by default
• Blaming permissions instead of wrong method

5. You want to ensure your MongoDB data is encrypted at rest and can be recovered safely. Which combination of steps is best practice?

hard

A. Enable encryption at rest in server config and securely manage encryption keys separately.

B. Encrypt data manually in application code and store keys in the database.

C. Use shell commands to enable encryption and keep keys in the same server folder.

D. Rely on MongoDB default settings without managing keys.

Solution

1. Step 1: Understand encryption at rest best practices

   Encryption at rest should be enabled via server config, and keys must be managed securely outside the database for safety and recovery.

2. Step 2: Evaluate options for key management and encryption

   Enable encryption at rest in server config and securely manage encryption keys separately. correctly combines enabling encryption at rest with secure key management. Other options either misuse shell commands, store keys insecurely, or rely on defaults.

3. Final Answer:

   Enable encryption at rest in server config and securely manage encryption keys separately. -> Option A

4. Quick Check:

   Config encryption + secure keys = best practice [OK]

Hint: Enable encryption in config and keep keys safe separately [OK]

Common Mistakes:

• Storing keys inside the database
• Trying to enable encryption via shell commands
• Ignoring key management importance