From vRealize - Cassandra Security Technical Implementation Guide
Part of SRG-APP-000179-DB-000114
Associated with: CCI-000803
Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak algorithms can be easily broken and not validated cryptographic modules may not implement algorithms correctly. Unapproved cryptographic modules or algorithms should not be relied on for authentication, confidentiality or integrity. Weak cryptography could allow an attacker to gain access to and modify data stored in the database as well as the administration settings of the DBMS.
Review the Cassandra Server configuration to ensure NIST FIPS 140-2 validated cryptographic modules are used for cryptographic operations.
Review the Apache2 configuration by opening the /etc/apache2/ssl-global.conf file.
Search for the
Configure the Cassandra Server to use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
To enable the FIPS mode of operation, complete the following steps:
Replace the mod_ssl.so with the following command:
cd /usr/lib64/apache2-prefork/
cp mod_ssl.so mod_ssl.so.old
cp mod_ssl.so.FIPSON.openssl1.0.2 mod_ssl.so
Modify your Apache2 configuration by editing the /etc/apache2/ssl-global.conf file.
Search for the
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