Details
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.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Document validation can be added at the time of creation of a 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.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: System and Information Integrity.This control applies to the following type of system MongoDB.
References
- 800-53|SI-10(3)
- CAT|II
- CCI|CCI-002754
- Rule-ID|SV-96639r1_rule
- STIG-ID|MD3X-00-000780
- Vuln-ID|V-81925