MD4X-00-002300 - 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.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and procedures can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions if they were the owner. If not properly managed, this can lead to privileged actions being taken by unauthorized individuals.

Conversely, if critical tables or other objects rely on unauthorized owner accounts, these objects may be lost when an account is removed.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

For each user where the role of dbOwner is found verify whether or not the user is authorized for this role on the resources listed.

This information will be found in the organizational or site-specific documentation.

If a user if found not authorized to have the role dbOwner the remove that role from the user with the
db.revokeRolesFromUser() command

https://docs.mongodb.com/v4.4/reference/command/revokeRolesFromUser/

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MDB_Enterprise_Advanced_4-x_V1R2_STIG.zip

Item Details

References: CAT|II, CCI|CCI-001499, Rule-ID|SV-252154r813844_rule, STIG-ID|MD4X-00-002300, Vuln-ID|V-252154

Plugin: MongoDB

Control ID: a2325cd73a44b8a1391f5d67b3c956e13996fb1cb189c2a503a47a9097227c11