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

From vRealize - Cassandra Security Technical Implementation Guide

Associated with: CCI-000172

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

Vulnerability discussion

Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative.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 configuration to ensure audit records are generated when unsuccessful attempts to modify security objects occur. Open console to the server, Cassandra DB is hosted at, and type: "find / | grep "logback.xml"". Open "logback.xml" file and review "level" parameter value under . If level is not set to "ALL", this is a finding.

Fix text

Configure the Cassandra Server to generate audit records when unsuccessful attempts to modify security objects occur. Open console to the server, Cassandra DB is hosted at, and type: "find / | grep "logback.xml"". Open "logback.xml" file and set "level" parameter value under to "ALL".

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.