Skip to content

[ResponseOps] Add access to .alerting* for kibana_system role#143046

Merged
adcoelho merged 1 commit intoelastic:mainfrom
adcoelho:alerting-v2-update-kibana-role
Feb 26, 2026
Merged

[ResponseOps] Add access to .alerting* for kibana_system role#143046
adcoelho merged 1 commit intoelastic:mainfrom
adcoelho:alerting-v2-update-kibana-role

Conversation

@adcoelho
Copy link
Copy Markdown
Contributor

Closes https://github.com/elastic/rna-program/issues/146

Summary

For the alert engine refactor work(alerting v2), we need to allow the Kibana system user to access .alerting* indexes.

@adcoelho adcoelho self-assigned this Feb 25, 2026
@adcoelho adcoelho requested review from a team as code owners February 25, 2026 11:50
@adcoelho adcoelho requested a review from kc13greiner February 25, 2026 11:50
@adcoelho adcoelho added v9.4.0 Team:Security Meta label for security team labels Feb 25, 2026
@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label and removed Team:Security Meta label for security team labels Feb 25, 2026
@adcoelho adcoelho added the :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC label Feb 25, 2026
@elasticsearchmachine elasticsearchmachine added the Team:Security Meta label for security team label Feb 25, 2026
@elasticsearchmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-security (Team:Security)

Copy link
Copy Markdown
Contributor

@kc13greiner kc13greiner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heya @adcoelho !

Can you provide some context about why the kibana_system user needs all privilege on this system index?

@adcoelho
Copy link
Copy Markdown
Contributor Author

Hi @kc13greiner, thanks for reviewing.

We are working on a new direction for "rules and alerts" that rewrites everything from scratch in a new architecture. Until now, the indexes we created were all named .alerts-* so we could rely on the existing permissions for ReservedRolesStore.ALERTS_INDEX_ALIAS. This is, however, the index name pattern for alerting v1, and we want to enforce a clear distinction for users when querying these indexes for alerts. These indexes are managed by the Kibana system user on startup, so for our changes to work, it will need read, write, delete, and manage permissions.

Copy link
Copy Markdown
Member

@cnasikas cnasikas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From a ResponseOps standpoint (naming of indices) LGTM!

@kc13greiner
Copy link
Copy Markdown
Contributor

Hi @kc13greiner, thanks for reviewing.

We are working on a new direction for "rules and alerts" that rewrites everything from scratch in a new architecture. Until now, the indexes we created were all named .alerts-* so we could rely on the existing permissions for ReservedRolesStore.ALERTS_INDEX_ALIAS. This is, however, the index name pattern for alerting v1, and we want to enforce a clear distinction for users when querying these indexes for alerts. These indexes are managed by the Kibana system user on startup, so for our changes to work, it will need read, write, delete, and manage permissions.

Thanks for the info!

You mention it will need read, write, delete, and manage permissions: is there a subset of specific privileges you could add rather than "all"?

@adcoelho
Copy link
Copy Markdown
Contributor Author

You mention it will need read, write, delete, and manage permissions: is there a subset of specific privileges you could add rather than "all"?

@kc13greiner, atm not, we plan on using all of these as we did for the old ALERTS_INDEX_ALIAS.

@kc13greiner
Copy link
Copy Markdown
Contributor

You mention it will need read, write, delete, and manage permissions: is there a subset of specific privileges you could add rather than "all"?

@kc13greiner, atm not, we plan on using all of these as we did for the old ALERTS_INDEX_ALIAS.

++ ok! Thanks for the discussion! Since it is a system index and all the privileges are required, we can accept this 👍

@adcoelho
Copy link
Copy Markdown
Contributor Author

@kc13greiner and thanks for the approval 🙌 I fully understand where you are coming from wrt to granting the least amount of necessary permissions. It is just that in this case, we have needed the same in the past, I just need to update the index names 😁

@adcoelho adcoelho merged commit e5d521d into elastic:main Feb 26, 2026
35 checks passed
adcoelho added a commit to elastic/kibana that referenced this pull request Mar 4, 2026
…#254901)

Closes elastic/rna-program#144

## Summary

**This PR depends on:
elastic/elasticsearch#143046

Renaming the alerting indexes:

```
.alerts-events -> .alerting-events
.alerts-actions -> .alerting-actions
```

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>non-issue :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC Team:Security Meta label for security team v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants