You configure security auditing settings in the
elasticsearch.yml configuration file
on each node in the cluster. For more information, see Enabling audit logging.
The events and some other information about what gets logged can be controlled by using the following settings:
Specifies whether to include the request body from REST requests on certain event types such as
authentication_failed. The default value is
No filtering is performed when auditing, so sensitive data may be audited in plain text when including the request body in audit events.
Specifies whether to include the node name as a field in
each audit event. The default value is
Specifies whether to include the node id as a field in each audit event.
This is available for the new format only. That is to say, this information
does not exist in the
<clustername>_access.logfile. Unlike node name, whose value might change if the administrator changes the setting in the config file, the node id will persist across cluster restarts and the administrator cannot change it. The default value is
These settings affect the ignore policies that enable fine-grained control over which audit events are printed to the log file. All of the settings with the same policy name combine to form a single policy. If an event matches all of the conditions for a specific policy, it is ignored and not printed.
- A list of role names or wildcards. The specified policy will not print audit events for users that have these roles. If the user has several roles, some of which are not covered by the policy, the policy will not cover this event.
- A list of index names or wildcards. The specified policy will not print audit events when all the indices in the event match these values. If the event concerns several indices, some of which are not covered by the policy, the policy will not cover this event.