Information
DBMSs handling data requiring 'data at rest' protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to MongoDB or implemented via additional software or operating system/file system settings, as appropriate to the situation.
Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).
The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides.
Satisfies: SRG-APP-000428-DB-000386, SRG-APP-000429-DB-000387
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Configure MongoDB to use the Encrypted Storage Engine and a KMIP appliance as documented here:
https://docs.mongodb.com/v4.4/core/security-encryption-at-rest/
https://docs.mongodb.com/v4.4/tutorial/configure-encryption/