The Cassandra Server must generate audit records when unsuccessful attempts to add privileges/permissions occur.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-72699 | VROM-CS-000290 | SV-87331r1_rule | Medium |
| Description |
|---|
| Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict individuals' and groups' privileges could go undetected. In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. |
| STIG | Date |
|---|---|
| vRealize - Cassandra Security Technical Implementation Guide | 2017-06-06 |
Details
| Check Text ( C-72855r1_chk ) |
|---|
| Review the Cassandra Server configuration to ensure audit records are generated when unsuccessful attempts to add privileges/permissions occur. At the command prompt, execute the following command: # grep ' If level is not set to "ALL", this is a finding. |
| Fix Text (F-79103r1_fix) |
|---|
| Configure the Cassandra Server to generate audit records when unsuccessful attempts to add privileges/permissions occur. At the command line execute the following command: # sed -i 's/^\(\s*\) |