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

MarkLogic Server must limit privileges to change software modules, including stored procedures, functions, and triggers, and links to software external to the DBMS.

DISA Rule

SV-220355r960960_rule

Vulnerability Number

V-220355

Group Title

SRG-APP-000133-DB-000179

Rule Version

ML09-00-002500

Severity

CAT II

CCI(s)

• CCI-001499 - Limit privileges to change software resident within software libraries.

Weight

10

Fix Recommendation

Implement procedures to monitor for unauthorized changes to DBMS software libraries, related software application libraries, and configuration files. If a third-party automated tool is not employed, an automated job that reports file information on the directories and files of interest and compares them to the baseline report for the same will meet the requirement.

The supplemental file "ml-filechange-mon.sh" can be used to meet this requirement.
- Edit the ml-filechange-mon.sh script with the correct email addresses and notification level.
- Place the script in a location that can be accessed by the cron daemon.
- Edit the crontab, and configure the script to run frequently enough to meet DoD minimum requirements.

Check Contents

Review monitoring procedures and implementation evidence to verify monitoring of changes to MarkLogic software libraries, related applications, and configuration files is done.

If a third-party file automated tool is used, this is not a finding.

To check for automated monitoring, issue the following command at a command prompt with a user that has administrative privileges:

Check to see if the crond service is running for scheduling recurring tasks.

If it is not running, this is a finding.
> sudo systemctl status crond

Check to see if ml-filechange-mon.sh is in the cron schedule, and runs frequently enough to meet System Security Plan (SSP) requirements. If the script is not scheduled to run, or does not run frequently enough to meet the SSP requirements, this is a finding.
> sudo crontab -l | grep ml-filechange

Check ml-filechange-mon.sh to verify email addresses have been configured to receive alerts. If no email addresses have been added, this is a finding.
> grep "EMAIL_LIST" /path/to/ml-filechange-mon.sh

Vulnerability Number

V-220355

Documentable

False

Rule Version

ML09-00-002500

Severity Override Guidance

Review monitoring procedures and implementation evidence to verify monitoring of changes to MarkLogic software libraries, related applications, and configuration files is done.

If a third-party file automated tool is used, this is not a finding.

To check for automated monitoring, issue the following command at a command prompt with a user that has administrative privileges:

Check to see if the crond service is running for scheduling recurring tasks.

If it is not running, this is a finding.
> sudo systemctl status crond

Check to see if ml-filechange-mon.sh is in the cron schedule, and runs frequently enough to meet System Security Plan (SSP) requirements. If the script is not scheduled to run, or does not run frequently enough to meet the SSP requirements, this is a finding.
> sudo crontab -l | grep ml-filechange

Check ml-filechange-mon.sh to verify email addresses have been configured to receive alerts. If no email addresses have been added, this is a finding.
> grep "EMAIL_LIST" /path/to/ml-filechange-mon.sh

Check Content Reference

M

Target Key

4064