MongoDB must protect the confidentiality and integrity of all information at rest.

This control is intended to address the confidentiality and integrity of information at rest in nonmobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive) within an organizational information system. Applications and application users generate information throughout the course of their application use.

User data generated, as well as application-specific configuration data, needs to be protected. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate.

If the confidentiality and integrity of application data is not protected, the data will be open to compromise and unauthorized modification.

To provide integrity and confidentiality for data at rest, MongoDB must be configured to use the Encrypted Storage Engine.

Run the following command to verify whether or not the Encrypted Storage Engine is enabled:

> db.serverStatus().encryptionAtRest.encryptionEnabled

Any output other than "true" is a finding.

Validate whether the Encrypted Storage Engine is running with an AEAD block cipher, which provides integrity, by running the following command:

> db.serverStatus().encryptionAtRest.encryptionCipherMode

Any response other than "AES256-GCM" is a finding.

Validate the system is configured to use KMIP to obtain a master encryption key, rather than storing the master key on the local filesystem.

Run:

> db.serverStatus().encryptionAtRest.encryptionKeyId

If the response is "local" or no response, this is a finding.

Enable the Encrypted Storage Engine with KMIP as the key storage mechanism and AES256-GCM as the encryption mode.

Consult MongoDB documentation for encryption setup instruction here: https://www.mongodb.com/docs/v8.0/tutorial/configure-encryption/