Skip to content
Back to skills

Cis Cassandra311 2.1

ASecurity

Ensure that authentication is enabled for Cassandra databases

  • 2,182 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 30, 2026
securitygobashdatabasesecurity

Works with

  • cli

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-cassandra311-2.1 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis Cassandra311 2.1?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cis Cassandra311 2.1
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-cassandra311-2-1/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-cassandra311-2-1)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cis-cassandra311-2.1
description: "Ensure that authentication is enabled for Cassandra databases"
category: cis-cassandra
version: "1.1.0"
author: cyberstrike-official
tags: [cis, cassandra, authentication, authorization]
cis_id: "2.1"
cis_benchmark: "CIS Apache Cassandra 3.11 Benchmark v1.1.0"
tech_stack: [cassandra]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---

# 2.1 Ensure that authentication is enabled for Cassandra databases

## Profile Applicability

- Level 1 - Cassandra on Linux
- Level 2 - Cassandra on Linux

## Description

Authentication is pluggable in Cassandra and is configured using the authenticator setting in cassandra.yaml. Cassandra ships with two options included in the default distribution, AllowAllAuthenticator and PasswordAuthenticator. The default, AllowAllAuthenticator, performs no authentication checks and therefore requires no credentials. It is used to disable authentication completely. The second option, PasswordAuthenticator, stores encrypted credentials in a system table. This can be used to enable simple username/password authentication.

## Rationale

Authentication is a necessary condition of Cassandra's permissions subsystem, so if authentication is disabled then so are permissions. Failure to authenticate clients, users, and/or servers can allow unauthorized access to the Cassandra database and can prevent tracing actions back to their sources. The authentication mechanism should be implemented before anyone accesses the Cassandra server.

## Audit

Run the following command to verify whether authentication is enabled (authenticator values set to PasswordAuthenticator) on the Cassandra server.
The Cassandra configuration files can be found in the conf directory of tarballs. For packages, the configuration files will be located in /etc/cassandra.

```bash
cat cassandra.yaml | grep -in "authenticator:"
```

If authenticator is set to AllowAllAuthenticator, then this is a finding.

## Remediation

To enable the authentication mechanism:

1. Stop the Cassandra database.
2. Modify cassandra.yaml file to modify/add entry for authenticator: set it to PasswordAuthenticator
3. Start the Cassandra database.

## Default Value

```
authenticator: AllowAllAuthenticator
```

## References

1. http://cassandra.apache.org/doc/latest/getting_started/configuring.html
2. http://cassandra.apache.org/doc/latest/operating/security.html

## CIS Controls

- v8: 16.11 Leverage Vetted Modules or Services for Application Security Components
- v7: 14.7 Enforce Access Control to Data through Automated Tools

## Profile

- Level 1 | Automated

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.