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

From vRealize - Cassandra Security Technical Implementation Guide

Associated with: CCI-001495

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

Vulnerability discussion

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.

Check content

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

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

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.