Detections
Analytics

MD3X-00-000570 - MongoDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.

Warning! Audit Deprecated

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

View Next Audit Version

Information

Discretionary Access Control (DAC) is based on the notion that individual users are 'owners' of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled table permissions.

When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects.

A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level.

The policy is bounded by the information system boundary. Once the information is passed outside of the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.

Satisfies: SRG-APP-000328-DB-000301, SRG-APP-000340-DB-000304

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

Solution

Revoke any roles with unnecessary privileges to privileged functionality by executing the revoke command as documented here:
https://docs.mongodb.com/v3.4/reference/method/db.revokeRolesFromUser/

Revoke any unnecessary privileges from any roles by executing the revoke command as document here:
https://docs.mongodb.com/v3.4/reference/method/db.revokePrivilegesFromRole/

If a new role with associated privileges needs to be created, follow the documentation here:
https://docs.mongodb.com/v3.4/reference/command/createRole/

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MDB_Enterprise_Advanced_3-x_V2R1_STIG.zip

Item Details

References: CAT|II, CCI|CCI-002165, CCI|CCI-002235, Rule-ID|SV-221186r411054_rule, STIG-ID|MD3X-00-000570, STIG-Legacy|SV-96613, STIG-Legacy|V-81899, Vuln-ID|V-221186

Plugin: MongoDB

Control ID: b20de2aa832f31c863a9ba0586fafe1b79af9cf66beb2c8e853eadbe008f394f