-
Notifications
You must be signed in to change notification settings - Fork 464
Set sensitive values as secret - Part 3 #9128
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
Set sensitive values as secret - Part 3 #9128
Conversation
🚀 Benchmarks reportTo see the full report comment with |
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍🏼
type: keyword | ||
type: long |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actor.Type
and Target.Type
are both mapped to same type. Maybe we could make it both integer
or long
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'll actually drop in a convert processor here. Dan mentioned this here and I think it's applicable in this case as well. In general, even though it is technically a number, what we really want is it indexed as is a keyword.
💚 Build Succeeded
History
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍🏼
Package o365 - 2.3.0 containing this change is available at https://epr.elastic.co/search?package=o365 |
Package okta - 2.8.0 containing this change is available at https://epr.elastic.co/search?package=okta |
Package panw_cortex_xdr - 1.25.0 containing this change is available at https://epr.elastic.co/search?package=panw_cortex_xdr |
Package ping_one - 1.14.0 containing this change is available at https://epr.elastic.co/search?package=ping_one |
Package prisma_cloud - 1.1.0 containing this change is available at https://epr.elastic.co/search?package=prisma_cloud |
Package proofpoint_tap - 1.17.0 containing this change is available at https://epr.elastic.co/search?package=proofpoint_tap |
Package qualys_vmdr - 1.1.0 containing this change is available at https://epr.elastic.co/search?package=qualys_vmdr |
Package rapid7_insightvm - 1.9.0 containing this change is available at https://epr.elastic.co/search?package=rapid7_insightvm |
Package sentinel_one - 1.20.0 containing this change is available at https://epr.elastic.co/search?package=sentinel_one |
Package sentinel_one_cloud_funnel - 0.11.0 containing this change is available at https://epr.elastic.co/search?package=sentinel_one_cloud_funnel |
Package slack - 1.18.0 containing this change is available at https://epr.elastic.co/search?package=slack |
Package snyk - 1.20.0 containing this change is available at https://epr.elastic.co/search?package=snyk |
Package sophos_central - 1.14.0 containing this change is available at https://epr.elastic.co/search?package=sophos_central |
Package symantec_edr_cloud - 1.1.0 containing this change is available at https://epr.elastic.co/search?package=symantec_edr_cloud |
Package tanium - 1.8.0 containing this change is available at https://epr.elastic.co/search?package=tanium |
Package tenable_io - 2.9.0 containing this change is available at https://epr.elastic.co/search?package=tenable_io |
Package tenable_sc - 1.21.0 containing this change is available at https://epr.elastic.co/search?package=tenable_sc |
- Set sensitive values as secret in integrations. - Updated package-spec to 3.0.2 in most packages to leverage secrets validation checks. - Certain packages required fixes to mappings (due to missing or incorrect mappings). - Certain packages were not able to go to package-spec 3.0.2 due to issues with dynamic mappings. These have been held back at 3.0.0.
- Set sensitive values as secret in integrations. - Updated package-spec to 3.0.2 in most packages to leverage secrets validation checks. - Certain packages required fixes to mappings (due to missing or incorrect mappings). - Certain packages were not able to go to package-spec 3.0.2 due to issues with dynamic mappings. These have been held back at 3.0.0.
- Set sensitive values as secret in integrations. - Updated package-spec to 3.0.2 in most packages to leverage secrets validation checks. - Certain packages required fixes to mappings (due to missing or incorrect mappings). - Certain packages were not able to go to package-spec 3.0.2 due to issues with dynamic mappings. These have been held back at 3.0.0.
Proposed commit message
Checklist
changelog.yml
file.Related issues