Audit trail
KCM records who did what, when, from where and with which result: sign ins, access changes, cluster, topic, connector and schema operations, messages produced, test scenario runs and access as code applies.
What is recorded
Each event holds a time, an action, a status (SUCCESS or FAILURE), the actor and its
type (USER, SERVICE_ACCOUNT, SYSTEM or ANONYMOUS), the resource
type and id, the cluster and environment, the duration, the client address and user agent, details, and the error
message of a failure. Examples:
| Area | Actions |
|---|---|
| Sign in | Successful and failed sign ins, locks, second factor steps
(LOGIN, LOGIN_PASSWORD) |
| Two-factor | MFA_ENABLE, MFA_DISABLE, MFA_RESET,
MFA_RECOVERY_CODES, MFA_RECOVERY_CODE_USED |
| Users and service accounts | Creation, update, enable, disable, password change, sessions ended, role from SSO, tokens created and revoked |
| Access | Roles, grants, role groups and their members, memberships from SSO
(ROLE_GROUP_SSO_SYNC), access as code (IAC_APPLY, IAC_UNMANAGE) |
| Configuration | Settings, SSO providers, trusted certificates, license |
| Kafka | Cluster, topic, consumer group, ACL and Kafka user operations, connectors, schemas, Confluent Cloud operations |
| Data | Messages produced from KCM and test scenario runs, without the message content |
Actions started outside a web request (live message tail, asynchronous and scheduled test scenarios, what-if
simulations, leader rebalances) are attributed to the user who started them, or to a system actor for scheduled
runs, together with the user who set the schedule. Detail values that look like secrets (tokens, passwords, keys)
are masked as ***.
Browse the audit
- Global audit: every environment, plus the events that belong to none (sign in, users,
service accounts, grants, role groups, settings, SSO). For global
ADMIN,AUDITORandSECURITY_ADMIN. - Audit of an environment: the events of one KCM group, for anyone with a role on it.
Filter by actor, action, resource type, resource id, status, free text and time range, and sort by any column.
CSV export
Enterprise Export the audit with the current filters, from the global audit or from
an environment. Global ADMIN, AUDITOR and SECURITY_ADMIN can export the
global audit.
- Up to 100,000 rows, taken as a snapshot when the export starts. The response headers
X-Kcm-Export-TotalandX-Kcm-Export-Truncatedtell whether the export was cut. - File name
kcm-audit-global-yyyyMMdd-HHmmss.csvorkcm-audit-group-{id}-yyyyMMdd-HHmmss.csv. - Standard CSV (RFC 4180). Cells that start with a formula character are prefixed with
'so that a spreadsheet never runs them. - Columns:
id,timestamp,actor,actor_type,action,status,resource_type,resource_id,cluster_id,kcm_group_id,duration_ms,ip,user_agent,meta,error_message. - The export itself is recorded as
AUDIT_EXPORT.
# Global audit of the last day, failures only
curl -s -H "Authorization: Bearer $KCM_TOKEN" -o audit.csv \
"https://kcm.example.com/api/v1/audit/export?status=FAILURE&from=2026-11-18T00:00:00Z"
# Audit of one environment
curl -s -H "Authorization: Bearer $KCM_TOKEN" -o audit-group.csv \
"https://kcm.example.com/api/v1/groups/{groupId}/audit/export?action=DELETE_KAFKA_TOPIC"
Filters: actor (contains), action (exact), resourceType,
resourceId (contains), status, q (free text), from and
to (ISO date and time), sort (for example ts,desc).
Event stream for a SIEM
Enterprise With KCM_AUDIT_LOG_ENABLED=true, every audit event is
also written as one JSON line on the standard output of the API, once the change is committed.
Collect it with your log agent (Fluent Bit, Vector, the agent of your SIEM...) and route it to your SIEM.
- The lines carry the logger name
kcm.audit, and the line is the JSON alone, with no prefix, so it is easy to filter from the other API logs. - A line never holds a secret nor the content of a message.
- Without an Enterprise license, the stream stays off and a warning at startup says why. Installing an Enterprise license turns it on without restart.
{"schemaVersion":1,"id":48213,"timestamp":"2026-11-19T10:42:07.512Z","action":"IAC_APPLY",
"status":"SUCCESS","actor":{"user":"platform-ci","type":"SERVICE_ACCOUNT"},"resourceType":"IAC",
"resourceId":"iac:git:platform-access","clusterId":null,"kcmGroupId":null,"durationMs":0,
"ip":"10.0.4.12","userAgent":"curl/8.5.0","traceId":"...","meta":{"prune":true,"changes":{"CREATE":2}},
"errorMessage":null}
Fields: schemaVersion, id, timestamp, action,
status, actor (user, type), resourceType,
resourceId, clusterId, kcmGroupId, durationMs,
ip, userAgent, traceId, meta, errorMessage.
Fields may be added in later versions, never renamed or removed. (The example is shown on several lines for
reading; each event is one line.)
Retention
KCM 1.5.0 keeps audit events in its database and has no automatic purge. For long-term retention and alerting, use the CSV export or the SIEM stream.