Inter-node Encryption
Scanned 5/30/2026
Install via CLI
openskills install CyberStrikeus/CyberStrike---
name: cis-cassandra41-5.1
description: "Inter-node Encryption"
category: cis-cassandra
version: "1.0.0"
author: cyberstrike-official
tags: [cis, cassandra, encryption, tls, ssl, inter-node]
cis_id: "5.1"
cis_benchmark: "CIS Apache Cassandra 4.1 Benchmark v1.0.0"
tech_stack: [cassandra]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# 5.1 Inter-node Encryption
## Profile Applicability
- Level 1 - Cassandra on Linux
## Description
Cassandra offers the option to encrypt data in transit between nodes on the cluster. By default, inter-node encryption is turned off.
## Rationale
Data being transferred on the wire should be encrypted to avoid network snooping, whether legitimate or not.
## Audit
Run the following command to verify whether inter-node encryption is enabled.
```bash
cat cassandra.yaml | grep -in "internode_encryption:"
```
Acceptable values are `all`, `dc` or `rack`. If the `internode_encryption` is set to `none`, this is a finding.
**Note:** The Cassandra configuration files can be found in the conf directory of tarballs. For packages, the configuration files will be located in `/etc/cassandra`.
## Remediation
The inter-node encryption should be implemented before anyone accesses the Cassandra server.
To enable the inter-node 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 entry for `internode_encryption:` set it to `all`
4. Start the Cassandra database.
## Default Value
```
internode_encryption: none
```
## References
1. 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
No comments yet. Be the first to comment!
Set up the Globalize CLI, create a translation project, and connect a GitHub or GitLab repository. Use this skill when the user asks to set up Globalize, install the Globalize CLI, authenticate with Globalize, or connect their project to the Globalize translation platform. Also use when the user mentions @globalize-now/cli-client or globalise-now-cli. This skill handles installation, authentication, project creation, and repository connection. For managing existing projects (glossaries, style...
Team Mode security research skill. Orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity by actual exploitability. Use for security review, vulnerability research, exploitability audit, pre-release security check, threat model validation, and `/security-research`. Triggers: 'security-research', 'security research', 'security review', 'vulnerability audit', 'exploitability audit', '보안 리뷰', '취...
Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.