Granting Users Access to Packetbeat Indices

edit

To enable users to access the indices a Packetbeat creates, grant them read and view_index_metadata privileges on the Packetbeat indices:

  1. Create a role that has the read and view_index_metadata privileges for the Packetbeat indices. You can create roles from the Management > Roles UI in Kibana or through the role API. For example, the following request creates a packetbeat_reader role:

    POST _xpack/security/role/packetbeat_reader
    {
      "indices": [
        {
          "names": [ "packetbeat-*" ], 
          "privileges": ["read","view_index_metadata"]
        }
      ]
    }

    If you use a custom Packetbeat index pattern, specify that pattern instead of the default packetbeat-* pattern.

  2. Assign your users the reader role so they can access the Packetbeat indices:

    1. If you’re using the native realm, you can assign roles with the Management > Users UI in Kibana or through the user API. For example, the following request grants packetbeat_user the packetbeat_reader role:

      POST /_xpack/security/user/packetbeat_user
      {
        "password" : "x-pack-test-password",
        "roles" : [ "packetbeat_reader"],
        "full_name" : "Packetbeat User"
      }
    2. If you’re using the LDAP, Active Directory, or PKI realms, you assign the roles in the role_mapping.yml configuration file. For example, the following snippet grants Packetbeat User the packetbeat_reader role:

      packetbeat_reader:
        - "cn=Packetbeat User,dc=example,dc=com"

      For more information, see Using Role Mapping Files.