| V-279334 | | MongoDB must provide audit record generation for DOD-defined auditable events within all DBMS/database components. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-279336 | | The audit information produced by MongoDB must be protected from unauthorized access, modification, and deletion. | If audit data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity is imp... |
| V-279337 | | MongoDB must protect its audit features from unauthorized access, modification, and removal. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ne... |
| V-279338 | | 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... |
| V-279340 | | MongoDB database software, including 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 that any changes to the hardware, software, and/or firmware components of the information ... |
| V-279341 | | MongoDB 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 ot... |
| V-279342 | | 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 appro... |
| V-279344 | | Unused database components, MongoDB 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 no... |
| V-279346 | | MongoDB must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-279347 | | MongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). | To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and... |
| V-279352 | | 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 acco... |
| V-279355 | | MongoDB must separate user functionality (including user interface services) from database management functionality. | Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers, and ty... |
| V-279358 | | 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 identifie... |
| V-279363 | | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. | Applications, including database management systems (DBMSs), must prevent unauthorized and unintended information transfer via shared system resources... |
| V-279364 | | Access to database files must be limited to relevant processes and to authorized, administrative users. | Applications, including database management systems (DBMSs), must prevent unauthorized and unintended information transfer via shared system resources... |
| V-279365 | | 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 ... |
| V-279366 | | 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 t... |
| V-279367 | | MongoDB must provide nonprivileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. | Any database management systems (DBMSs) or associated application providing too much information in error messages on the screen or printout risks com... |
| V-279368 | | MongoDB must reveal detailed error messages only to the information system security officer (ISSO), information system security manager (ISSM), system administrator (SA) and database administrator (DBA). | If the database management system (DBMS) provides too much information in error logs and administrative messages to the screen, this could lead to com... |
| V-279371 | | 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 the database management systems (DBMS) to make security-related acces... |
| V-279372 | | MongoDB must enforce Discretionary Access Control (DAC) policies, as defined by the data owner, over defined subjects and objects. | DAC is based on the idea that individual users are "owners" of objects and therefore, have discretion over who should be authorized to access the obje... |
| V-279373 | | MongoDB must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary ... |
| V-279375 | | MongoDB must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | To ensure sufficient storage capacity for the audit logs, the DBMS must be able to allocate audit record storage capacity. Although another requiremen... |
| V-279376 | | 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 the database management s... |
| V-279380 | | 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 instal... |
| V-279381 | | 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 sy... |
| V-279382 | | MongoDB must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance. | Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.... |
| V-279383 | | 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, ... |
| V-279386 | | 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 they have security controls and identity vetting procedures in place, which are sufficie... |
| V-279389 | | 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 agg... |
| V-279390 | | 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 c... |
| V-279391 | | When updates are applied to MongoDB software, any software components that have been replaced or made unnecessary must be removed. | Previous versions of database management system (DBMS) components that are not removed from the information system after updates have been installed m... |
| V-279392 | | 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 t... |
| V-279394 | | MongoDB must off-load audit data to a separate log management facility; this shall be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-279395 | | 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 organizationwide security implementation guides and security checklists ensures compliance with federal standards and... |
| V-279398 | | MongoDB must prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate recognized and approved by the organization. | Software and firmware components prevented from installation unless signed with recognized and approved certificates include software and firmware ver... |
| V-279399 | | MongoDB must require users to be individually authenticated before granting access to the shared accounts or resources. | Individual authentication prior to shared group authentication mitigates the risk of using group accounts or authenticators.... |
| V-279409 | | MongoDB must, for public key-based authentication, implement a local cache of revocation data to support path discovery and validation. | Public key cryptography is a valid authentication mechanism for individuals, machines, and devices. For PKI solutions, status information for certific... |
| V-279411 | | MongoDB must include only approved trust anchors in trust stores or certificate stores managed by the organization. | Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the inter... |
| V-279412 | | MongoDB must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store. | A Trusted Platform Module (TPM) is an example of a hardware-protected data store that can be used to protect cryptographic keys.... |
| V-282943 | | MongoDB must be configured to restrict the use of administrator access to authorized IP addresses. | MongoDB will use Authentication Restrictions to enforce network-based separation of admin users from application users on the same port.
With Authen... |
| V-279331 | | MongoDB must limit the total number of concurrent connections to the database. | Database management includes the ability to control the number of users and user sessions utilizing a DBMS. Unlimited concurrent connections to the DB... |
| V-281700 | | MongoDB must terminate a user session after organization-defined conditions or trigger events requiring session disconnect via a scheduled script. | This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with commu... |
| V-279332 | | MongoDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. | Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functi... |
| V-279333 | | MongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. | Authentication with a DOD-approved PKI certificate does not necessarily imply authorization to access the DBMS. To mitigate the risk of unauthorized a... |
| V-279339 | | MongoDB software installation account must be restricted to authorized users. | When dealing with change control issues, it should be noted that any changes to the hardware, software, and/or firmware components of the information ... |
| V-279349 | | MongoDB must, for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash. | 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 po... |
| V-279350 | | 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 po... |
| V-279351 | | MongoDB must enforce authorized access to all PKI private keys stored/used by the DBMS. | The DOD standard for authentication is DOD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate h... |
| V-279353 | | 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 authentica... |
| V-279354 | | MongoDB must use NIST FIPS 140-2/140-3 validated cryptographic modules for cryptographic operations. | Use of weak or not validated cryptographic algorithms undermines the purposes of using encryption and digital signatures to protect data. Weak algorit... |
| V-279361 | | 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 nonmobile devices and covers user information and syst... |
| V-279385 | | MongoDB must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements. | Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The application must implement cryptographi... |
| V-279387 | | 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. | Database management system (DBMSs) handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized discl... |
| V-279393 | | MongoDB 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 ... |
