Skip to content

Add Wiz and AWS SecurityHub new full posture data streams to kibana_system role permissions #124074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

maxcold
Copy link
Contributor

@maxcold maxcold commented Mar 5, 2025

Adding logs-wiz.cloud_configuration_finding_full_posture-* and logs-aws.securityhub_findings_full_posture-* data streams to the kibana_system privileges. This is required for the latest transforms to work.

Related to:

@maxcold maxcold added >non-issue :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC auto-backport Automatically create backport pull requests when merged Team:Cloud Security Meta label for Cloud Security team v9.0.0 v8.18.0 v8.16.6 v8.17.4 labels Mar 5, 2025
@maxcold maxcold requested a review from a team as a code owner March 5, 2025 09:08
@elasticsearchmachine elasticsearchmachine added v9.1.0 external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Security Meta label for security team labels Mar 5, 2025
@elasticsearchmachine
Copy link
Collaborator

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

Copy link
Contributor

@slobodanadamovic slobodanadamovic left a comment

Choose a reason for hiding this comment

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

LGTM

@slobodanadamovic
Copy link
Contributor

@maxcold I believe the version labels should be :

8.16.6, 8.17.4, 8.18.1, 8.19.0, 9.0.1, 9.1.0

@maxcold
Copy link
Contributor Author

maxcold commented Mar 5, 2025

@slobodanadamovic it's past FF for 8.18.0 and 9.0.0 but if possible I'd like to have it in these versions. Plus is it even possible to get into 8.18.1 and 9.0.1 while 8.18 and 9.0 branches are pointing to 8.18.0 and 9.0? I'm not very familiar with how Elasticsearch repo backporting logic works, but in Kibana repo it's not possible

@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
9.0
8.18
8.16
8.17

maxcold added a commit to maxcold/elasticsearch that referenced this pull request Mar 5, 2025
maxcold added a commit to maxcold/elasticsearch that referenced this pull request Mar 5, 2025
@maxcold maxcold added the v8.19.0 label Mar 5, 2025
elasticsearchmachine pushed a commit that referenced this pull request Mar 5, 2025
elasticsearchmachine pushed a commit that referenced this pull request Mar 5, 2025
@maxcold
Copy link
Contributor Author

maxcold commented Mar 5, 2025

💚 All backports created successfully

Status Branch Result
8.x

Questions ?

Please refer to the Backport tool documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged external-contributor Pull request authored by a developer outside the Elasticsearch team >non-issue :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC Team:Cloud Security Meta label for Cloud Security team Team:Security Meta label for security team v8.16.6 v8.17.4 v8.18.0 v8.19.0 v9.0.0 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants