STIGQter: STIG Summary: MongoDB Enterprise Advanced 7.x Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 01 Jul 2026:

Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to MongoDB, etc.) must be owned by database/DBMS principals authorized for ownership.

DISA Rule

SV-265913r1028525_rule

Vulnerability Number

V-265913

Group Title

SRG-APP-000133-DB-000200

Rule Version

MD7X-00-002900

Severity

CAT II

CCI(s)

• CCI-001499 - Limit privileges to change software resident within software libraries.

Weight

10

Fix Recommendation

For each user identified as having a "dbOwner" role on a database they are not authorized for, revoke the "dbOwner" role from that user on that database by running the following commands:

use <database>
db.revokeRolesFromUser() command

https://www.mongodb.com/docs/v7.0/reference/command/revokeRolesFromUser/

Example to revoke "dbOwner" role from "user1" on the "anotherDatabase" in the "admin" database:

use admin
db.revokeRolesFromUser(
"user1",
[
{ role: "dbOwner", db: "anotherDatabase" }
]
)

Check Contents

For each database in MongoDB, run the following commands:

use <database>
db.getUsers()

Example output:

{
_id: 'admin.user1',
userId: UUID('b78e490a-4661-491f-8197-c3251934e785'),
user: 'user1',
db: 'admin',
roles: [
{ role: 'readWrite', db: 'myDatabase' },
{ role: 'dbOwner', db: 'myDatabase' },
{ role: 'dbOwner', db: 'anotherDatabase' }
]

Here, the user named "user1" in the "admin" database has a role of "dbOwner" for the database (db:) "myDatabase" and the database (db:) "anotherDatabase".

For users where the role of "dbOwner" is found, verify with the organization or site-specific documentation whether the user is authorized for the "dbOwner" role on the database resources listed.

If the user account has the role of "dbOwner" but is not authorized for the role for any database listed in their output, this is a finding.

Vulnerability Number

V-265913

Documentable

False

Rule Version

MD7X-00-002900

Severity Override Guidance

For each database in MongoDB, run the following commands:

use <database>
db.getUsers()

Example output:

{
_id: 'admin.user1',
userId: UUID('b78e490a-4661-491f-8197-c3251934e785'),
user: 'user1',
db: 'admin',
roles: [
{ role: 'readWrite', db: 'myDatabase' },
{ role: 'dbOwner', db: 'myDatabase' },
{ role: 'dbOwner', db: 'anotherDatabase' }
]

Here, the user named "user1" in the "admin" database has a role of "dbOwner" for the database (db:) "myDatabase" and the database (db:) "anotherDatabase".

For users where the role of "dbOwner" is found, verify with the organization or site-specific documentation whether the user is authorized for the "dbOwner" role on the database resources listed.

If the user account has the role of "dbOwner" but is not authorized for the role for any database listed in their output, this is a finding.

Check Content Reference

M

Target Key

5637