How do I install the Cis Cassandra41 5.2 skill?

Run npx skillmds@latest add cyberstrikeus/cis-cassandra41-5-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Cis Cassandra41 5.2 skill do?

Client Encryption It is listed under Coding & Dev Tools on SkillMD.

Is Cis Cassandra41 5.2 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cis Cassandra41 5.2?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cis Cassandra41 5.2 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cis Cassandra41 5.2?

cyberstrikeus (@cyberstrikeus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cis Cassandra41 5.2 by cyberstrikeus

Name: Cis Cassandra41 5.2
Author: cyberstrikeus

File contents

5.2 Client Encryption

Profile Applicability

Level 1 - Cassandra on Linux

Description

Cassandra offers the option to encrypt data in transit between the client and nodes on the cluster. By default client encryption is turned off.

Rationale

Data in transit between the client and node on the cluster should be encrypted to avoid network snooping, whether legitimate or not.

Audit

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.

Remediation

The client encryption should be implemented before anyone accesses the Cassandra server. To enable the client encryption mechanism:

Stop the Cassandra database.
If not done so already, build out your keystore and truststore.
Modify cassandra.yaml file to modify/add entries under client_encryption_options:

client_encryption_options:
  enabled: true
  optional: false
  keystore: /path/to/keystore
  keystore_password: <password>
  require_client_auth: false
  truststore: /path/to/truststore
  truststore_password: <password>
  protocol: TLS
  algorithm: SunX509
  store_type: JKS
  cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA]

Start the Cassandra database.

Default Value

enabled: false
optional: false

References

http://cassandra.apache.org/doc/latest/operating/security.html

CIS Controls

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.

Profile

Level 1 | Automated

---name: cis-cassandra41-5-2description: Client Encryption---# 5.2 Client Encryption## Profile Applicability- Level 1 - Cassandra on Linux## DescriptionCassandra offers the option to encrypt data in transit between the client and nodes on the cluster. By default client encryption is turned off.## RationaleData in transit between the client and node on the cluster should be encrypted to avoid network snooping, whether legitimate or not.## AuditThe 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:````yamlenabled: trueoptional: 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.## RemediationThe client encryption should be implemented before anyone accesses the Cassandra server.To enable the client encryption mechanism:1. Stop the Cassandra database.2. If not done so already, build out your keystore and truststore.3. Modify `cassandra.yaml` file to modify/add entries under `client_encryption_options:````yamlclient_encryption_options: enabled: true optional: false keystore: /path/to/keystore keystore_password: <password> require_client_auth: false truststore: /path/to/truststore truststore_password: <password> protocol: TLS algorithm: SunX509 store_type: JKS cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA]```4. Start the Cassandra database.## Default Value```yamlenabled: falseoptional: false```## References1. http://cassandra.apache.org/doc/latest/operating/security.html## CIS Controls**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.## Profile- Level 1 | Automated

Frequently asked questions

Cis Cassandra41 5.2