OpenControls Logo

STIG Viewer

STIGViewer Support

MarkLogic Server software installation account must be restricted to authorized users.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-220356ML09-00-002600SV-220356r960960_ruleCCI-001499medium
Description
When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application could have significant effects on the overall security of the system. If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qualified and authorized individuals must be allowed access to information system components for purposes of initiating changes, including upgrades and modifications. DBA and other privileged administrative or application owner accounts are granted privileges that allow actions that can have a great impact on database security and operation. It is especially important to grant privileged access to only those persons who are qualified and authorized to use them.
STIGDate
MarkLogic Server v9 Security Technical Implementation Guide2024-09-04

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CHG-04.5Library Privileges
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (56) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00

+46 more (top 10 by confidence shown)

CCI1 mapping
CCI-001499
1.00

Details

Check Text (C-220356r960960_chk)

Review procedures for controlling, granting access to, and tracking use of the MarkLogic software installation account. If access or use of this account is not restricted to the minimum number of personnel required or if unauthorized access to the account has been granted, this is a finding. At a command prompt, on the system where MarkLogic is installed run the following command: > ls -al /var/opt/MarkLogic If files are owned by the user "daemon", this is not a finding. If user is not "daemon", verify that Organization policy and system documentation states that a separate user is needed and approved.

Fix Text (F-22060r401520_fix)

Review procedures for controlling, granting access to, and tracking the use of the MarkLogic software installation account. Ensure use of this account is restricted to the minimum number of personnel required and no unauthorized access to the account has been granted. MarkLogic should be installed by a user account that has "sudo" privileges to run "yum" or "rpm". At a command prompt, on the system where MarkLogic is installed, run one of the following commands: > sudo yum install /path/to/MarkLogic-version.rpm or > sudo rpm -i /path/to/MarkLogic-version.rpm Either of these commands will install MarkLogic with the owner set correctly to "daemon". If user is not "daemon", ensure Organization policy and system documentation states that a separate user is needed and approved.