STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

MarkLogic Server v9 Security Technical Implementation Guide

Version

V3R2

Release Date

Sep 4, 2024

SCAP Benchmark ID

MarkLogic_Server_v9_STIG

Total Checks

80

Tags

other
CAT I: 8CAT II: 70CAT III: 2

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: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (80)

V-220339LOWMarkLogic Server must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.V-220340MEDIUMMarkLogic Server must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.V-220341HIGHMarkLogic Server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.V-220342MEDIUMMarkLogic Server must protect against a user falsely repudiating having performed organization-defined actions.V-220343MEDIUMMarkLogic Server must be configured to provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.V-220344MEDIUMMarkLogic Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.V-220345MEDIUMMarkLogic Server must be able to generate audit records when privileges/permissions are retrieved.V-220346MEDIUMMarkLogic Server must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.V-220347MEDIUMMarkLogic Server must initiate session auditing upon startup.V-220348MEDIUMMarkLogic 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.V-220349MEDIUMThe audit information produced by MarkLogic Server must be protected from unauthorized read access.V-220350MEDIUMThe audit information produced by MarkLogic Server must be protected from unauthorized modification.V-220351MEDIUMThe audit information produced by MarkLogic Server must be protected from unauthorized deletion.V-220352MEDIUMMarkLogic Server must protect its audit features from unauthorized access.V-220353MEDIUMMarkLogic Server must protect its audit configuration from unauthorized modification.V-220354MEDIUMMarkLogic Server must protect its audit features from unauthorized removal.V-220355MEDIUMMarkLogic Server must limit privileges to change software modules, including stored procedures, functions, and triggers, and links to software external to the DBMS.V-220356MEDIUMMarkLogic Server software installation account must be restricted to authorized users.V-220357MEDIUMMarkLogic Server software, including configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.V-220358MEDIUMMarkLogic 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.V-220359MEDIUMThe 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.V-220360MEDIUMUnused database components, DBMS software, and database objects must be removed.V-220361MEDIUMAccess to external executables must be disabled or restricted.V-220362MEDIUMMarkLogic 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.V-220363MEDIUMMarkLogic Server must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).V-220364MEDIUMIf MarkLogic Server authentication using passwords is employed, MarkLogic Server must enforce the DOD standards for password complexity and lifetime.V-220365HIGHIf passwords are used for authentication, the MarkLogic Server must transmit only encrypted representations of passwords.V-220366MEDIUMMarkLogic Server, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.V-220367HIGHMarkLogic Server must enforce authorized access to all PKI private keys stored/utilized by the DBMS.V-220368HIGHMarkLogic 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.V-220369MEDIUMMarkLogic Server must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).V-220370MEDIUMMarkLogic Server must separate user functionality (including user interface services) from database management functionality.V-220371MEDIUMMarkLogic Server must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.V-220372HIGHMarkLogic Server must protect the confidentiality and integrity of all information at rest.V-220373MEDIUMAccess to MarkLogic Server files must be limited to relevant processes and to authorized, administrative users.V-220374MEDIUMMarkLogic 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.V-220375MEDIUMMarkLogic Server must associate organization-defined types of security labels having organization-defined security label values with information in process.V-220376MEDIUMMarkLogic Server must associate organization-defined types of security labels having organization-defined security label values with information in transmission.V-220377MEDIUMMarkLogic Server must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.V-220378MEDIUMExecution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.V-220380MEDIUMMarkLogic Server must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.V-220381MEDIUMMarkLogic Server must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.V-220382MEDIUMMarkLogic Server must provide an immediate real-time alert to appropriate support staff of all audit failures.V-220383MEDIUMMarkLogic Server must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s).V-220384MEDIUMMarkLogic 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.V-220385MEDIUMMarkLogic Server must prohibit the use of cached authenticators after an organization-defined time period.V-220386MEDIUMMarkLogic 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.V-220387HIGHMarkLogic 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.V-220388HIGHMarkLogic Server must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.V-220389MEDIUMSecurity-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).V-220390MEDIUMMarkLogic Server must be able to generate audit records when security objects are accessed.V-220391MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to access security objects occur.V-220392MEDIUMMarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.V-220393MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.V-220394MEDIUMMarkLogic Server must generate audit records when privileges/permissions are added.V-220395MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to add privileges/permissions occur.V-220396MEDIUMMarkLogic Server must generate audit records when privileges/permissions are modified.V-220397MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to modify privileges/permissions occur.V-220398MEDIUMMarkLogic Server must generate audit records when security objects are modified.V-220399MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to modify security objects occur.V-220400MEDIUMMarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are modified.V-220401MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.V-220402MEDIUMMarkLogic Server must generate audit records when privileges/permissions are deleted.V-220403MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to delete privileges/permissions occur.V-220404MEDIUMMarkLogic Server DBMS must generate audit records when security objects are deleted.V-220405MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to delete security objects occur.V-220406MEDIUMMarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.V-220407MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.V-220408MEDIUMMarkLogic Server must generate audit records when successful logons or connections occur.V-220409MEDIUMMarkLogic Server must generate audit records when unsuccessful logons or connection attempts occur.V-220410MEDIUMMarkLogic Server must generate audit records for all privileged activities or other system-level access.V-220411MEDIUMMarkLogic Server must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.V-220412MEDIUMMarkLogic Server must generate audit records when concurrent logons/connections by the same user from different workstations occur.V-220413MEDIUMMarkLogic must be able to generate audit records when successful accesses to objects occur.V-220414MEDIUMMarkLogic Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.V-220415MEDIUMMarkLogic Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.V-220416MEDIUMMarkLogic 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.V-220417LOWMarkLogic 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.V-220418MEDIUMMarkLogic 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.V-265874HIGHMarkLogic Server must be a version supported by the vendor.