The Cassandra database must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.

From vRealize - Cassandra Security Technical Implementation Guide

Associated with: CCI-000172

SV-87261r1_rule The Cassandra database must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.

Vulnerability discussion

Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically make such information available through views or functions.This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted.To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Check content

Review the Cassandra Server settings to ensure that audit records can be produced when the system denies or fails to complete attempts to retrieve privileges/permissions/role membership. At the command prompt, execute the following command: # grep '

Fix text

Configure the Cassandra Server to produce audit records when other errors prevent access to privileges/permissions/role membership. 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.