The Cassandra Server must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-72733 | VROM-CS-000390 | SV-87365r1_rule | Medium |
| Description |
|---|
| Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system. |
| STIG | Date |
|---|---|
| vRealize - Cassandra Security Technical Implementation Guide | 2017-06-06 |
Details
| Check Text ( C-72889r1_chk ) |
|---|
| Review the Cassandra Server to ensure audit data is off-loaded to a separate log management facility. At the command prompt, execute the following command: # grep SyslogAppender /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml If level is not set to "ALL", this is a finding. |
| Fix Text (F-79153r1_fix) |
|---|
| Configure the Cassandra Server to off-load audit data to a separate log management facility. Navigate to and open /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml. Navigate to the Add the following Navigate to the Add the following to the |