STIGQter: STIG Summary: MongoDB Enterprise Advanced 3.x Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 24 Jul 2020:

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

DISA Rule

SV-96595r1_rule

Vulnerability Number

V-81881

Group Title

SRG-APP-000225-DB-000153

Rule Version

MD3X-00-000420

Severity

CAT II

CCI(s)

• CCI-001190 - The information system fails to an organization-defined known-state for organization-defined types of failures.
• CCI-001665 - The information system preserves organization-defined system state information in the event of a system failure.

Weight

10

Fix Recommendation

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:

storage:
journal:
enabled: true

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

Check Contents

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.

Vulnerability Number

V-81881

Documentable

False

Rule Version

MD3X-00-000420

Severity Override Guidance

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.

Check Content Reference

M

Target Key

3265

Comments