The Cassandra Server must generate audit records when unsuccessful attempts to access security objects occur.

From vRealize - Cassandra Security Technical Implementation Guide

Associated with: CCI-000172

SV-87327r1_rule The Cassandra Server must generate audit records when unsuccessful attempts to access security objects occur.

Vulnerability discussion

Changes to the security configuration must be tracked.This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality.In an SQL environment, types of access include, but are not necessarily limited to:SELECTINSERTUPDATEDELETEEXECUTETo aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Check content

Review the Cassandra Server configuration to ensure audit records are generated when unsuccessful attempts to access security objects occur. At the command prompt, execute the following command: # grep '

Fix text

Configure the Cassandra Server to generate audit records when unsuccessful attempts to access security objects occur. At the command line execute the following command: # sed -i 's/^$\s*$$\s*$$/\1\2/' /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.