MarkLogic Server must generate audit records when privileges/permissions are added.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-220394	ML09-00-009700	SV-220394r622777_rule		Medium

Description
Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users.

STIG	Date
MarkLogic Server v9 Security Technical Implementation Guide	2022-09-12

Details

Check Text ( C-22109r401633_chk )
Review MarkLogic security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are added. 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 check 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 and this is a finding. 5. If audit enabled field is true, but the user-role-addition 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.

Check Text ( C-22109r401633_chk )

Review MarkLogic security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are added.

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 check 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 and this is a finding.
5. If audit enabled field is true, but the user-role-addition 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.

Fix Text (F-22098r401634_fix)
Configure MarkLogic to produce audit records when privileges/permissions/role memberships are added. 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 be checked 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 user-role-addition event for auditing. 6. Enable "both" for the audit restriction under the outcome selection.

Fix Text (F-22098r401634_fix)

Configure MarkLogic to produce audit records when privileges/permissions/role memberships are added.

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 be checked 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 user-role-addition event for auditing.
6. Enable "both" for the audit restriction under the outcome selection.