STIGQter: STIG Summary: MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 26 Jan 2026:

MongoDB must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.

DISA Rule

SV-279387r1179328_rule

Vulnerability Number

V-279387

Group Title

SRG-APP-000428-DB-000386

Rule Version

MD8X-00-008100

Severity

CAT I

CCI(s)

• CCI-002475 - Implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information when at rest on organization-defined system components.
• CCI-002476 - Implement cryptographic mechanisms to prevent unauthorized disclosure of organization-defined information at rest on organization-defined system components.

Weight

10

Fix Recommendation

Configure encryption-at-rest through hardware encryption, volume encryption, filesystem encryption, or third-party products if not using MongoDBs native encryption-at-rest.

When using MongoDBs native encryption-at-rest, configure MongoDB to use the Encrypted Storage Engine and a KMIP appliance as documented here:

https://www.mongodb.com/docs/v8.0/core/security-encryption-at-rest/

https://www.mongodb.com/docs/v8.0/tutorial/configure-encryption/

Check Contents

Review the documentation or specification for the organization-defined information.

If any data is PII, classified, or per the organization must be encrypted at rest, verify the method of encryption is documented.

If no documented mechanism is being used to encrypt data-at-rest such as hardware encryption, volume encryption, filesystem encryption or the use of third-party products to enable encryption at rest, this is a finding.

If the documented method to encrypt MongoDB data-at-rest is the native MongoDB encryption-at-rest, verify the MongoDB configuration file (default location /etc/mongod.conf) contains the following options:

security:
kmip:
keyIdentifier: <string>
rotateMasterKey: <boolean>
serverName: <string>
port: <string>
clientCertificateFile: <string>
clientCertificatePassword: <string>
clientCertificateSelector: <string>
serverCAFile: <string>
connectRetries: <int>
connectTimeoutMS: <int>
activateKeys: <boolean>
keyStatePollingSeconds: <int>

If these above options are not configured in the MongoDB security.kmip section in the MongoDB configuration file, this is a finding.

Vulnerability Number

V-279387

Documentable

False

Rule Version

MD8X-00-008100

Severity Override Guidance

Review the documentation or specification for the organization-defined information.

If any data is PII, classified, or per the organization must be encrypted at rest, verify the method of encryption is documented.

If no documented mechanism is being used to encrypt data-at-rest such as hardware encryption, volume encryption, filesystem encryption or the use of third-party products to enable encryption at rest, this is a finding.

If the documented method to encrypt MongoDB data-at-rest is the native MongoDB encryption-at-rest, verify the MongoDB configuration file (default location /etc/mongod.conf) contains the following options:

security:
kmip:
keyIdentifier: <string>
rotateMasterKey: <boolean>
serverName: <string>
port: <string>
clientCertificateFile: <string>
clientCertificatePassword: <string>
clientCertificateSelector: <string>
serverCAFile: <string>
connectRetries: <int>
connectTimeoutMS: <int>
activateKeys: <boolean>
keyStatePollingSeconds: <int>

If these above options are not configured in the MongoDB security.kmip section in the MongoDB configuration file, this is a finding.

Check Content Reference

M

Target Key

5728