STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to MongoDB Enterprise Advanced 4.x Security Technical Implementation Guide

V-252181

CAT II (Medium)

When invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives.

Rule ID

SV-252181r961656_rule

STIG

MongoDB Enterprise Advanced 4.x Security Technical Implementation Guide

Version

V1R4

CCIs

CCI-002754

Discussion

A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state. The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input. This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Check Content

This is application-specific, but see Schema Validation documentation here:
https://docs.mongodb.com/v4.4/core/schema-validation/

As an example, as a user with the dbAdminAnyDatabase role, execute the following on the database of interest:

 use database
 db.getCollectionInfos()

Where database is the name of the database on which validator rules are to be inspected. This returns an array of documents containing all collections information within the database. 

For all collections information received, check if the options sub-document contains a validator.

If the options sub-document does not contain a validator, this is a finding.

Example below shows a finding:
[
        {
                "name" : "inventory",
                "type" : "collection",
                "options" : {

                },
                "info" : {
                        "readOnly" : false,
                        "uuid" : UUID("b2c86d4d-48bf-4394-9743-620e6d68b87f")
                },
                "idIndex" : {
                        "v" : 2,
                        "key" : {
                                "_id" : 1
                        },
                        "name" : "_id_",
                        "ns" : "products.inventory"
                }
        }
]

Fix Text

Document validation can be added at the time of creation of a new collection. 

Existing collections can also be modified with document validation rules. 

Use the validator option to create or update a collection with the desired validation rules. 

See Schema Validation documentation for details:
https://docs.mongodb.com/v4.4/core/schema-validation/