The Cassandra database must produce audit records containing sufficient information to establish what type of events occurred.
From vRealize - Cassandra Security Technical Implementation Guide
Part of SRG-APP-000095-DB-000039
Associated with:
CCI-000130
SV-87265r1_rule
The Cassandra database must produce audit records containing sufficient information to establish what type of events occurred.
Vulnerability discussion
Information system auditing capability is critical for accurate forensic analysis. Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit record content that may be necessary to satisfy the requirement of this policy includes, for example, time stamps, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.Associating event types with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application. Database software is capable of a range of actions on data stored within the database. It is important, for accurate forensic analysis, to know exactly what actions were performed. This requires specific information regarding the event type an audit record is referring to. If event type information is not recorded and stored with the audit record, the record itself is of very limited use.
Check content
Review the Cassandra Server settings to ensure audit records containing sufficient information to establish what type of events occurred are produced.
Navigate to and open /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml.
Navigate to the node with the name="FILE" attribute.
Navigate to node.
If the node does not look like the expected result, this is a finding.
Expected result:
%-5level [%thread] %date{ISO8601, UTC} %F:%L - %msg%n
Fix text
Configure the Cassandra Server to produce audit records containing sufficient information to establish what type of events occurred.
Navigate to and open /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml.
Navigate to the node with the name="FILE" attribute.
Navigate to node.
Edit the to look like the below.
%-5level [%thread] %date{ISO8601, UTC} %F:%L - %msg%n
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.
Powered by sagemincer