MongoDB Enterprise Advanced 4.x Security Technical Implementation Guide

Description

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]

Details

Version / Release: V1R1

Published: 2022-01-25

Updated At: 2022-04-06 01:06:14

Actions

Download

Filter

Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-252134r817007_rule MD4X-00-000100 CCI-000130 MEDIUM MongoDB must provide audit record generation for DoD-defined auditable events within all DBMS/database components. MongoDB must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components. Satisfies: SRG-APP-000089-DB-000064, SRG-APP-000080-DB-000063, SRG-APP-000090-DB-000065, SRG-APP-000091-DB-000066, SRG-APP-00009
    SV-252135r813787_rule MD4X-00-000200 CCI-000162 MEDIUM The audit information produced by MongoDB must be protected from unauthorized access. If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In addition, access to audit records provides information an
    SV-252136r813790_rule MD4X-00-000300 CCI-001493 MEDIUM MongoDB must protect its audit features from unauthorized access. Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application
    SV-252137r813793_rule MD4X-00-000400 CCI-000381 MEDIUM Unused database components that are integrated in MongoDB and cannot be uninstalled must be disabled. Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is det
    SV-252138r816978_rule MD4X-00-000500 CCI-000382 MEDIUM Unused database components that are integrated in MongoDB and cannot be uninstalled must be disabled. Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is det
    SV-252139r813799_rule MD4X-00-000600 CCI-000197 MEDIUM If passwords are used for authentication, MongoDB must transmit only encrypted representations of passwords. 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 protec
    SV-252140r813802_rule MD4X-00-000700 CCI-001082 MEDIUM MongoDB must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, indiv
    SV-252141r813805_rule MD4X-00-000800 CCI-001190 MEDIUM MongoDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. 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 th
    SV-252142r817009_rule MD4X-00-000900 CCI-001090 MEDIUM MongoDB must prevent unauthorized and unintended information transfer via shared system resources. The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current
    SV-252143r813811_rule MD4X-00-001000 CCI-001310 MEDIUM MongoDB and associated applications must reserve the use of dynamic code execution for situations that require it. With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such ca
    SV-252144r817017_rule MD4X-00-001100 CCI-002262 MEDIUM MongoDB must associate organization-defined types of security labels having organization-defined security label values with information in storage and transmission. Without the association of security labels to information, there is no basis for MongoDB to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects
    SV-252145r813817_rule MD4X-00-001200 CCI-002165 MEDIUM MongoDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired
    SV-252146r813820_rule MD4X-00-001300 CCI-002450 MEDIUM MongoDB must use NIST FIPS 140-2-validated cryptographic modules for cryptographic operations. The use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak algorithms can be easily broken and not validated cryptographic modules may not implement algorithms co
    SV-252147r813823_rule MD4X-00-001400 CCI-002475 MEDIUM MongoDB must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components. DBMSs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to MongoDB or implemented via additi
    SV-252148r813826_rule MD4X-00-001550 CCI-000054 MEDIUM MongoDB must limit the total number of concurrent connections to the database. MongoDB must limit the total number of concurrent connections to the database.
    SV-252149r813829_rule MD4X-00-001600 CCI-000015 MEDIUM MongoDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. MongoDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.
    SV-252150r813832_rule MD4X-00-001700 CCI-000213 MEDIUM MongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. MongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
    SV-252151r813835_rule MD4X-00-002000 CCI-001499 MEDIUM MongoDB must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to MongoDB. If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qualified
    SV-252152r813838_rule MD4X-00-002100 CCI-001499 MEDIUM MongoDB software installation account must be restricted to authorized users. When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can have significant effects on the overall security of the system. If the system w
    SV-252153r813841_rule MD4X-00-002200 CCI-001499 MEDIUM Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system. Mul
    SV-252154r813844_rule MD4X-00-002300 CCI-001499 MEDIUM Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to MongoDB, etc.) must be owned by database/DBMS principals authorized for ownership. Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and procedures can be coded using definer's rights. This allows anyone w
    SV-252155r813938_rule MD4X-00-002400 CCI-001499 MEDIUM The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to MongoDB, etc.) must be restricted to authorized users. If MongoDB were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qual
    SV-252156r813850_rule MD4X-00-002600 CCI-000381 MEDIUM Unused database components that are integrated in MongoDB and cannot be uninstalled must be disabled. Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is det
    SV-252157r813853_rule MD4X-00-002800 CCI-000764 MEDIUM MongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the orga
    SV-252158r813856_rule MD4X-00-002950 CCI-000192 MEDIUM If passwords are used for authentication, MongoDB must implement LDAP or Kerberos for authentication to enforce the DoD standards for password complexity and lifetime. OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable, and must be documented and AO-approved. The DoD standard for authentication is Do
    SV-252159r817005_rule MD4X-00-003000 CCI-000196 MEDIUM If passwords are used for authentication, MongoDB must store only hashed, salted representations of passwords. 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, database passwords stored i
    SV-252160r813862_rule MD4X-00-003100 CCI-000186 MEDIUM MongoDB must enforce authorized access to all PKI private keys stored/utilized by MongoDB. The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key. If the private key is stol
    SV-252161r813865_rule MD4X-00-003200 CCI-000187 MEDIUM MongoDB must map the PKI-authenticated identity to an associated user account. The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI certificate has been validated, it must be mapped to a DBMS user account for the authenticated identity to be meaningful to MongoDB and useful for authorization decisions.
    SV-252162r813868_rule MD4X-00-003300 CCI-000206 MEDIUM MongoDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. The DoD standard for authentication is DoD-approved PKI certificates. Normally, with PKI authentication, the interaction with the user for authentication will be handled by a software component separate from MongoDB, such as ActivIdentity ActivClient. Ho
    SV-252163r817011_rule MD4X-00-003400 CCI-000804 MEDIUM MongoDB must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, indiv
    SV-252164r817013_rule MD4X-00-003700 CCI-001188 MEDIUM MongoDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of un
    SV-252165r813877_rule MD4X-00-003800 CCI-001199 MEDIUM MongoDB must protect the confidentiality and integrity of all information at rest. This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary
    SV-252166r813880_rule MD4X-00-004000 CCI-001090 MEDIUM Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. Data used for the development and testing of applications often involves copying data from production. It is important that specific
    SV-252167r813883_rule MD4X-00-004100 CCI-001310 MEDIUM MongoDB must check the validity of all data inputs except those specifically identified by the organization. Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application or i
    SV-252168r813886_rule MD4X-00-004200 CCI-001312 MEDIUM MongoDB must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromising the data and security of the system. The structure and content of error messages need to be carefully considered by the organi
    SV-252169r813889_rule MD4X-00-004300 CCI-001314 MEDIUM MongoDB must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA. If MongoDB provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be carefully considered by the organization and development team. The exte
    SV-252170r813892_rule MD4X-00-004400 CCI-002361 MEDIUM MongoDB must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect. This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access)
    SV-252171r813895_rule MD4X-00-004800 CCI-001844 MEDIUM MongoDB must utilize centralized management of the content captured in audit records generated by all components of MongoDB. Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. The con
    SV-252172r813898_rule MD4X-00-004900 CCI-001849 MEDIUM MongoDB must allocate audit record storage capacity in accordance with site audit record storage requirements. In order to ensure sufficient storage capacity for the audit logs, MongoDB must be able to allocate audit record storage capacity. Although another requirement (SRG-APP-000515-DB-000318) mandates that audit data be off-loaded to a centralized log manageme
    SV-252173r813901_rule MD4X-00-005000 CCI-001855 MEDIUM MongoDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity. Organizations are required to use a central log management system; so, under normal conditions, the audit space allocated to MongoDB on its own server will not be an issue. However, space will still be required on MongoDB server for audit records in trans
    SV-252174r816988_rule MD4X-00-005300 CCI-001812 MEDIUM MongoDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular use
    SV-252175r816991_rule MD4X-00-005400 CCI-001813 MEDIUM MongoDB must enforce access restrictions associated with changes to the configuration of MongoDB or database(s). Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be noted that any ch
    SV-252176r816993_rule MD4X-00-005600 CCI-002038 MEDIUM MongoDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. The DoD standard for authentication of an interactive user is the presentation of a Common Access Card (CAC) or other physical token bearing a valid, current, DoD-issued Public Key Infrastructure (PKI) certificate, coupled with a Personal Identification N
    SV-252177r813913_rule MD4X-00-005700 CCI-002007 MEDIUM MongoDB must prohibit the use of cached authenticators after an organization-defined time period. If cached authentication information is out-of-date, the validity of the authentication information may be questionable.
    SV-252178r817015_rule MD4X-00-005800 CCI-002470 MEDIUM MongoDB must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions. Only DoD-approved external PKIs have been evaluated to ensure that they have security controls and identity vetting procedures in place which are sufficient for DoD systems to rely on the identity asserted in the certificate. PKIs lacking sufficient secur
    SV-252179r813919_rule MD4X-00-006000 CCI-002420 MEDIUM MongoDB must maintain the confidentiality and integrity of information during preparation for transmission. Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures
    SV-252180r813922_rule MD4X-00-006100 CCI-002422 MEDIUM MongoDB must maintain the confidentiality and integrity of information during reception. Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications c
    SV-252181r816995_rule MD4X-00-006200 CCI-002754 MEDIUM When invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives. 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 cau
    SV-252182r813928_rule MD4X-00-006300 CCI-002617 MEDIUM When updates are applied to MongoDB software, any software components that have been replaced or made unnecessary must be removed. Previous versions of DBMS components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some DBMSs' installation tools may remove older versions of software automatically from the informati
    SV-252183r816997_rule MD4X-00-006400 CCI-002605 MEDIUM Security-relevant software updates to MongoDB must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contract
    SV-252184r813934_rule MD4X-00-006500 CCI-002605 MEDIUM MongoDB products must be a version supported by the vendor. Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilities. Systems at unsupported servicing levels or releases
    SV-252185r816999_rule MD4X-00-006600 CCI-000366 MEDIUM MongoDB must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs. Configuring MongoDB to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture c