CIS Apache Cassandra 4.1 Benchmark

This recommendation verifies that Cassandra Runs Under a Dedicated Service Account on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Cassandra Runs Under a Dedicated Service Account:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Cassandra Runs Under a Dedicated Service Account:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This setting ensures that Cassandra Configuration Directory Permissions Are Restricted on the Apache Cassandra NoSQL database. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the Apache Cassandra NoSQL database is essential for defense in depth.

Review the Cassandra configuration and verify that Cassandra Configuration Directory Permissions Are Restricted:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Cassandra Configuration Directory Permissions Are Restricted:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This setting ensures that Cassandra Data Directory Permissions Are Restricted on the Apache Cassandra NoSQL database. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the Apache Cassandra NoSQL database is essential for defense in depth.

Review the Cassandra configuration and verify that Cassandra Data Directory Permissions Are Restricted:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Cassandra Data Directory Permissions Are Restricted:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Latest Stable Version of Cassandra Is Installed on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Latest Stable Version of Cassandra Is Installed:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Latest Stable Version of Cassandra Is Installed:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Cluster Name Is Changed from Default on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Cluster Name Is Changed from Default:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Cluster Name Is Changed from Default:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that listen_address Is Bound to a Specific Interface on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that listen_address Is Bound to a Specific Interface:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure listen_address Is Bound to a Specific Interface:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that rpc_address Is Bound to a Specific Interface on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that rpc_address Is Bound to a Specific Interface:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure rpc_address Is Bound to a Specific Interface:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that JMX Listener Is Bound to Localhost on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that JMX Listener Is Bound to Localhost:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure JMX Listener Is Bound to Localhost:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that PasswordAuthenticator Is Enabled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that PasswordAuthenticator Is Enabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure PasswordAuthenticator Is Enabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Default cassandra Superuser Password Is Changed on the Apache Cassandra NoSQL database. Using the recommended component or protocol ensures alignment with security best practices and reduces risk.

Using an insecure or legacy component instead of the recommended approach increases the risk of compromise. Ensuring the Apache Cassandra NoSQL database uses the correct component aligns with industry best practices and standards.

Review the Cassandra configuration and verify that Default cassandra Superuser Password Is Changed:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Default cassandra Superuser Password Is Changed:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that a Custom Superuser Account Is Created on the Apache Cassandra NoSQL database. Using the recommended component or protocol ensures alignment with security best practices and reduces risk.

Using an insecure or legacy component instead of the recommended approach increases the risk of compromise. Ensuring the Apache Cassandra NoSQL database uses the correct component aligns with industry best practices and standards.

Review the Cassandra configuration and verify that a Custom Superuser Account Is Created:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure a Custom Superuser Account Is Created:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Default cassandra Superuser Account Is Disabled on the Apache Cassandra NoSQL database. Disabling or removing unnecessary components reduces the attack surface and limits potential vectors for exploitation.

Running unnecessary components on the Apache Cassandra NoSQL database increases the attack surface and the risk of exploitation. Disabling or removing them follows the principle of least functionality and reduces exposure to known vulnerabilities.

Review the Cassandra configuration and verify that Default cassandra Superuser Account Is Disabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Default cassandra Superuser Account Is Disabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that JMX Authentication Is Enabled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that JMX Authentication Is Enabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure JMX Authentication Is Enabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that JMX Remote Authentication Uses Strong Credentials on the Apache Cassandra NoSQL database. Using the recommended component or protocol ensures alignment with security best practices and reduces risk.

Using an insecure or legacy component instead of the recommended approach increases the risk of compromise. Ensuring the Apache Cassandra NoSQL database uses the correct component aligns with industry best practices and standards.

Review the Cassandra configuration and verify that JMX Remote Authentication Uses Strong Credentials:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure JMX Remote Authentication Uses Strong Credentials:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that JMX SSL Is Enabled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that JMX SSL Is Enabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure JMX SSL Is Enabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that CassandraAuthorizer Is Enabled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that CassandraAuthorizer Is Enabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure CassandraAuthorizer Is Enabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Role-Based Access Control Is Implemented on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Role-Based Access Control Is Implemented:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Role-Based Access Control Is Implemented:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This setting ensures that Superuser Roles Are Minimized on the Apache Cassandra NoSQL database. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the Apache Cassandra NoSQL database is essential for defense in depth.

Review the Cassandra configuration and verify that Superuser Roles Are Minimized:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Superuser Roles Are Minimized:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that GRANT and REVOKE Permissions Follow Least Privilege on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that GRANT and REVOKE Permissions Follow Least Privilege:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure GRANT and REVOKE Permissions Follow Least Privilege:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This setting ensures that Native Transport Port Is Restricted to Trusted Networks on the Apache Cassandra NoSQL database. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the Apache Cassandra NoSQL database is essential for defense in depth.

Review the Cassandra configuration and verify that Native Transport Port Is Restricted to Trusted Networks:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Native Transport Port Is Restricted to Trusted Networks:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This setting ensures that Inter-Node Communication Is Restricted on the Apache Cassandra NoSQL database. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the Apache Cassandra NoSQL database is essential for defense in depth.

Review the Cassandra configuration and verify that Inter-Node Communication Is Restricted:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Inter-Node Communication Is Restricted:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that CQL Native Transport Is Not Exposed Publicly on the Apache Cassandra NoSQL database. Disabling or removing unnecessary components reduces the attack surface and limits potential vectors for exploitation.

Running unnecessary components on the Apache Cassandra NoSQL database increases the attack surface and the risk of exploitation. Disabling or removing them follows the principle of least functionality and reduces exposure to known vulnerabilities.

Review the Cassandra configuration and verify that CQL Native Transport Is Not Exposed Publicly:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure CQL Native Transport Is Not Exposed Publicly:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Client-to-Node TLS Is Enabled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Client-to-Node TLS Is Enabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Client-to-Node TLS Is Enabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation ensures that TLS 1.2 or Higher Is Required for Client Connections on the Apache Cassandra NoSQL database. Enforcing this requirement establishes a minimum security standard and prevents insecure configurations.

Without this enforcement, the Apache Cassandra NoSQL database may accept insecure configurations that weaken overall security posture. Mandating this control ensures consistent protection against common attack vectors.

Review the Cassandra configuration and verify that TLS 1.2 or Higher Is Required for Client Connections:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure TLS 1.2 or Higher Is Required for Client Connections:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Strong Cipher Suites Are Used for Client Encryption on the Apache Cassandra NoSQL database. Using the recommended component or protocol ensures alignment with security best practices and reduces risk.

Using an insecure or legacy component instead of the recommended approach increases the risk of compromise. Ensuring the Apache Cassandra NoSQL database uses the correct component aligns with industry best practices and standards.

Review the Cassandra configuration and verify that Strong Cipher Suites Are Used for Client Encryption:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Strong Cipher Suites Are Used for Client Encryption:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Inter-Node TLS Is Enabled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Inter-Node TLS Is Enabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Inter-Node TLS Is Enabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation ensures that TLS 1.2 or Higher Is Required for Inter-Node Communication on the Apache Cassandra NoSQL database. Enforcing this requirement establishes a minimum security standard and prevents insecure configurations.

Without this enforcement, the Apache Cassandra NoSQL database may accept insecure configurations that weaken overall security posture. Mandating this control ensures consistent protection against common attack vectors.

Review the Cassandra configuration and verify that TLS 1.2 or Higher Is Required for Inter-Node Communication:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure TLS 1.2 or Higher Is Required for Inter-Node Communication:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Mutual TLS Authentication Is Configured for Inter-Node on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Mutual TLS Authentication Is Configured for Inter-Node:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Mutual TLS Authentication Is Configured for Inter-Node:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Certificates Are Rotated Regularly on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Certificates Are Rotated Regularly:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Certificates Are Rotated Regularly:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Audit Logging Is Enabled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Audit Logging Is Enabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Audit Logging Is Enabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that DML Audit Category Is Configured on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that DML Audit Category Is Configured:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure DML Audit Category Is Configured:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that AUTH Audit Category Is Configured on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that AUTH Audit Category Is Configured:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure AUTH Audit Category Is Configured:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that DDL Audit Category Is Configured on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that DDL Audit Category Is Configured:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure DDL Audit Category Is Configured:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Audit Logs Are Written to a Dedicated Directory on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Audit Logs Are Written to a Dedicated Directory:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Audit Logs Are Written to a Dedicated Directory:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Audit Log Rotation Is Configured on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Audit Log Rotation Is Configured:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Audit Log Rotation Is Configured:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Audit Logs Are Forwarded to SIEM on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Audit Logs Are Forwarded to SIEM:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Audit Logs Are Forwarded to SIEM:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Snapshot Backups Are Configured on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to properly configure this setting may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Snapshot Backups Are Configured:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Snapshot Backups Are Configured:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Incremental Backups Are Enabled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Incremental Backups Are Enabled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Incremental Backups Are Enabled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Backup Data Is Encrypted on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Backup Data Is Encrypted:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Backup Data Is Encrypted:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Cassandra Metrics Are Collected via JMX or Prometheus on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Cassandra Metrics Are Collected via JMX or Prometheus:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Cassandra Metrics Are Collected via JMX or Prometheus:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Compaction Strategy Is Reviewed on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Compaction Strategy Is Reviewed:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Compaction Strategy Is Reviewed:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Repair Operations Are Scheduled on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Repair Operations Are Scheduled:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Repair Operations Are Scheduled:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.

This recommendation verifies that Tombstone Warnings Are Monitored on the Apache Cassandra NoSQL database. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Failure to implement this control may leave the Apache Cassandra NoSQL database vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Review the Cassandra configuration and verify that Tombstone Warnings Are Monitored:

grep -i '...' /etc/cassandra/cassandra.yaml
nodetool status

Edit the Cassandra configuration to ensure Tombstone Warnings Are Monitored:

vi /etc/cassandra/cassandra.yaml

Restart the Cassandra service for changes to take effect.