Cassandra

Connect your Apache Cassandra cluster so Myrmex can audit its hardening and compliance, check its operational health, explore its keyspaces, and — with approval — run CQL for you. Myrmex reaches the cluster over the native CQL protocol through a Collector on your network. Operations run live and on demand through the Integration Specialist agent — Myrmex reads only what you ask for and keeps none of your data on the Myrmex side.

What Myrmex Can Do

Compliance audit

Run a Security Posture audit and map findings to CIS, ISO 27001, NIST CSF, and BACEN frameworks.

Health checks

Review node status, keyspace and table statistics, and latency signals.

Explore tables

List keyspaces and tables so you can see what the cluster holds.

Describe structure

Inspect a table’s columns, keys, and options.

Sensitive-data scan

Scan tables and columns for personal or sensitive data that needs protection.

Run CQL

Execute read CQL any time; write CQL (DDL/DML) requires your confirmation.

Before You Start

A Collector on a network that can reach a Cassandra contact point on its native transport port (default 9042). See Collector mode.
Authentication enabled on the cluster (PasswordAuthenticator) and a dedicated role for Myrmex (create it in Step 1).

Step 1 — Create the Credential in Cassandra

Create a dedicated, least-privilege role for auditing with read access to the system keyspaces the audit inspects.

-- Requires PasswordAuthenticator enabled in cassandra.yaml
CREATE ROLE myrmex_audit WITH LOGIN = true AND PASSWORD = 'a-strong-password';

-- Read access to the system keyspaces the audit relies on
GRANT SELECT ON KEYSPACE system TO myrmex_audit;
GRANT SELECT ON KEYSPACE system_schema TO myrmex_audit;
GRANT SELECT ON KEYSPACE system_auth TO myrmex_audit;

-- Add any application keyspace you want inspected:
-- GRANT SELECT ON KEYSPACE your_keyspace TO myrmex_audit;

Keep the role read-only for auditing. Grant MODIFY on a keyspace only if you want the agents to run write CQL through Run CQL.

Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Cassandra, then fill in:

Field	Description
Name	A unique name for this cluster.
Description	Optional note to identify the instance.
Host	Cassandra contact point hostname or IP.
Port	Cassandra native transport port (default `9042`).
Username	Cassandra username.
Password	Cassandra password (stored encrypted).
Keyspace	Keyspace to inspect (optional).
Collectors	The Collector(s) that can reach this cluster.

Connect

Click Connect to validate the login. The cluster then appears under Environment → Integrations alongside your other integrations, and you can start asking the AI about it in the Workspace.

Notes

Read-only by default. Auditing, health, exploration, and sensitive-data scans only need the SELECT grants above. Grant MODIFY only if you want confirmation-gated Run CQL writes.
Nothing is stored. Every operation runs in real time through the Collector; results return to your Workspace and no cluster data is retained on the Myrmex side.
Encryption in transit follows your cluster’s configuration; the posture audit flags an unencrypted listener.

Get Started

The AI Agents

The AI Workspace

Detection & Response

Security Posture & Compliance

Endpoints & the Security Agent

Integrations

Automation

Change Management

Management

Policies

What Myrmex Can Do

Compliance audit

Health checks

Explore tables

Describe structure

Sensitive-data scan

Run CQL

Before You Start

Step 1 — Create the Credential in Cassandra

Step 2 — Add the Integration in Myrmex

Connect

Notes

​What Myrmex Can Do

Compliance audit

Health checks

Explore tables

Describe structure

Sensitive-data scan

Run CQL

​Before You Start

​Step 1 — Create the Credential in Cassandra

​Step 2 — Add the Integration in Myrmex

​Connect

​Notes

What Myrmex Can Do

Before You Start

Step 1 — Create the Credential in Cassandra

Step 2 — Add the Integration in Myrmex

Connect

Notes