Anomaly detection security

All anomaly detection indices are protected as system indices. Only a super admin user or an admin user with a TLS certificate can access system indices. For more information, see System indices.

Security for anomaly detection works the same as .

As an admin user, you can use the security plugin to assign specific permissions to users based on which APIs they need access to. For a list of supported APIs, see Anomaly detection API.

If these roles don’t meet your needs, mix and match individual anomaly detection to suit your use case. Each action corresponds to an operation in the REST API. For example, the cluster:admin/opensearch/ad/detector/delete permission lets you delete detectors.

(Advanced) Limit access by backend role

Use backend roles to configure fine-grained access to individual detectors based on roles. For example, users of different departments in an organization can view detectors owned by their own department.

First, make sure your users have the appropriate . Backend roles usually come from an LDAP server or , but if you use the internal user database, you can use the REST API to add them manually.

Now when users view anomaly detection resources in OpenSearch Dashboards (or make REST API calls), they only see detectors created by users who share at least one backend role. For example, consider two users: and bob.

alice has an analyst backend role:

has a human-resources backend role:

Because they have different backend roles, and bob cannot view each other’s detectors or their results.