The Cassandra database must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.

From vRealize - Cassandra Security Technical Implementation Guide

Associated with: CCI-000171

SV-87257r1_rule The Cassandra database must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.

Vulnerability discussion

Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events.Suppression of auditing could permit an adversary to evade detection.Misconfigured audits can degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.

Check content

Check the Cassandra Server settings and documentation to determine whether designated personnel are able to select which auditable events are being audited. At the command prompt, execute the following command: # ls -al /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml If the permissions are not "0640", this is a finding.

Fix text

Configure the Cassandra Server settings to allow designated personnel to select which auditable events are audited. At the command line 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.