Cis Cassandra40 V110 4.1
DevOps & Securitycis-cassandra40-v110-4.1Cis Cassandra40 V110 4.1 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Ensure that logging is enabled
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Server_Software/Apache_Cassandra/CIS_Apache_Cassandra_4.0_Benchmark_v1.1.0/cis-cassandra40-v110-4.1/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-cassandra40-v110-4-1, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
4.1 Ensure that logging is enabled
Profile Applicability
- Level 1 - Cassandra
- Level 1 - Cassandra on Linux
Description
Apache Cassandra uses Logback for logging functionality. While this can be set using nodetool setlogginglevel changes made using this method will be reverted to the level specified in the logback.xml file the next time the process restarts.
The configurable logging levels are:
OFFTRACEDEBUGINFO(Default)WARNERROR
Rationale
If logging is not enabled, issues may go undiscovered, and compromises and other incidents may occur without being quickly detected. It may also not be possible to provide evidence of compliance with security laws, regulations, and other requirements.
Audit
Execute the following command to confirm the setting is correct:
$ nodetool getlogginglevels
Logger Name Log Level
ROOT INFO
org.clsecurity.workbench WARN
If set to OFF then this is a finding.
Remediation
To remediate this setting:
- Edit the
logback-test.xmlif present; otherwise, edit thelogback.xml - Add or update the configuration section as follows:
<configuration scan="true">
<appender name="STDOUT"
class="ch.qos.logback.core.ConsoleAppender">
<filter class="ch.qos.logback.classic.filter.ThresholdFilter">
<level>INFO</level>
</filter>
<encoder>
<pattern>%*-5level [%thread] %date{ISO8601} %F:%L -
%msg%n</pattern>
</encoder>
</appender>
<root level="INFO">
<appender-ref ref="STDOUT" />
</root>
<logger name="org.clsecurity.workbench" level="WARN"/>
</configuration>
- Restart the Apache Cassandra
Default Value
INFO
References
- http://cassandra.apache.org/doc/latest/troubleshooting/reading_logs.html?highlight=logging
- https://logback.qos.ch/manual/configuration.html
CIS Controls
v8:
- 8.5 Collect Detailed Audit Logs - Configure detailed audit logging for enterprise assets containing sensitive data. Include event source, date, username, timestamp, source addresses, destination addresses, and other useful elements that could assist in a forensic investigation.
v7:
- 6.3 Enable Detailed Logging - Enable system logging to include detailed information such as an event source, date, user, timestamp, source addresses, destination addresses, and other useful elements.
Profile
- Level 1 | Automated