The Cassandra database log configuration file must set internode encryption.

From vRealize - Cassandra Security Technical Implementation Guide

Associated with: CCI-000197

SV-87293r1_rule The Cassandra database log configuration file must set internode encryption.

Vulnerability discussion

The DoD standard for authentication is DoD-approved PKI certificates.Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval.In such cases, passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission.DBMS passwords sent in clear text format across the network are vulnerable to discovery by unauthorized users. Disclosure of passwords may easily lead to unauthorized access to the database.

Check content

Review configuration settings for encrypting passwords in transit across the network. If passwords are not encrypted, this is a finding. At the command prompt, execute the following command: # grep '^\s*internode_encryption:' /usr/lib/vmware-vcops/user/conf/cassandra/cassandra.yaml If the line below is returned, this is a finding: internode_encryption: all

Fix text

Configure encryption for transmission of passwords across the network. If the database does not provide encryption for logon events natively, employ encryption at the OS or network level. At the command line execute the following command: # sed -i 's/^.*\binternode_encryption:.*$/internode_encryption: all/' /usr/lib/vmware-vcops/user/conf/cassandra/cassandra.yaml

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.