When invalid inputs are received, the Cassandra Server must behave in a predictable and documented manner that reflects organizational and system objectives.

From vRealize - Cassandra Security Technical Implementation Guide

Part of SRG-APP-000447-DB-000393

Associated with: CCI-002754

SV-87321r1_rule When invalid inputs are received, the Cassandra Server must behave in a predictable and documented manner that reflects organizational and system objectives.

Vulnerability discussion

A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.

Check content

Review the Cassandra Server to ensure that it behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. Open the "cqlsh" prompt in the Cassandra Server and type "DESCRIBE KEYSPACES;". Type "DESCRIBE " for all the keyspace names that have been displayed as output for the first command. Review keyspaces content. Open the console to the server that Cassandra DB is hosted at and type: "find / | grep "logback.xml"". Open "logback.xml" file and review "level" parameter value under . If level is not set to "ALL", this is a finding.

Fix text

Configure the Cassandra Server to behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. Modify tables by adding constraints (CREATE TRIGGER IF NOT EXISTS ON , where TRIGGER triggered validation event). Open console to the server, Cassandra DB is hosted at, and type: "find / | grep "logback.xml"". Open "logback.xml" file and set "level" parameter value under to "ALL".

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.

Powered by sagemincer