How do I install the Cis Cassandra311 2.2 skill?

Run npx skillmds@latest add cyberstrikeus/cis-cassandra311-2-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 Cassandra311 2.2 skill do?

Ensure that authorization is enabled for Cassandra databases It is listed under Coding & Dev Tools on SkillMD.

Is Cis Cassandra311 2.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 Cassandra311 2.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 Cassandra311 2.2 free to use?

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

Who published Cis Cassandra311 2.2?

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

Cis Cassandra311 2.2 by cyberstrikeus

Name: Cis Cassandra311 2.2
Author: cyberstrikeus

File contents

2.2 Ensure that authorization is enabled for Cassandra databases

Profile Applicability

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

Description

Authorization is pluggable in Cassandra and is configured using the authorizer setting in cassandra.yaml. Cassandra ships with two options included in the default distribution, AllowAllAuthenticator and CassandraAuthorizer. The default, AllowAllAuthenticator performs no checking which grants all permissions to all roles. The second option, CassandraAuthorizer, implements full permissions management functionality and stores its data in Cassandra system tables.

Rationale

Authorizing roles is an important step towards ensuring only authorized access to the Cassandra database tables is permitted. It also provides the requisite means of implementing least privilege best practices. The authorization mechanism should be implemented before anyone accesses the Cassandra database.

Audit

Run the following command to verify whether authorization is enabled (authorization values set to CassandraAuthorizer) 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.

cat cassandra.yaml | grep -in "authorizer:"

If authorizer is set to AllowAllAuthorizer, then this is a finding.

Remediation

To enable the authorization mechanism:

Stop the Cassandra database.
Modify cassandra.yaml file to modify/add entry for authorization: set it to CassandraAuthorizer
Start the Cassandra database.

Default Value

authorizer: AllowAllAuthorizer

References

Additional Information

The authorizer must be configured to AllowAllAuthorizer if AllowAllAuthenticator is the configured authenticator.

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

---name: cis-cassandra311-2-2description: Ensure that authorization is enabled for Cassandra databases---# 2.2 Ensure that authorization is enabled for Cassandra databases## Profile Applicability- Level 1 - Cassandra on Linux- Level 2 - Cassandra on Linux## DescriptionAuthorization is pluggable in Cassandra and is configured using the authorizer setting in cassandra.yaml. Cassandra ships with two options included in the default distribution, AllowAllAuthenticator and CassandraAuthorizer. The default, AllowAllAuthenticator performs no checking which grants all permissions to all roles. The second option, CassandraAuthorizer, implements full permissions management functionality and stores its data in Cassandra system tables.## RationaleAuthorizing roles is an important step towards ensuring only authorized access to the Cassandra database tables is permitted. It also provides the requisite means of implementing least privilege best practices. The authorization mechanism should be implemented before anyone accesses the Cassandra database.## AuditRun the following command to verify whether authorization is enabled (authorization values set to CassandraAuthorizer) 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.```bashcat cassandra.yaml | grep -in "authorizer:"```If authorizer is set to AllowAllAuthorizer, then this is a finding.## RemediationTo enable the authorization mechanism:1. Stop the Cassandra database.2. Modify cassandra.yaml file to modify/add entry for authorization: set it to CassandraAuthorizer3. Start the Cassandra database.## Default Value```authorizer: AllowAllAuthorizer```## References1. http://cassandra.apache.org/doc/latest/getting_started/configuring.html2. http://cassandra.apache.org/doc/latest/operating/security.html## Additional InformationThe authorizer must be configured to AllowAllAuthorizer if AllowAllAuthenticator is the configured authenticator.## 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

Frequently asked questions

Cis Cassandra311 2.2