How to Configure ScyllaDB Audit Log

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up the scylladb audit log by turning on auditing in each node file. You then pick a storage backend and choose which database events to record. Most data teams start by turning on broad logging across every cluster node. This approach captures login attempts, schema changes, and data reads. Still, teams often share wide database roles across many engineers and apps. When everyone uses the same role, the native log cannot show who ran a query. How the native scylladb audit log works Sc

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up the scylladb audit log by turning on auditing in each node file. You then pick a storage backend and choose which database events to record. Most data teams start by turning on broad logging across every cluster node. This approach captures login attempts, schema changes, and data reads. Still, teams often share wide database roles across many engineers and apps. When everyone uses the same role, the native log cannot show who ran a query.

How the native scylladb audit log works

ScyllaDB processes audit events right inside each database node. Before you turn this feature on, you must update the main node settings. You define where the database should send the log entries. Admins usually pick between two storage targets. You can send events to local system logs on the server disk. You can also write events straight into an internal database table.

Next, you choose the exact categories of database activity to track. You can track login checks, data queries, schema updates, and permission changes. You can also filter the scylladb audit log by specific keyspaces or tables. This filtering keeps high-traffic tables from filling up your storage disk. Once you save the settings and restart the service, the node starts recording.

Each log entry holds basic facts about the database request. It records the timestamp, the source IP, the database role, and the query text. If you use the internal table target, you query logs with standard database reads. If you use the system log target, a log shipper moves the files out. Your security team can then read those files in a central log tool.

What native logging solves and where it falls short

Native database auditing solves the basic need for cluster activity records. It proves that the database tracks schema drops, role changes, and failed logins. It also helps admins spot broken apps that send bad queries. For simple setups with few users, this native feature works well.

Still, native logging leaves a large gap in daily operations. The database only knows the local database role used to log in. In most companies, engineers and scripts share a small set of admin roles. When someone runs a bad query, the log only shows the shared role name. You cannot tell which person on the team actually ran the command.

Audit Log Integrity + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Native logs also happen after the query starts or finishes. They record what happened, but they cannot stop a risky command in flight. They also do not mask sensitive data returned in query results. If an engineer queries a table with card numbers or emails, raw values return. The native audit log only notes that the read query happened.

Managing node load and log storage

Turning on full query logging adds extra work to every database node. When you log every read and write, the node does twice the work. This extra load can slow down fast workloads when traffic spikes. Storing audit records inside a database table also eats up cluster disk space. Teams must clean up old audit rows often to stop disks from filling up.

Sending logs to local files avoids extra database table writes. Yet you still need agents on every host to ship those files away. If a host disk fills up, the node can stall or drop log lines. Good audit setups separate human query tracking from heavy app traffic.

Add runtime guardrails and masking beside your databases and APIs

Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits inline in the protocol beside the service as an open-source proxy, a sidecar for your database or API. On every production query an agent or human runs, hoop.dev decides whether to pass, mask, block, or escalate it for review.

Before a query runs, hoop.dev guardrails check the statement against your rules, an AI Analyzer you configure can score intent or hold risky calls for human approval, and hoop.dev data masking rewrites sensitive fields in responses in memory. Explore the MIT-licensed project on GitHub.

Frequently asked questions

Where does ScyllaDB store audit log records?

ScyllaDB can write audit records to local system log files on each node. It can also write them into an internal audit table inside the cluster.

Does turning on the audit log slow down the database?

Logging admin changes and logins adds very little load to the cluster. Logging every single read and write query will add disk and CPU work.

Why do shared database roles hurt audit log quality?

The native log only records the database role name, not the human user. When ten engineers share one role, you cannot see who ran a query.

The query runs. The emails stay hidden.