IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Configure Auditbeat to use X-Pack security Grant users access to Auditbeat indices »

› › ›

Configure authentication credentials

edit

Configure authentication credentials

edit

When sending data to a secured cluster through the elasticsearch output, Auditbeat must either provide basic authentication credentials or present a client certificate.

To configure authentication credentials for Auditbeat:

Create a writer role that has the following privileges:
- Cluster: manage_index_templates and monitor
- Index: write and create_index on the Auditbeat indices
You can create roles from the Management / Roles UI in Kibana or through the role API. For example, the following request creates a role named auditbeat_writer:
```
POST _xpack/security/role/auditbeat_writer
{
  "cluster": ["manage_index_templates","monitor"],
  "indices": [
    {
      "names": [ "auditbeat-*" ], 
      "privileges": ["write","create_index"]
    }
  ]
}
```
If you use a custom Auditbeat index pattern, specify that pattern instead of the default auditbeat-* pattern.
Assign the writer role to the user that Auditbeat will use to connect to Elasticsearch. If you plan to load the pre-built Kibana dashboards, also assign the kibana_user role. If you plan to load machine learning jobs, assign the machine_learning_admin role.
1. To authenticate as a native user, create a user for Auditbeat to use internally and assign it the writer role, plus any other roles that are needed.
  
  You can create users from the Management / Users UI in Kibana or through the user API. For example, following request creates a user named auditbeat_internal that has the auditbeat_writer and kibana_user roles:
```
POST /_xpack/security/user/auditbeat_internal
{
  "password" : "YOUR_PASSWORD",
  "roles" : [ "auditbeat_writer","kibana_user"],
  "full_name" : "Internal Auditbeat User"
}
```
2. To use PKI authentication, assign the writer role, plus any other roles that are needed, in the role_mapping.yml configuration file. Specify the user by the distinguished name that appears in its certificate:
```
auditbeat_writer:
  - "cn=Internal Auditbeat User,ou=example,o=com"
kibana_user:
  - "cn=Internal Auditbeat User,ou=example,o=com"
```
  For more information, see Using Role Mapping Files.

In the Auditbeat configuration file, specify authentication credentials for the elasticsearch output:

To use basic authentication, configure the username and password settings. For example, the following Auditbeat output configuration uses the native auditbeat_internal user to connect to Elasticsearch:
```
output.elasticsearch:
  hosts: ["localhost:9200"]
  username: "auditbeat_internal" 
  password: "YOUR_PASSWORD" 
```
You created this user earlier.

The example shows a hard-coded password, but you should store sensitive values in the secrets keystore.

To use PKI authentication, configure the certificate and key settings:

output.elasticsearch:
  hosts: ["localhost:9200"]
  ssl.certificate: "/etc/pki/client/cert.pem" 
  ssl.key: "/etc/pki/client/cert.key"

The distinguished name (DN) in the certificate must be mapped to the auditbeat_writer and kibana_user roles in the role_mapping.yml configuration file on each node in the Elasticsearch cluster.

« Configure Auditbeat to use X-Pack security Grant users access to Auditbeat indices »

	You created this user earlier.
	The example shows a hard-coded password, but you should store sensitive values in the secrets keystore.