TMA-CASSANDRA-4.2
Ensure that auditing is enabled
Description
Audit logging in Cassandra logs every incoming CQL command request, Authentication (successful as well as unsuccessful login) to C* node. Currently, there are two implementations provided, the custom logger can be implemented and injected with the class name as a parameter in cassandra.yaml. The benchmark rates this recommendation Manual; the automated check covers its objective pass criterion. Checks /etc/cassandra/cassandra.yaml (package install; SKIP when it does not exist).
How it is checked
Audit method: File pattern
- File
/etc/cassandra/cassandra.yaml- Pattern
(?m)^audit_logging_options:[ \t]*\n(?:[ \t]*(?:#[^\n]*)?\n|[ \t]+[^\n]*\n)*?[ \t]+enabled:[ \t]*['\x22]?true\b
How it is fixed
Fix method: Guidance or infrastructure patch
Set audit_logging_options.enabled: true (logger BinAuditLogger or FileAuditLogger, with included_categories) in cassandra.yaml and restart, or run nodetool enableauditlog on each node.
Properties
- Operating systems
- Any
- Tags
- cassandraloggingaudit
- Reference
- CIS Apache Cassandra 5.0 Benchmark v1.1.0 - 4.2 Ensure that auditing is enabled
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
tmaegis scan --target cassandra