Rule ID
SV-252139r961029_rule
Version
V1R4
The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. In such cases, passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission. DBMS passwords sent in clear text format across the network are vulnerable to discovery by unauthorized users. Disclosure of passwords may easily lead to unauthorized access to the database. Satisfies: SRG-APP-000172-DB-000075, SRG-APP-000175-DB-000067
In the MongoDB database configuration file (default location: /etc/mongod.conf), verify the following parameters in the net.tls: (network TLS) section of the file:
net:
tls:
mode: requireTLS
certificateKeyFile: /etc/ssl/mongodb.pem
CAFile: /etc/ssl/caToValidateClientCertificates.pem
allowInvalidCertificates: false
allowConnectionsWithoutCertificates: false
If the net.tls: parameter is not present, this is a finding.
If the net.tls.certificateKeyFile parameter is not present, this is a finding.
If the net.tls.CAFile parameter is not present, this is a finding.
If the net.tls.allowInvalidCertificates parameter is found and set to true, this is a finding.
If the net.tls.allowConnectionsWithoutCertificates parameter is found and set to true, this is a finding.In the MongoDB database configuration file (default location: /etc/mongod.conf), ensure the following parameters are present in the net.tls (network TLS) section of the file and are configured correctly for the site and server:
net:
tls:
mode: requireTLS
certificateKeyFile: /etc/ssl/mongodb.pem
CAFile: /etc/ssl/caToValidateClientCertificates.pem
allowInvalidCertificates: false
allowConnectionsWithoutCertificates: false
Stop/start (restart) the mongod or mongos instance using this configuration.
More information for configuring TLS/SSL for MongoDB can be found here:
https://docs.mongodb.com/v4.4/tutorial/configure-ssl/