The Cassandra database log configuration file must have the correct group-owner.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-72645	VROM-CS-000090	SV-87277r1_rule		Medium

Description

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

STIG	Date
vRealize - Cassandra Security Technical Implementation Guide	2017-06-06

Details

Check Text ( C-72801r1_chk )
Review the Cassandra Server settings to ensure the log configuration file has the correct group-owner. At the command prompt, execute the following command: # ls -l /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml If the file is not group-owned by "admin", this is a finding.

Fix Text (F-79049r1_fix)
Configure the Cassandra Server log configuration file to have the correct group-owner. At the command prompt, execute the following command: # chown admin /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml