[8.19] Add {m365_defender,microsoft_defender_endpoint}.vulnerability indices to kibana_system role permissions (#132445)#132629
Merged
elasticsearchmachine merged 2 commits intoelastic:8.19from Aug 11, 2025
Conversation
… to kibana_system role permissions (elastic#132445) Add logs-m365_defender.vulnerability-* and logs-microsoft_defender_endpoint.vulnerability-* data stream indices to the kibana_system's read privileges. This is required for the latest transform for 3rd party integrations CDR workflows (vulnerability findings) to work. Also add delete_index on logs-m365_defender.vulnerability-* and logs-microsoft_defender_endpoint.vulnerability-* to facilitate index removal through ILM policies. (cherry picked from commit 716bff8)
Contributor
Author
|
@elasticsearchmachine test this please |
Contributor
Author
|
@elasticsearchmachine test this please |
5 tasks
efd6
pushed a commit
to elastic/integrations
that referenced
this pull request
Oct 12, 2025
…plementation (#15603) Existing CEL program uses 3 API endpoints to fetch vulnerability data. Although we fetch more fields using this approach, it doesn't scale well and hence is unusable even for few hundred machines. This PR updates the vulnerability data stream with new SoftwareVulnerabilitiesExport API[1], which is recommended for larger workloads. While there are few data points missed in this new implementation[2], we maintain all the required fields for 3rd party vulnerability workflow[3]. Other changes: - Updates microsoft_defender_endpoint min stack version to "8.19.3" as the permissions for the transform were actually applied in "8.19.3" version, and not in "8.19.2"[4]. - Add dataset filter to all visualisations of vulnerability dashboards. [1]: https://learn.microsoft.com/en-us/defender-endpoint/api/get-assessment-software-vulnerabilities#2-export-software-vulnerabilities-assessment-via-files [2]: #15521 (comment) [3]: https://docs.elastic.dev/security-solution/cloud-security/cdr/3p-dev-guide [4]: elastic/elasticsearch#132629
Member
|
Looks like this one did not make it to 8.19.2 but 8.19.3 |
Contributor
Author
Yes, we recently noticed it and updated the integration's version constraint to |
agithomas
pushed a commit
to agithomas/integrations
that referenced
this pull request
Oct 30, 2025
…plementation (elastic#15603) Existing CEL program uses 3 API endpoints to fetch vulnerability data. Although we fetch more fields using this approach, it doesn't scale well and hence is unusable even for few hundred machines. This PR updates the vulnerability data stream with new SoftwareVulnerabilitiesExport API[1], which is recommended for larger workloads. While there are few data points missed in this new implementation[2], we maintain all the required fields for 3rd party vulnerability workflow[3]. Other changes: - Updates microsoft_defender_endpoint min stack version to "8.19.3" as the permissions for the transform were actually applied in "8.19.3" version, and not in "8.19.2"[4]. - Add dataset filter to all visualisations of vulnerability dashboards. [1]: https://learn.microsoft.com/en-us/defender-endpoint/api/get-assessment-software-vulnerabilities#2-export-software-vulnerabilities-assessment-via-files [2]: elastic#15521 (comment) [3]: https://docs.elastic.dev/security-solution/cloud-security/cdr/3p-dev-guide [4]: elastic/elasticsearch#132629
tehbooom
pushed a commit
to tehbooom/integrations
that referenced
this pull request
Nov 19, 2025
…plementation (elastic#15603) Existing CEL program uses 3 API endpoints to fetch vulnerability data. Although we fetch more fields using this approach, it doesn't scale well and hence is unusable even for few hundred machines. This PR updates the vulnerability data stream with new SoftwareVulnerabilitiesExport API[1], which is recommended for larger workloads. While there are few data points missed in this new implementation[2], we maintain all the required fields for 3rd party vulnerability workflow[3]. Other changes: - Updates microsoft_defender_endpoint min stack version to "8.19.3" as the permissions for the transform were actually applied in "8.19.3" version, and not in "8.19.2"[4]. - Add dataset filter to all visualisations of vulnerability dashboards. [1]: https://learn.microsoft.com/en-us/defender-endpoint/api/get-assessment-software-vulnerabilities#2-export-software-vulnerabilities-assessment-via-files [2]: elastic#15521 (comment) [3]: https://docs.elastic.dev/security-solution/cloud-security/cdr/3p-dev-guide [4]: elastic/elasticsearch#132629
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto8.19:Questions ?
Please refer to the Backport tool documentation