Stack security event audit logging
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is not available in Elastic Cloud Serverless. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Unavailable
Unavailable
Stack
Generally available
Audit logs are only available on certain subscription levels.
Audit logging is a powerful feature that helps you monitor and track security-related events within the Elastic Stack. By enabling audit logs, you can gain visibility into authentication attempts, authorization decisions, and other system activity.
Audit logging also provides forensic evidence in the event of an attack, and can be enabled independently for Elasticsearch and Kibana.
In FedRAMP Moderate environments, you can also audit organization-level actions such as deployment management, API key usage, and sign-in activity. Refer to Elastic Cloud audit trail.
Use the Kibana audit logs in conjunction with Elasticsearch audit logging to get a holistic view of all security related events. Kibana defers to the Elasticsearch security model for authentication, data index authorization, and features that are driven by cluster-wide privileges.
In this section, you'll learn how to:
Enable audit logging: Activate Elasticsearch or Kibana audit logs for all supported deployment types.
Configure audit logging: Filter and control what security events get logged in the audit log output.
Audit Elasticsearch HTTP request bodies: Include authenticated REST request bodies in audit events.
Correlate audit events: Explore audit logs and understand how events from the same request are correlated.
By following these guidelines, you can effectively audit system activity, enhance security monitoring, and meet compliance requirements.
For a complete description of audit event details and format, refer to: