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

Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.

DISA Rule

SV-220378r961359_rule

Vulnerability Number

V-220378

Group Title

SRG-APP-000342-DB-000302

Rule Version

ML09-00-006800

Severity

CAT II

CCI(s)

• CCI-002233 - Prevent the organization-defined software from executing at higher privilege levels than users executing the software.

Weight

10

Fix Recommendation

Correcting issues with unnecessary elevated privileges, and access to or execution of system resources, is a two-step process.

Correcting custom code/module permissions:
When inserting custom code into a given Modules database, ensure those custom modules have the correct permissions applied by writing them to the database with the applicable/correct document permissions. The permissions should specify specific roles and permissions (i.e., read, update, execute)

Correcting User privileges:
1. Navigate to the MarkLogic Admin page >> Security >> Roles.
2. Select a role under consideration and add/remove specific roles or permissions allowing the required level of permissions for a given role.
3. Save the configuration.
4. Navigate to the MarkLogic Admin page >> Security >> Users.
5. Select a user under consideration and add or remove applicable roles providing the user with the least level of privileges required for acceptable interaction with the system.
6. Repeat as required for each User and Role (usually these are user-defined roles or users).

Check Contents

By default, MarkLogic does not allow any user to perform any actions within or against the system unless that user is assigned specific roles granting access/execution privileges.

All read, update, or execute privileges are defined by specifying applicable system roles/permissions.

1. Verify MarkLogic user-defined modules are created and stored with applicable document permissions.
2. Verify users interacting with the system are assigned to roles with the least amount of privileges required for a given user.
3. Navigate to the MarkLogic Admin page >> Security >> Users.
4. Validate all system users are assigned to roles with the least amount of privileges necessary while allowing them to interact with system resources and perform applicable actions based upon their use case.

If a user is assigned roles exceeding their required access/privilege level, this is a finding.

If custom modules are stored with unnecessary elevated document permissions, this is finding.

Vulnerability Number

V-220378

Documentable

False

Rule Version

ML09-00-006800

Severity Override Guidance

By default, MarkLogic does not allow any user to perform any actions within or against the system unless that user is assigned specific roles granting access/execution privileges.

All read, update, or execute privileges are defined by specifying applicable system roles/permissions.

1. Verify MarkLogic user-defined modules are created and stored with applicable document permissions.
2. Verify users interacting with the system are assigned to roles with the least amount of privileges required for a given user.
3. Navigate to the MarkLogic Admin page >> Security >> Users.
4. Validate all system users are assigned to roles with the least amount of privileges necessary while allowing them to interact with system resources and perform applicable actions based upon their use case.

If a user is assigned roles exceeding their required access/privilege level, this is a finding.

If custom modules are stored with unnecessary elevated document permissions, this is finding.

Check Content Reference

M

Target Key

4064