SV-251210r960960_rule
V-251210
SRG-APP-000133-DB-000179
RD6X-00-007300
CAT II
10
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. Syslog can be used to track and monitor access, deletions, and modification actions of the Redis logs, system configuration files, and binaries stored on the RHEL OS.
Ensure that the permissions of the Redis logs, system configuration files, and binaries are set so that only those with admin privileges can modify them on the hosting RHEL OS. Permissions can be modified using the chmod command.
The RHEL server OS must be STIG-compliant to ensure only appropriate users have access. Verify user ownership, group ownership, and permissions on the directories where the Redis logs, binaries ,and modules reside:
From Linux command line as root, perform the command ls –ald on the following directory paths:
/var/opt/redislabs - Default storage location for the cluster data, system logs, backups and ephemeral, persisted data
/var/opt/redislabs/log - System logs for Redis Enterprise Software
/var/opt/redislabs/run - Socket files for Redis Enterprise Software
/etc/opt/redislabs - Default location for cluster manager configuration and certificates
/opt/redislabs - Main installation directory for all Redis Enterprise Software binaries
/opt/redislabs/bin - Binaries for all the utilities for command line access and managements such as "rladmin" or "redis-cli"
/opt/redislabs/config - System configuration files
/opt/redislabs/lib - System library files
/opt/redislabs/sbin - System binaries for tweaking provisioning
If the user owner is not a defined admin, this is a finding.
If the group owner is not a defined admin group, this is a finding.
If the directory is more permissive than 700, this is a finding.
Review monitoring procedures and implementation evidence to verify monitoring of changes to database software libraries, related applications, and configuration files is done. This is performed on the RHEL OS utilizing syslog.
Verify the list of files, directories, and database application objects (procedures, functions, and triggers) being monitored is complete.
If monitoring does not occur or the list of monitored objects is not complete, this is a finding.
V-251210
False
RD6X-00-007300
The RHEL server OS must be STIG-compliant to ensure only appropriate users have access. Verify user ownership, group ownership, and permissions on the directories where the Redis logs, binaries ,and modules reside:
From Linux command line as root, perform the command ls –ald on the following directory paths:
/var/opt/redislabs - Default storage location for the cluster data, system logs, backups and ephemeral, persisted data
/var/opt/redislabs/log - System logs for Redis Enterprise Software
/var/opt/redislabs/run - Socket files for Redis Enterprise Software
/etc/opt/redislabs - Default location for cluster manager configuration and certificates
/opt/redislabs - Main installation directory for all Redis Enterprise Software binaries
/opt/redislabs/bin - Binaries for all the utilities for command line access and managements such as "rladmin" or "redis-cli"
/opt/redislabs/config - System configuration files
/opt/redislabs/lib - System library files
/opt/redislabs/sbin - System binaries for tweaking provisioning
If the user owner is not a defined admin, this is a finding.
If the group owner is not a defined admin group, this is a finding.
If the directory is more permissive than 700, this is a finding.
Review monitoring procedures and implementation evidence to verify monitoring of changes to database software libraries, related applications, and configuration files is done. This is performed on the RHEL OS utilizing syslog.
Verify the list of files, directories, and database application objects (procedures, functions, and triggers) being monitored is complete.
If monitoring does not occur or the list of monitored objects is not complete, this is a finding.
M
5443