Update Wiz mappings and ingest pipeline - #11348
Merged
Merged
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
kcreddy
reviewed
Oct 7, 2024
Contributor
🚀 Benchmarks reportTo see the full report comment with |
kcreddy
approved these changes
Oct 8, 2024
💚 Build Succeeded
History
|
|
Contributor
|
Package wiz - 1.9.0-preview04 containing this change is available at https://epr.elastic.co/search?package=wiz |
Contributor
|
Package wiz - 2.0.0 containing this change is available at https://epr.elastic.co/search?package=wiz |
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
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.


Summary
As part of the CDR epic, the cloud security team introduced a default index pattern for the latest findings indices (
security_solution-*), which include misconfiguration and vulnerability data. Currently, this new index pattern does not automatically inherit the ECS mappings component (a fix for this is being tracked in https://github.com/elastic/security-team/issues/10720).In this PR, I manually added the relevant ECS fields for the vulnerability latest index.
In addition I updated the ingest pipeline to populate
package.namefield.