This is an earlier version of the OpenSearch documentation. For the latest version, see the current documentation. For information about OpenSearch version maintenance, see Release Schedule and Maintenance Policy.
Audit logs let you track access to your OpenSearch cluster and are useful for compliance purposes or in the aftermath of a security breach. You can configure the categories to be logged, the detail level of the logged messages, and where to store the logs.
To enable audit logging:
Add the following line to
opensearch.ymlon each node:
This setting stores audit logs on the current cluster. For other storage options, see Audit Log Storage Types.
Restart each node.
After this initial setup, you can use OpenSearch Dashboards to manage your audit log categories and other settings. In OpenSearch Dashboards, choose Security, Audit logs.
Table of contents
- Tracked events
- Exclude categories
- Disable REST or the transport layer
- Disable request body logging
- Log index names
- Configure bulk request handling
- Exclude requests
- Exclude users
- Configure the audit log index name
- (Advanced) Tune the thread pool
Audit logging records events in two ways: HTTP requests (REST) and the transport layer.
|Event||Logged on REST||Logged on transport||Description|
| ||Yes||Yes||The credentials of a request could not be validated, most likely because the user does not exist or the password is incorrect.|
| ||Yes||Yes||A user successfully authenticated.|
| ||No||Yes||The user does not have the required permissions to execute the request.|
| ||No||Yes||A user made a successful request to OpenSearch.|
| ||Yes||Yes||An attempt was made to access OpenSearch without a valid SSL/TLS certificate.|
| ||No||Yes||An attempt was made to modify the security plugin internal user and privileges index without the required permissions or TLS admin certificate.|
| ||Yes||Yes||An attempt was made to spoof a request to OpenSearch with the security plugin internal headers.|
These default log settings work well for most use cases, but you can change settings to save storage space or adapt the information to your exact needs.
To exclude categories, set:
plugins.security.audit.config.disabled_rest_categories: <disabled categories> plugins.security.audit.config.disabled_transport_categories: <disabled categories>
plugins.security.audit.config.disabled_rest_categories: AUTHENTICATED, opensearch_SECURITY_INDEX_ATTEMPT plugins.security.audit.config.disabled_transport_categories: GRANTED_PRIVILEGES
If you want to log events in all categories, use
plugins.security.audit.config.disabled_rest_categories: NONE plugins.security.audit.config.disabled_transport_categories: NONE
Disable REST or the transport layer
By default, the security plugin logs events on both REST and the transport layer. You can disable either type:
plugins.security.audit.enable_rest: false plugins.security.audit.enable_transport: false
Disable request body logging
By default, the security plugin includes the body of the request (if available) for both REST and the transport layer. If you do not want or need the request body, you can disable it:
Log index names
By default, the security plugin logs all indices affected by a request. Because index names can be aliases and contain wildcards/date patterns, the security plugin logs the index name that the user submitted and the actual index name to which it resolves.
For example, if you use an alias or a wildcard, the audit event might look like:
audit_trace_indices: [ "human*" ], audit_trace_resolved_indices: [ "humanresources" ]
You can disable this feature by setting:
Disabling this feature only takes effect if
plugins.security.audit.log_request_body is also set to
Configure bulk request handling
Bulk requests can contain many indexing operations. By default, the security plugin only logs the single bulk request, not each individual operation.
The security plugin can be configured to log each indexing operation as a separate event:
This change can create a massive number of events in the audit logs, so we don’t recommend enabling this setting if you make heavy use of the
You can exclude certain requests from being logged completely, by either configuring actions (for transport requests) and/or HTTP request paths (REST):
plugins.security.audit.ignore_requests: ["indices:data/read/*", "SearchRequest"]
By default, the security plugin logs events from all users, but excludes the internal OpenSearch Dashboards server user
kibanaserver. You can exclude other users:
plugins.security.audit.ignore_users: - kibanaserver - admin
If requests from all users should be logged, use
Configure the audit log index name
By default, the security plugin stores audit events in a daily rolling index named
auditlog-YYYY.MM.dd. You can configure the name of the index in
Use a date pattern in the index name to configure daily, weekly, or monthly rolling indices:
For a reference on the date pattern format, see the Joda DateTimeFormat documentation.
(Advanced) Tune the thread pool
The Search plugin logs events asynchronously, which keeps performance impact on your cluster minimal. The plugin uses a fixed thread pool to log events. You can define the number of threads in the pool in
The default setting is
10. Setting this value to
0 disables the thread pool, which means the plugin logs events synchronously. To set the maximum queue length per thread: