IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
Elastic Docs ›Auditbeat Reference [7.6] ›Secure Auditbeat
« Secure communication with Logstash Grant users access to secured resources »

Configure Auditbeat to use security featuresedit

If you want Auditbeat to connect to a cluster that has security features enabled, there are extra configuration steps:

  1. Grant users access to secured resources.

    You can use role-based access control to grant Auditbeat users access to secured resources.

  2. Grant access using API keys.

    You can use API keys to grant access to Elasticsearch more securely.

  3. Configure authentication credentials.

    To interact with a secured cluster, Auditbeat must either provide basic authentication credentials or present a client certificate.

  4. Configure Auditbeat to use encrypted connections.

    If encryption is enabled on the cluster, you need to enable HTTPS in the Auditbeat configuration.

For more information about security features, see Secure a cluster.

« Secure communication with Logstash Grant users access to secured resources »