| V-221159 ||High ||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. |
| V-221172 ||High ||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... |
| V-221163 ||High ||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... |
| V-221169 ||High ||If DBMS authentication using passwords is employed, MongoDB must enforce the DoD standards for password complexity and lifetime. ||OS/enterprise authentication and identification must be used (SQL2-00-023600). Built-in DBMS authentication may be used only when circumstances make it unavoidable and must be documented and... |
| V-221178 ||High ||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... |
| V-221158 ||High ||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. |
| V-221170 ||High ||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... |
| V-221171 ||High ||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... |
| V-221174 ||High ||MongoDB must use NIST FIPS 140-2-validated cryptographic modules for cryptographic operations. ||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... |
| V-221200 ||High ||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... |
| V-221173 ||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... |
| V-221175 ||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... |
| V-221167 ||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... |
| V-221162 ||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... |
| V-221161 ||Medium ||The audit information produced by MongoDB must be protected from unauthorized read 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... |
| V-221160 ||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,... |
| V-221189 ||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... |
| V-221188 ||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... |
| V-221165 ||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... |
| V-221164 ||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... |
| V-221185 ||Medium ||MongoDB must associate organization-defined types of security labels having organization-defined security label values with information in storage. ||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... |
| V-221184 ||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... |
| V-221168 ||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.
| V-221181 ||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... |
| V-221180 ||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... |
| V-221183 ||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... |
| V-221182 ||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... |
| V-221191 ||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... |
| V-221166 ||Medium ||Unused database components, DBMS software, and database objects must be removed. ||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... |
| V-221179 ||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... |
| V-221186 ||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... |
| V-221198 ||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... |
| V-221199 ||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... |
| V-221176 ||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... |
| V-221177 ||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,... |
| V-221192 ||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... |
| V-221193 ||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... |
| V-221190 ||Medium ||MongoDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% 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... |
| V-221201 ||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... |
| V-221196 ||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... |
| V-221197 ||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,... |
| V-221194 ||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. |
| V-221195 ||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... |