The Cassandra database log configuration file must be protected from unauthorized read access.

From vRealize - Cassandra Security Technical Implementation Guide

Part of SRG-APP-000121-DB-000202

Associated with: CCI-001493

SV-87273r1_rule The Cassandra database log configuration file must be protected from unauthorized read access.

Vulnerability discussion

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access. 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 access to audit tools.Audit tools include, but are not limited to, OS-provided audit tools, vendor-provided audit tools, and open source audit tools needed to successfully view and manipulate audit information system activity and records. If an attacker were to gain access to audit tools, he could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.

Check content

Review the Cassandra Server settings to ensure the log configuration file is protected from unauthorized read access. At the command prompt, execute the following command: # ls -l /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml If the file does not have permissions of "0640", this is a finding.

Fix text

Configure the Cassandra Server log configuration file to be protected from unauthorized read access. At the command prompt, execute the following command: # chmod 0640 /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.

Powered by sagemincer