UCF STIG Viewer Logo

MongoDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.


Finding ID Version Rule ID IA Controls Severity
V-221177 MD3X-00-000420 SV-221177r879640_rule Medium
Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Systems that fail suddenly and with no incorporated failure state planning may leave the hosting system available but with a reduced security protection capability. Preserving information system state data also facilitates system restart and return to the operational mode of the organization with less disruption of mission/business processes. Databases must fail to a known consistent state. Transactions must be successfully completed or rolled back. In general, security mechanisms should be designed so that a failure will follow the same execution path as disallowing the operation. For example, application security methods, such as isAuthorized(), isAuthenticated(), and validate(), should all return false if there is an exception during processing. If security controls can throw exceptions, they must be very clear about exactly what that condition means. Abort refers to stopping a program or function before it has finished naturally. The term abort refers to both requested and unexpected terminations. Satisfies: SRG-APP-000225-DB-000153, SRG-APP-000226-DB-000147
MongoDB Enterprise Advanced 3.x Security Technical Implementation Guide 2024-01-24


Check Text ( C-22892r411025_chk )
Journaling is enabled by default in 64-bit systems.

With journaling enabled, if mongod stops unexpectedly, the program can recover everything written to the journal.

MongoDB will re-apply the write operations on restart and maintain a consistent state. By default, the greatest extent of lost writes, i.e., those not made to the journal, are those made in the last 100 milliseconds, plus the time it takes to perform the actual journal writes.

Verify the mongod process startup options.

If the mongod process was started with the "--nojournal" option, this is a finding.
Fix Text (F-22881r411026_fix)
Modify the mongod startup command-line options by removing the "--nojournal" option.

Edit the MongoDB database configuration file (default location: /etc/mongod.conf) to ensure it contains the following parameter setting:

enabled: true

Stop/start (restart) any or all mongod processes.