STIGQter: STIG Summary: MarkLogic Server v9 Security Technical Implementation Guide Version: 3 Release: 2 Benchmark Date: 24 Oct 2024:

MarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.

DISA Rule

SV-220392r961797_rule

Vulnerability Number

V-220392

Group Title

SRG-APP-000494-DB-000344

Rule Version

ML09-00-009500

Severity

CAT II

CCI(s)

• CCI-000172 - Generate audit records for the event types defined in AU-2 c that include the audit record content defined in AU-3.

Weight

10

Fix Recommendation

Configure MarkLogic to produce audit records when categories of information are accessed, to include reads, creations, modifications, and deletions.

Perform the fix from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges.

1. Click the Groups icon.
2. Click the group in which the configuration to check resides (e.g., Default).
3. Click the Auditing icon on the left tree menu.
4. Set the audit enabled field to true.
5. Enable the document-read event for auditing.
6. Enable "both" for the audit restriction under the outcome selection.
7. Add the role that encompasses the categories of information that need auditing. See MarkLogic Server - Using Security Guide 9.0-9, Ch 5, Section 2: Configuring Compartment Security, for information on defining the categories of information by using compartmented security.

Check Contents

Review the DBMS/database security and audit configurations to verify that audit records are produced when categories of information are accessed, to include reads, creations, modifications, and deletions.

If they are not produced, this is a finding.

Perform the check from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges.

1. Click the Groups icon.
2. Click the group in which the configuration to be checked resides (e.g., Default).
3. Click the Auditing icon on the left tree menu.
4. Inspect the audit enabled field, a value of false means there is no auditing identifying the individual user, this is a finding.
5. If audit enabled field is true but the document-read event is not selected, this is a finding.
6. Under the Audit Restrictions - Outcome section, verify the security-access event for auditing is set to "both". If the setting is not both, this is a finding.
7. If the role that has been configured for the category of information is not included under the audit restriction roles, this is a finding.

Vulnerability Number

V-220392

Documentable

False

Rule Version

ML09-00-009500

Severity Override Guidance

Review the DBMS/database security and audit configurations to verify that audit records are produced when categories of information are accessed, to include reads, creations, modifications, and deletions.

If they are not produced, this is a finding.

Perform the check from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges.

1. Click the Groups icon.
2. Click the group in which the configuration to be checked resides (e.g., Default).
3. Click the Auditing icon on the left tree menu.
4. Inspect the audit enabled field, a value of false means there is no auditing identifying the individual user, this is a finding.
5. If audit enabled field is true but the document-read event is not selected, this is a finding.
6. Under the Audit Restrictions - Outcome section, verify the security-access event for auditing is set to "both". If the setting is not both, this is a finding.
7. If the role that has been configured for the category of information is not included under the audit restriction roles, this is a finding.

Check Content Reference

M

Target Key

4064