What changed in MongoDB Enterprise Advanced 7.x STIG V1R2V1R2 changes

MongoDB Enterprise Advanced 7.x STIG V1R2 (2026-07-01) replaced V1R1 (2024-09-25): 1 check added, 1 updated. It has 51 checks, against 50 in V1R1.

V1R2 checklistV1R1 checklist Compare V1R1 and V1R2 in STIG Compare

  • 1 added
  • 0 removed
  • 1 updated

Updated fields: Fix text 1Severity 1Discussion 1

Added in V1R2 (1)

  • V-285312CAT IIMongoDB must be configured to restrict the use of administrator access to authorized IP addresses.

Updated in V1R2 (1)

V-265947CAT IMongoDB 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.Severity, Fix text, Discussion

Severity

mediumhigh

Fix text

Configure encryption at rest through hardware encryption, volume encryption, filesystem encryption, or third-party products if not using MongoDBsMongoDB's native encryption at rest. When using MongoDBsMongoDB's native encryption at rest, configure MongoDB to use the Encrypted Storage Engine and a KMIP appliance as documented here: https://www.mongodb.com/docs/v7.0/core/security-encryption-at-rest/ https://www.mongodb.com/docs/v7.0/tutorial/configure-encryption/

Discussion

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 of 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

V-265947 in V1R2

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V1R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.