Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-cassandra40-v130-5-2The command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
Based on SOC occupation classification
Showing SKILL.md
| name | cis-cassandra40-v130-5.2 |
| description | Client Encryption |
| category | cis-cassandra |
| version | 1.3.0 |
| author | cyberstrike-official |
| tags | ["cis","cassandra","encryption","tls","ssl"] |
| cis_id | 5.2 |
| cis_benchmark | CIS Apache Cassandra 4.0 Benchmark v1.3.0 |
| tech_stack | ["cassandra"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Cassandra offers the option to encrypt data in transit between the client and nodes on the cluster. By default client encryption is turned off.
Data in transit between the client and node on the cluster should be encrypted to avoid network snooping, whether legitimate or not.
The Cassandra configuration files can be found in the conf directory of tarballs. For packages, the configuration files will be located in /etc/cassandra.
Open up the cassandra.yaml file, look for client_encryption_options section.
Look for enabled: and optional:
enabled: true
optional: false
If neither is true, then all client connections are unencrypted which makes this a finding.
If enabled is true and optional is false, then all client connections must be encrypted which makes this not a finding.
If enabled is false and optional is true, then enabled wins and all client connections are unencrypted which makes this a finding.
If both are set to true, then both unencrypted and encrypted connections are allowed on the same port which makes this not a finding.
You can also excuse this command
cat cassandra.yaml | grep -A7 -in "client_encryption_options:"
or
cat cassandra.yaml | grep -A2 -in "client_encryption_options:"
If enabled is set to true, then success. Anything else is a finding.
The client encryption should be implemented before anyone accesses the Cassandra server.
To enable the client encryption mechanism:
cassandra.yaml file to modify/add entries under client_encryption_options:set enabled:
This will force all connections to be encrypted between client and node on the cluster.
enabled: false
optional: false
Controls Version v8:
Controls Version v7: