基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-cassandra5-5-2命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
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
| name | cis-cassandra5-5.2 |
| description | Client Encryption |
| category | cis-cassandra |
| version | 1.1.0 |
| author | cyberstrike-official |
| tags | ["cis","cassandra","linux","database","nosql","encryption","tls"] |
| cis_id | 5.2 |
| cis_benchmark | CIS Apache Cassandra 5.0 Benchmark v1.1.0 |
| tech_stack | ["linux","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.
None
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 entry for client_encryption_options section:
enabled to trueoptional to false (to require encryption for all connections)client_encryption_options:
enabled: false
optional: false
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.10 Encrypt Sensitive Data in Transit Encrypt sensitive data in transit. Example implementations can include: Transport Layer Security (TLS) and Open Secure Shell (OpenSSH). | ● | ● | |
| v7 | 14.4 Encrypt All Sensitive Information in Transit Encrypt all sensitive information in transit. | ● | ● |