TMA-CASSANDRA-5.2
Client Encryption
HighLevel 1Automatedcassandra
Description
Cassandra offers the option to encrypt data in transit between the client and nodes on the cluster. By default client encryption is turned off. Checks /etc/cassandra/cassandra.yaml (package install; SKIP when it does not exist). Passes when client_encryption_options.enabled is true; set optional: false to refuse unencrypted clients.
How it is checked
Audit method: File pattern
- File
/etc/cassandra/cassandra.yaml- Pattern
(?m)^client_encryption_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
Create a keystore, set client_encryption_options: {enabled: true, optional: false, keystore: ..., keystore_password: ...} in cassandra.yaml and rolling-restart; update drivers/cqlsh to use TLS.
Properties
- Operating systems
- Any
- Tags
- cassandraencryptiontls
- Reference
- CIS Apache Cassandra 5.0 Benchmark v1.1.0 - 5.2 Client Encryption
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
shell
tmaegis scan --target cassandra