MarkLogic Server v9 STIG Version Comparison

There are 2 differences between versions v2 r2 (Jan. 24, 2024) (the "left" version) and v3 r2 (Oct. 24, 2024) (the "right" version).

Check ML09-00-007000 was removed from the benchmark in the "right" version. The text below reflects the old wording.

This check's original form is available here.

Title

MarkLogic Server must utilize centralized management of the content captured in audit records generated by all components of the DBMS.

Check Content

Review the system documentation for a description of how audit records are off-loaded and how local audit log space is managed. If the MarkLogic Server instance is not monitored by a MarkLogic Ops Director server, or a third-party log/audit management tool, this is a finding.

Discussion

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 content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.

Fix

Configure and/or deploy software tools to ensure that MarkLogic audit records are written directly to, or systematically transferred to, a centralized log management system. Add the MarkLogic Server instance under the monitoring of a MarkLogic Ops Director server. Use MarkLogic Server - Ops Director Guide Rev 2.0.1 as a reference. Alternatively, use a third-party audit/log management tool.