OpenParable
Skip to content
← Back to skills

Cis Cassandra5 3.1

DevOps & Security
cis-cassandra5-3.1

Cis Cassandra5 3.1 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure the cassandra and superuser roles are separate

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Server_Software/Apache_Cassandra/CIS_Apache_Cassandra_5.0_Benchmark_v1.1.0/cis-cassandra5-3.1/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-cassandra5-3-1, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Ensure the cassandra and superuser roles are separate (Automated)

Profile Applicability

  • Level 1 - Cassandra
  • Level 1 - Cassandra on Linux

Description

The default installation of Cassandra includes a superuser role named cassandra. This necessitates the creation of a separate role to be the superuser role.

Rationale

Superuser permissions allow for the creation, deletion, and permission management of other users. Considering the cassandra role is well known it should not be a superuser or one which is used for any administrative tasks.

Impact

If a separate superuser account is not created and tested for correct functionality prior to removing the superuser role from the cassandra account you will no longer be able to perform certain actions, including:

  • Create a role with super user status.
  • Perform DROP or CREATE USER queries.

Audit Procedure

To verify the configuration, run the following query:

select role from system_auth.roles where is_superuser= True;

If you get an error 2200 [ INVALID QUERY] due to where clause, add "ALLOW FILTERING to end of query so:

select role from system_auth.roles where is_superuser= True ALLOW FILTERING;

Looking at the role, verify any show up with is_superuser = True and make sure it is not cassandra or any unapproved role. If any are found then, this is a finding.

Remediation

To remediate a misconfiguration, perform the following steps:

  1. Execute the following command:
create role '<NEW_ROLE_HERE>' with password='<NEW_PASSWORD_HERE>' and login=TRUE and superuser=TRUE ;

grant all permissions on all keyspaces to <NEW_ROLE_HERE>;

Note: Replace <NEW_ROLE_HERE> with the desired role and <NEW_PASSWORD_HERE> with a password.

  1. Verify the new role is working.
  2. Remove the superuser role from the cassandra account by executing the following command:
UPDATE system_auth.roles SET is_superuser=null WHERE role='cassandra';

Default Value

The default cassandra role has superuser privileges.

References

None

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v85.4 Restrict Administrator Privileges to Dedicated Administrator AccountsRestrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user's primary, non-privileged account.●●●
v74.3 Ensure the Use of Dedicated Administrative AccountsEnsure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities.●●●