Use ECS definitions for email.attachments and threat.enrichments - #19396
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
The external ECS definition is explicitly used for these fields, because the dynamic template shipped with Elasticsearch doesn't map any nested fields and these are the ones we use. This is for all relevant SSI integrations: - abnormal_security - amazon_security_lake - box_events - cloudflare_logpush - darktrace - dataminr_pulse - eset_protect - google_workspace - ironscales - microsoft_exchange_online_message_trace - mimecast - o365 - proofpoint_365totalprotection - proofpoint_essentials - proofpoint_on_demand - proofpoint_tap - sublime_security - ti_google_threat_intelligence - ti_greynoise - ti_rapid7_threat_command - zscaler_zia For the threat intelligence integrations, the change is made in both the source data streams and the transform destination index field mappings. There are subfields of these nested fields that are mapped differently (in ECS), and those are untouched. The aws_bedrock integration uses ECS git@v8.11.0. That version doesn't include the field gen_ai.response.finish_reasons, which the integration manually maps to keyword but later versions of ECS map to nested. That manual mapping is untouched here, but should be revisited with a general ECS update.
cb11670 to
a4e6511
Compare
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
# Conflicts: # packages/eset_protect/changelog.yml # packages/eset_protect/manifest.yml
13f2eb0 to
48a12c7
Compare
TL;DRAll 4 failed jobs are the same failure: the package README files are stale versus current generated output, so Remediation
Investigation detailsRoot CauseThis is a documentation generation drift failure (not a runtime test failure): Buildkite’s package check regenerated README content and found diffs, then failed. The diffs are all in ECS field-table content around Relevant ECS references in package build config:
Evidence
Verification
Follow-upIf you already regenerated READMEs and still see this, make sure all generated README changes are committed (including any package-level generated docs touched by Note 🔒 Integrity filter blocked 2 itemsThe following items were blocked because they don't meet the GitHub integrity level.
To allow these resources, lower tools:
github:
min-integrity: approved # merged | approved | unapproved | noneWhat is this? | From workflow: PR Buildkite Detective Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
48a12c7 to
9cf5ce8
Compare
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
|
|
Package abnormal_security - 1.15.1 containing this change is available at https://epr.elastic.co/package/abnormal_security/1.15.1/ |
|
Package amazon_security_lake - 2.8.3 containing this change is available at https://epr.elastic.co/package/amazon_security_lake/2.8.3/ |
|
Package box_events - 3.3.1 containing this change is available at https://epr.elastic.co/package/box_events/3.3.1/ |
|
Package cloudflare_logpush - 1.46.1 containing this change is available at https://epr.elastic.co/package/cloudflare_logpush/1.46.1/ |
|
Package darktrace - 2.2.1 containing this change is available at https://epr.elastic.co/package/darktrace/2.2.1/ |
|
Package dataminr_pulse - 0.2.2 containing this change is available at https://epr.elastic.co/package/dataminr_pulse/0.2.2/ |
|
Package eset_protect - 2.5.1 containing this change is available at https://epr.elastic.co/package/eset_protect/2.5.1/ |
|
Package google_workspace - 3.4.1 containing this change is available at https://epr.elastic.co/package/google_workspace/3.4.1/ |
|
Package ironscales - 0.2.1 containing this change is available at https://epr.elastic.co/package/ironscales/0.2.1/ |
|
Package microsoft_exchange_online_message_trace - 2.2.1 containing this change is available at https://epr.elastic.co/package/microsoft_exchange_online_message_trace/2.2.1/ |
|
Package mimecast - 3.4.3 containing this change is available at https://epr.elastic.co/package/mimecast/3.4.3/ |
|
Package o365 - 3.10.2 containing this change is available at https://epr.elastic.co/package/o365/3.10.2/ |
|
Package proofpoint_365totalprotection - 0.1.1 containing this change is available at https://epr.elastic.co/package/proofpoint_365totalprotection/0.1.1/ |
|
Package proofpoint_essentials - 1.1.1 containing this change is available at https://epr.elastic.co/package/proofpoint_essentials/1.1.1/ |
|
Package proofpoint_on_demand - 1.10.1 containing this change is available at https://epr.elastic.co/package/proofpoint_on_demand/1.10.1/ |
|
Package proofpoint_tap - 1.31.1 containing this change is available at https://epr.elastic.co/package/proofpoint_tap/1.31.1/ |
|
Package sublime_security - 1.12.1 containing this change is available at https://epr.elastic.co/package/sublime_security/1.12.1/ |
|
Package ti_greynoise - 0.9.1 containing this change is available at https://epr.elastic.co/package/ti_greynoise/0.9.1/ |
|
Package ti_rapid7_threat_command - 2.10.1 containing this change is available at https://epr.elastic.co/package/ti_rapid7_threat_command/2.10.1/ |
|
Package zscaler_zia - 3.22.1 containing this change is available at https://epr.elastic.co/package/zscaler_zia/3.22.1/ |
1 similar comment
|
Package zscaler_zia - 3.22.1 containing this change is available at https://epr.elastic.co/package/zscaler_zia/3.22.1/ |
Proposed commit message
Checklist
changelog.ymlfile.Related issues
ecs@mappingsdoes not map ECS nested fields, causing mapping conflicts elasticsearch#150902