| Checked | Name | Title |
|---|
| ☐ | SV-220339r960735_rule | MarkLogic Server must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. |
| ☐ | SV-220340r960768_rule | MarkLogic Server must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. |
| ☐ | SV-220341r960792_rule | MarkLogic Server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-220342r960864_rule | MarkLogic Server must protect against a user falsely repudiating having performed organization-defined actions. |
| ☐ | SV-220343r960879_rule | MarkLogic Server must be configured to provide audit record generation capability for DoD-defined auditable events within all DBMS/database components. |
| ☐ | SV-220344r960882_rule | MarkLogic Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. |
| ☐ | SV-220345r960885_rule | MarkLogic Server must be able to generate audit records when privileges/permissions are retrieved. |
| ☐ | SV-220346r960885_rule | MarkLogic Server must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. |
| ☐ | SV-220347r960888_rule | MarkLogic Server must initiate session auditing upon startup. |
| ☐ | SV-220348r960915_rule | MarkLogic Server must shut down by default upon audit failure, to include the unavailability of space for more audit log records; or must be configurable to shut down upon audit failure. |
| ☐ | SV-220349r960930_rule | The audit information produced by MarkLogic Server must be protected from unauthorized read access. |
| ☐ | SV-220350r960933_rule | The audit information produced by MarkLogic Server must be protected from unauthorized modification. |
| ☐ | SV-220351r960936_rule | The audit information produced by MarkLogic Server must be protected from unauthorized deletion. |
| ☐ | SV-220352r960939_rule | MarkLogic Server must protect its audit features from unauthorized access. |
| ☐ | SV-220353r960942_rule | MarkLogic Server must protect its audit configuration from unauthorized modification. |
| ☐ | SV-220354r960945_rule | MarkLogic Server must protect its audit features from unauthorized removal. |
| ☐ | SV-220355r960960_rule | MarkLogic Server must limit privileges to change software modules, including stored procedures, functions, and triggers, and links to software external to the DBMS. |
| ☐ | SV-220356r960960_rule | MarkLogic Server software installation account must be restricted to authorized users. |
| ☐ | SV-220357r960960_rule | MarkLogic Server software, including configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. |
| ☐ | SV-220358r960960_rule | MarkLogic Server objects (including but not limited to indexes, storage, functions, triggers, links to software external to the server, etc.) must be owned by database/MarkLogic Server principals authorized for ownership. |
| ☐ | SV-220359r960960_rule | The role(s)/group(s) used to modify database structure (including but not necessarily limited to indexes, storage, etc.) and logic modules (functions, triggers, links to software external to the MarkLogic Server, etc.) must be restricted to authorized users. |
| ☐ | SV-220360r960963_rule | Unused database components, DBMS software, and database objects must be removed. |
| ☐ | SV-220361r960963_rule | Access to external executables must be disabled or restricted. |
| ☐ | SV-220362r960966_rule | MarkLogic Server 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. |
| ☐ | SV-220363r960969_rule | MarkLogic Server must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-220364r1018604_rule | If MarkLogic Server authentication using passwords is employed, MarkLogic Server must enforce the DOD standards for password complexity and lifetime. |
| ☐ | SV-220365r961029_rule | If passwords are used for authentication, the MarkLogic Server must transmit only encrypted representations of passwords. |
| ☐ | SV-220366r961038_rule | MarkLogic Server, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. |
| ☐ | SV-220367r961041_rule | MarkLogic Server must enforce authorized access to all PKI private keys stored/utilized by the DBMS. |
| ☐ | SV-220368r961050_rule | MarkLogic Server must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations and protect classified information in accordance with the requirements of the data owner. |
| ☐ | SV-220369r961053_rule | MarkLogic Server must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). |
| ☐ | SV-220370r961095_rule | MarkLogic Server must separate user functionality (including user interface services) from database management functionality. |
| ☐ | SV-220371r961119_rule | MarkLogic Server must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. |
| ☐ | SV-220372r961128_rule | MarkLogic Server must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-220373r961149_rule | Access to MarkLogic Server files must be limited to relevant processes and to authorized, administrative users. |
| ☐ | SV-220374r961167_rule | MarkLogic Server must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. |
| ☐ | SV-220375r961272_rule | MarkLogic Server must associate organization-defined types of security labels having organization-defined security label values with information in process. |
| ☐ | SV-220376r961275_rule | MarkLogic Server must associate organization-defined types of security labels having organization-defined security label values with information in transmission. |
| ☐ | SV-220377r961353_rule | MarkLogic Server must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-220378r961359_rule | Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only. |
| ☐ | SV-220380r961392_rule | MarkLogic Server must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-220381r961398_rule | MarkLogic Server must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity. |
| ☐ | SV-220382r961401_rule | MarkLogic Server must provide an immediate real-time alert to appropriate support staff of all audit failures. |
| ☐ | SV-220383r1018605_rule | MarkLogic Server must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s). |
| ☐ | SV-220384r961470_rule | MarkLogic Server must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accordance with Ports, Protocols, and Services Management (PPSM) guidance. |
| ☐ | SV-220385r961521_rule | MarkLogic Server must prohibit the use of cached authenticators after an organization-defined time period. |
| ☐ | SV-220386r961596_rule | MarkLogic Server must only accept end-entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions. |
| ☐ | SV-220387r1018556_rule | MarkLogic Server 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. |
| ☐ | SV-220388r1018557_rule | MarkLogic Server must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. |
| ☐ | SV-220389r1001008_rule | Security-relevant software updates to MarkLogic Server must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). |
| ☐ | SV-220390r961791_rule | MarkLogic Server must be able to generate audit records when security objects are accessed. |
| ☐ | SV-220391r961791_rule | MarkLogic Server must generate audit records when unsuccessful attempts to access security objects occur. |
| ☐ | SV-220392r961797_rule | MarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are accessed. |
| ☐ | SV-220393r961797_rule | MarkLogic Server must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-220394r961800_rule | MarkLogic Server must generate audit records when privileges/permissions are added. |
| ☐ | SV-220395r961800_rule | MarkLogic Server must generate audit records when unsuccessful attempts to add privileges/permissions occur. |
| ☐ | SV-220396r961800_rule | MarkLogic Server must generate audit records when privileges/permissions are modified. |
| ☐ | SV-220397r961800_rule | MarkLogic Server must generate audit records when unsuccessful attempts to modify privileges/permissions occur. |
| ☐ | SV-220398r961803_rule | MarkLogic Server must generate audit records when security objects are modified. |
| ☐ | SV-220399r961803_rule | MarkLogic Server must generate audit records when unsuccessful attempts to modify security objects occur. |
| ☐ | SV-220400r961809_rule | MarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are modified. |
| ☐ | SV-220401r961809_rule | MarkLogic Server must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-220402r961812_rule | MarkLogic Server must generate audit records when privileges/permissions are deleted. |
| ☐ | SV-220403r961812_rule | MarkLogic Server must generate audit records when unsuccessful attempts to delete privileges/permissions occur. |
| ☐ | SV-220404r961818_rule | MarkLogic Server DBMS must generate audit records when security objects are deleted. |
| ☐ | SV-220405r961818_rule | MarkLogic Server must generate audit records when unsuccessful attempts to delete security objects occur. |
| ☐ | SV-220406r961821_rule | MarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are deleted. |
| ☐ | SV-220407r961821_rule | MarkLogic Server must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-220408r961824_rule | MarkLogic Server must generate audit records when successful logons or connections occur. |
| ☐ | SV-220409r961824_rule | MarkLogic Server must generate audit records when unsuccessful logons or connection attempts occur. |
| ☐ | SV-220410r961827_rule | MarkLogic Server must generate audit records for all privileged activities or other system-level access. |
| ☐ | SV-220411r961827_rule | MarkLogic Server must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. |
| ☐ | SV-220412r961833_rule | MarkLogic Server must generate audit records when concurrent logons/connections by the same user from different workstations occur. |
| ☐ | SV-220413r961836_rule | MarkLogic must be able to generate audit records when successful accesses to objects occur. |
| ☐ | SV-220414r961857_rule | MarkLogic Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures. |
| ☐ | SV-220415r961857_rule | MarkLogic Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes. |
| ☐ | SV-220416r961857_rule | MarkLogic Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the requirements of the data owner. |
| ☐ | SV-220417r961860_rule | MarkLogic Server must off-load audit data to a separate log management facility; this must 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. |
| ☐ | SV-220418r961863_rule | MarkLogic Server 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. |
| ☐ | SV-265874r999528_rule | MarkLogic Server must be a version supported by the vendor. |
STIGQter: STIG Summary: