mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-30 14:57:36 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
41 lines
2.0 KiB
Plaintext
41 lines
2.0 KiB
Plaintext
---
|
|
title: "Audit Logs"
|
|
sidebarTitle: "Audit Logs"
|
|
description: "Understand how KMS logs activity and supports external audit streaming."
|
|
---
|
|
|
|
KMS records a detailed audit trail of actions across the platform — providing deep visibility into access, changes, and usage for security and compliance purposes.
|
|
|
|
Every interaction with KMS resources generates an audit event. These events are immutable and include metadata such as the actor, event type, affected resources, timestamp, IP address, and client source.
|
|
|
|
Audit logs enable teams to:
|
|
|
|
- Monitor access and changes to secrets, certificates, and infrastructure.
|
|
- Investigate incidents with full context around who did what, when, and how.
|
|
- Meet compliance and governance requirements with structured activity records.
|
|
|
|
To learn more, refer to the [audit logs documentation](/documentation/platform/audit-logs).
|
|
|
|
## Log Coverage
|
|
|
|
KMS tracks dozens of event types across the platform — including secret access, permission changes, certificate issuance, SSH session activity, and identity management.
|
|
|
|
Each audit entry includes structured fields that make it easy to search, filter, and correlate across systems. For example:
|
|
|
|
- Event Type: Action that occurred (e.g., `create-secret`, `issue-ssh-cert`).
|
|
- Actor: Who performed the action (user or machine identity).
|
|
- Resource: What was affected (e.g., project, secret, certificate).
|
|
- Context: IP address, user agent, permissions, and more.
|
|
|
|
## External Log Streaming
|
|
|
|
For centralized monitoring and long-term retention, KMS supports [audit log streaming](/documentation/platform/audit-log-streams/audit-log-streams) to external systems.
|
|
|
|
You can forward logs to SIEM platforms, storage buckets, or observability stacks using JSON-based collectors. KMS integrates well with tools like [Fluent Bit](/documentation/platform/audit-log-streams/audit-log-streams-with-fluentbit#deploy-fluent-bit), enabling teams to route logs to destinations such as:
|
|
|
|
- AWS S3
|
|
- Elasticsearch
|
|
- Splunk
|
|
- Datadog
|
|
- Cloud-native log pipelines
|