TMA-MONGODB-4.5
Ensure Encryption of Data at Rest
Description
Encryption of data at rest must be enabled to ensure compliance with security and privacy standards including HIPAA, PCI-DSS, and FERPA. Encryption at rest, when used in conjunction with transport encryption and good security policies that protect relevant accounts, passwords, and encryption keys. The benchmark rates this recommendation Manual; the automated check covers its objective pass criterion. Checks the YAML config file /etc/mongod.conf (SKIP when it does not exist). Requires MongoDB Enterprise (encrypted WiredTiger storage engine); also confirm a KMIP server or encryptionKeyFile holds the master key and that keys are rotated.
How it is checked
Audit method: File pattern
- File
/etc/mongod.conf- Pattern
(?m)^[ \t]*enableEncryption:[ \t]*['\x22]?true\b
How it is fixed
Fix method: Guidance or infrastructure patch
Configure security.enableEncryption: true with security.kmip.* (recommended) or security.encryptionKeyFile, then resync each member so its data files are rewritten encrypted; rotate keys per policy.
Properties
- Operating systems
- Any
- Tags
- mongodbencryption
- Reference
- CIS MongoDB 8 Benchmark v2.0.0 - 4.5 Ensure Encryption of Data at Rest
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
tmaegis scan --target mongodb --level 2