UCF STIG Viewer Logo

The Cassandra database logs must have the correct group-owner.


Overview

Finding ID Version Rule ID IA Controls Severity
V-72751 VROM-CS-000075 SV-87383r1_rule Medium
Description
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods which will depend upon system architecture and design. Some commonly employed methods include: ensuring log files enjoy the proper file system permissions utilizing file system protections; restricting access; and backing up log data to ensure log data is retained. Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit data. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. Deletion of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.
STIG Date
vRealize - Cassandra Security Technical Implementation Guide 2017-06-06

Details

Check Text ( C-72893r1_chk )
Review the Cassandra Server settings to ensure logs have the correct group-owner.

At the command prompt, execute the following command:

# ls -lL /storage/log/vcops/log/cassandra

If any file is not group-owned by "admin", this is a finding.
Fix Text (F-79155r1_fix)
Configure the Cassandra Server logs to have the correct group-owner.

At the command prompt, execute the following command:

# chown admin /storage/log/vcops/log/cassandra/

Replace with any file that has the incorrect group-owner.