Skip to content
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

Update security service integrations packages mappings #12624

Draft
wants to merge 18 commits into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .buildkite/pipeline.yml
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,8 @@ env:
ELASTIC_PACKAGE_DISABLE_ELASTIC_AGENT_WOLFI: "${ELASTIC_PACKAGE_DISABLE_ELASTIC_AGENT_WOLFI:-false}"
# Disable checking for newer versions
ELASTIC_PACKAGE_CHECK_UPDATE_DISABLED: "true"
# Select method to validate fields are documented
ELASTIC_PACKAGE_FIELD_VALIDATION_TEST_METHOD: "mappings"

steps:
- label: "Get reference from target branch"
Expand Down
2 changes: 1 addition & 1 deletion .buildkite/scripts/common.sh
Original file line number Diff line number Diff line change
Expand Up @@ -757,7 +757,7 @@ teardown_test_package() {
}

list_all_directories() {
find . -maxdepth 1 -mindepth 1 -type d | xargs -I {} basename {} | sort
find . -maxdepth 1 -mindepth 1 -type d | xargs -I {} basename {} | sort |grep -E '^(box_events|claroty_ctd|crowdstrike|github|mimecast|sublime_security|teleport|ti_anomali|ti_custom|tychon|wiz)$'
}

check_package() {
Expand Down
2 changes: 2 additions & 0 deletions go.mod
Original file line number Diff line number Diff line change
Expand Up @@ -231,3 +231,5 @@ require (
sigs.k8s.io/structured-merge-diff/v4 v4.4.2 // indirect
sigs.k8s.io/yaml v1.4.0 // indirect
)

replace github.com/elastic/elastic-package => github.com/mrodm/elastic-package v0.53.1-0.20250205174526-5b3f7cdba246
4 changes: 2 additions & 2 deletions go.sum
Original file line number Diff line number Diff line change
Expand Up @@ -125,8 +125,6 @@ github.com/dustin/go-humanize v1.0.1 h1:GzkhY7T5VNhEkwH0PVJgjz+fX1rhBrR7pRT3mDkp
github.com/dustin/go-humanize v1.0.1/go.mod h1:Mu1zIs6XwVuF/gI1OepvI0qD18qycQx+mFykh5fBlto=
github.com/elastic/elastic-integration-corpus-generator-tool v0.10.0 h1:sx1lpZuTG5suJuvgix4FWQFCLFFbzkoOmPoHWYOPLCY=
github.com/elastic/elastic-integration-corpus-generator-tool v0.10.0/go.mod h1:2/30n+2QRzRzus4TPVUV1T3U/j8g2ItUgvP0pcpjLGk=
github.com/elastic/elastic-package v0.109.1 h1:ATZVgYOCI6L5Yr0NxjSX+MsuK4UvXkpu9tDkO4K2vgo=
github.com/elastic/elastic-package v0.109.1/go.mod h1:vmVYISfxBrl0ejjKbm/AG0drjrmevysVg2ZIP7yewLo=
github.com/elastic/go-elasticsearch/v7 v7.17.10 h1:TCQ8i4PmIJuBunvBS6bwT2ybzVFxxUhhltAs3Gyu1yo=
github.com/elastic/go-elasticsearch/v7 v7.17.10/go.mod h1:OJ4wdbtDNk5g503kvlHLyErCgQwwzmDtaFC4XyOxXA4=
github.com/elastic/go-licenser v0.4.2 h1:bPbGm8bUd8rxzSswFOqvQh1dAkKGkgAmrPxbUi+Y9+A=
Expand Down Expand Up @@ -372,6 +370,8 @@ github.com/modern-go/reflect2 v1.0.2 h1:xBagoLtFs94CBntxluKeaWgTMpvLxC4ur3nMaC9G
github.com/modern-go/reflect2 v1.0.2/go.mod h1:yWuevngMOJpCy52FWWMvUC8ws7m/LJsjYzDa0/r8luk=
github.com/monochromegane/go-gitignore v0.0.0-20200626010858-205db1a8cc00 h1:n6/2gBQ3RWajuToeY6ZtZTIKv2v7ThUy5KKusIT0yc0=
github.com/monochromegane/go-gitignore v0.0.0-20200626010858-205db1a8cc00/go.mod h1:Pm3mSP3c5uWn86xMLZ5Sa7JB9GsEZySvHYXCTK4E9q4=
github.com/mrodm/elastic-package v0.53.1-0.20250205174526-5b3f7cdba246 h1:EjWls8TjHBNk5E/caFYxZR7DkURTeDevDazWZgO1T7A=
github.com/mrodm/elastic-package v0.53.1-0.20250205174526-5b3f7cdba246/go.mod h1:vmVYISfxBrl0ejjKbm/AG0drjrmevysVg2ZIP7yewLo=
github.com/muesli/reflow v0.3.0 h1:IFsN6K9NfGtjeggFP+68I4chLZV2yIKsXJFNZ+eWh6s=
github.com/muesli/reflow v0.3.0/go.mod h1:pbwTDkVPibjO2kyvBQRBxTWEEGDGq0FlB1BIKtnHY/8=
github.com/muesli/termenv v0.15.2 h1:GohcuySI0QmI3wN8Ok9PtKGkgkFIk7y6Vpb5PvrY+Wo=
Expand Down
5 changes: 5 additions & 0 deletions packages/box_events/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "2.11.1"
changes:
- description: Add missing ECS mappings
type: bugfix
link: http://github.com/elastic/integrations/pull/12624
- version: "2.11.0"
changes:
- description: Add "preserve_original_event" tag to documents with `event.kind` set to "pipeline_error".
Expand Down
7 changes: 7 additions & 0 deletions packages/box_events/data_stream/events/fields/ecs.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# This definition could be removed once Kibana constraint is updated
# to 8.15.2 or higher. "ecs@mappings" component template would define
# the correct dynamic template for it.
- external: ecs
name: threat.enrichments.indicator.first_seen
- external: ecs
name: threat.enrichments.indicator.last_seen
Comment on lines +4 to +7
Copy link
Contributor Author

Choose a reason for hiding this comment

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

These fields were mapped as keyword, but they should be date according to ECS:

field "threat.enrichments.indicator.first_seen" is undefined: actual mapping type (keyword) does not match with ECS definition type: date

Added field definitions for them using external.

2 changes: 2 additions & 0 deletions packages/box_events/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -270,4 +270,6 @@ Preserves a raw copy of the original event, added to the field `event.original`.
| related.description | Array of `description` derived from `threat[.enrichments].indicator.description` | keyword |
| related.indicator_type | Array of `indicator_type` derived from `threat[.enrichments].indicator.type` | keyword |
| related.location | Array of `location` derived from `related.ip` | geo_point |
| threat.enrichments.indicator.first_seen | The date and time when intelligence source first reported sighting this indicator. | date |
| threat.enrichments.indicator.last_seen | The date and time when intelligence source last reported sighting this indicator. | date |

2 changes: 1 addition & 1 deletion packages/box_events/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: "3.0.3"
name: box_events
title: Box Events
version: "2.11.0"
version: "2.11.1"
description: "Collect logs from Box with Elastic Agent"
type: integration
categories:
Expand Down
5 changes: 5 additions & 0 deletions packages/claroty_ctd/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "0.4.1"
changes:
- description: Add missing ECS mappings
type: bugfix
link: http://github.com/elastic/integrations/pull/12624
- version: "0.4.0"
changes:
- description: Add "preserve_original_event" tag to documents with `event.kind` manually set to "pipeline_error".
Expand Down
6 changes: 6 additions & 0 deletions packages/claroty_ctd/data_stream/event/fields/ecs.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# This definition could be removed once Kibana constraint is updated
# to 8.15.2 or higher. "ecs@mappings" component template would define
# the correct dynamic template for it.
- external: ecs
name: threat.indicator.modified_at
Comment on lines +4 to +5
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same as in box_events.
Error:

field "threat.indicator.modified_at" is undefined: actual mapping type (keyword) does not match with ECS definition type: date


1 change: 1 addition & 0 deletions packages/claroty_ctd/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -717,6 +717,7 @@ An example event for `event` looks as following:
| log.offset | Log offset. | long |
| log.source.address | Source address from which the log event read/sent. | keyword |
| tags | User defined tags. | keyword |
| threat.indicator.modified_at | The date and time when intelligence source last modified information for this indicator. | date |


### Assets
Expand Down
2 changes: 1 addition & 1 deletion packages/claroty_ctd/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: 3.1.4
name: claroty_ctd
title: Claroty CTD
version: 0.4.0
version: 0.4.1
description: Collect logs from Claroty CTD using Elastic Agent.
type: integration
categories:
Expand Down
5 changes: 5 additions & 0 deletions packages/crowdstrike/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "1.50.1"
changes:
- description: Avoid using dynamic template for flattened fields
type: bugfix
link: http://github.com/elastic/integrations/pull/12624
- version: "1.50.0"
changes:
- description: Allow the usage of deprecated log input and support for stack 9.0
Expand Down
2 changes: 1 addition & 1 deletion packages/crowdstrike/data_stream/fdr/fields/fields.yml
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@
type: long
- name: AsepWrittenCount
type: long
- name: assessments.*
- name: assessments
Copy link
Contributor Author

Choose a reason for hiding this comment

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

All the fields under assessments were not defined (no mappings for it).
This field definition should be without * to avoid creating a dynamic template.

type: flattened
- name: AssociatedFile
type: keyword
Expand Down
2 changes: 1 addition & 1 deletion packages/crowdstrike/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1662,7 +1662,7 @@ and/or `session_token`.
| crowdstrike.__mv_aip | | keyword |
| crowdstrike.__mv_discoverer_aid | | keyword |
| crowdstrike.aipCount | | integer |
| crowdstrike.assessments.\* | | flattened |
| crowdstrike.assessments | | flattened |
| crowdstrike.cid | | keyword |
| crowdstrike.discovererCount | | integer |
| crowdstrike.discoverer_aid | | keyword |
Expand Down
2 changes: 1 addition & 1 deletion packages/crowdstrike/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: crowdstrike
title: CrowdStrike
version: "1.50.0"
version: "1.50.1"
description: Collect logs from Crowdstrike with Elastic Agent.
type: integration
format_version: "3.0.3"
Expand Down
5 changes: 5 additions & 0 deletions packages/github/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "2.3.1"
changes:
- description: Add missing ECS field in latest_code_scanning transform
type: bugfix
link: http://github.com/elastic/integrations/pull/12624
- version: "2.3.0"
changes:
- description: Do not remove `event.original` in main ingest pipeline.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -38,3 +38,5 @@
name: rule.name
- external: ecs
name: tags
- external: ecs
name: message
Comment on lines +41 to +42
Copy link
Contributor Author

Choose a reason for hiding this comment

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

message field was mapped as keyword, but according to ECS should be match_only_text

Error:

field "message" is undefined: actual mapping type (keyword) does not match with ECS definition type: match_only_text

In the data stream does not fail, because the mapping for that field is set by the ecs@mappings component template.

Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ source:
# that ability in order to prevent having duplicate data and prevent query
# time field type conflicts.
dest:
index: "logs-github_latest.dest_code_scanning-1"
index: "logs-github_latest.dest_code_scanning-2"
Copy link
Contributor Author

@mrodm mrodm Feb 6, 2025

Choose a reason for hiding this comment

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

If a new field definition is added to a transform, should this destination index be updated (increment suffix number)?

Same doubt for the other packages updating field definitions in transforms (tychon and wiz).

aliases:
- alias: "logs-github_latest.code_scanning"
move_on_creation: true
Expand Down
2 changes: 1 addition & 1 deletion packages/github/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: github
title: GitHub
version: "2.3.0"
version: "2.3.1"
description: Collect logs from GitHub with Elastic Agent.
type: integration
format_version: "3.0.2"
Expand Down
5 changes: 5 additions & 0 deletions packages/mimecast/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "2.4.4"
changes:
- description: Add missing ECS field mappings
type: bugfix
link: http://github.com/elastic/integrations/pull/12624
- version: "2.4.3"
changes:
- description: Fix rendering of CEL programs in configuration.
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# This definition could be removed once Kibana constraint is updated
# to 8.15.2 or higher. "ecs@mappings" component template would define
# the correct dynamic template for it.
- external: ecs
name: threat.indicator.modified_at
- external: ecs
name: threat.indicator.first_seen

Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# This definition could be removed once Kibana constraint is updated
# to 8.15.2 or higher. "ecs@mappings" component template would define
# the correct dynamic template for it.
- external: ecs
name: threat.indicator.modified_at
- external: ecs
name: threat.indicator.first_seen
Comment on lines +4 to +7
Copy link
Contributor Author

Choose a reason for hiding this comment

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

These two fields are mapped as keywords but they should date.

[0] field "threat.indicator.first_seen" is undefined: actual mapping type (keyword) does not match with ECS definition type: date
[1] field "threat.indicator.modified_at" is undefined: actual mapping type (keyword) does not match with ECS definition type: date

Using external ecs definition to update their mappings.


4 changes: 4 additions & 0 deletions packages/mimecast/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1018,6 +1018,8 @@ An example event for `threat_intel_malware_customer` looks as following:
| mimecast.type | The indicator type, can for example be "domain, email, FileHash-SHA256". | keyword |
| mimecast.valid_from | The valid from date. | date |
| mimecast.value | The value of the indicator. | keyword |
| threat.indicator.first_seen | The date and time when intelligence source first reported sighting this indicator. | date |
| threat.indicator.modified_at | The date and time when intelligence source last modified information for this indicator. | date |


### Threat Intel Feed Malware: Grid
Expand Down Expand Up @@ -1134,6 +1136,8 @@ An example event for `threat_intel_malware_grid` looks as following:
| mimecast.type | The indicator type, can for example be "domain, email, FileHash-SHA256". | keyword |
| mimecast.valid_from | The valid from date. | date |
| mimecast.value | The value of the indicator. | keyword |
| threat.indicator.first_seen | The date and time when intelligence source first reported sighting this indicator. | date |
| threat.indicator.modified_at | The date and time when intelligence source last modified information for this indicator. | date |


### TTP Attachment Logs
Expand Down
2 changes: 1 addition & 1 deletion packages/mimecast/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: "3.0.2"
name: mimecast
title: "Mimecast"
version: "2.4.3"
version: "2.4.4"
description: Collect logs from Mimecast with Elastic Agent.
type: integration
categories: ["security", "email_security"]
Expand Down
5 changes: 5 additions & 0 deletions packages/sublime_security/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "1.5.1"
changes:
- description: Fix sublime_security.email_message.headers.hops.fields group mappings
type: bugfix
link: http://github.com/elastic/integrations/pull/12624
- version: "1.5.0"
changes:
- description: Improve `file_selectors` documentation.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -641,9 +641,22 @@
- name: type
type: keyword
description: The type of authentication result, derived from the field name.
# https://github.com/elastic/kibana/pull/204104
# Option 1: generate all keys as keywords under fields
# - name: fields
# type: object
# object_type: keyword
# object_type_mapping_type: "*"
# Option 2: keep position as long
- name: fields
type: object
object_type: keyword
type: group
fields:
- name: "*"
type: object
object_type: keyword
- name: position
# description: ?
type: long
Comment on lines +644 to +659
Copy link
Contributor Author

Choose a reason for hiding this comment

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

What option should we use here for sublime_security.email_message.headers.hops.fields.position field definition?

The first one would map position as keyword.
The second option keeps the same mapping type (long) that it is created for that field in the last version of this package.

Should it be added descriptions to those fields? If so, could you provide them?

- name: index
type: long
description: Index indicates the order in which a hop occurred from sender to recipient.
Expand Down
3 changes: 2 additions & 1 deletion packages/sublime_security/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1222,7 +1222,8 @@ An example event for `email_message` looks as following:
| sublime_security.email_message.headers.hops.authentication_results.spf_details.server.valid | Whether the domain is valid. | boolean |
| sublime_security.email_message.headers.hops.authentication_results.spf_details.verdict | Verdict of the SPF. | keyword |
| sublime_security.email_message.headers.hops.authentication_results.type | The type of authentication result, derived from the field name. | keyword |
| sublime_security.email_message.headers.hops.fields | | object |
| sublime_security.email_message.headers.hops.fields.\* | | object |
| sublime_security.email_message.headers.hops.fields.position | | long |
| sublime_security.email_message.headers.hops.index | Index indicates the order in which a hop occurred from sender to recipient. | long |
| sublime_security.email_message.headers.hops.received.additional.raw | The raw string for remaining additional clauses, such as transport information. | keyword |
| sublime_security.email_message.headers.hops.received.id.raw | The raw string of 'id' section. | keyword |
Expand Down
2 changes: 1 addition & 1 deletion packages/sublime_security/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: 3.2.1
name: sublime_security
title: Sublime Security
version: 1.5.0
version: 1.5.1
description: Collect logs from Sublime Security with Elastic Agent.
type: integration
categories:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -872,14 +872,20 @@ processors:
field: teleport.audit.aws_region
target_field: cloud.region
ignore_missing: true
# This was failing due to `cloud.region` already existed
override: true # Should it be added an if condition? Should it be added a remove processor?
- rename:
field: teleport.audit.aws_service
target_field: cloud.service.name
ignore_missing: true
# This was failing due to `cloud.service.name` already existed
override: true # Should it be added an if condition? Should it be added a remove processor?
- rename:
field: teleport.audit.aws_host
target_field: cloud.instance.id
ignore_missing: true
# This was failing due to `cloud.instance.id` already existed
override: true # Should it be added an if condition? Should it be added a remove processor?
- rename:
field: teleport.audit.aws_assumed_role
target_field: teleport.audit.app.aws.assumed_role
Expand Down Expand Up @@ -968,6 +974,8 @@ processors:
field: teleport.audit.db_gcp_instance_id
target_field: cloud.instance.id
ignore_missing: true
# This was failing due to `cloud.instance.id` already existed
override: true # Should it be added an if condition? Should it be added a remove processor?
- rename:
field: teleport.audit.db_roles
target_field: teleport.audit.database.roles
Expand Down Expand Up @@ -1407,6 +1415,8 @@ processors:
field: teleport.audit.instance_id
target_field: cloud.instance.id
ignore_missing: true
# This was failing due to `cloud.instance.id` already existed
override: true # Should it be added an if condition? Should it be added a remove processor?
- rename:
field: teleport.audit.exit_code
target_field: process.exit_code
Expand All @@ -1426,11 +1436,17 @@ processors:
field: teleport.audit.account_id
target_field: cloud.account.id
ignore_missing: true
# This was failing due to `cloud.account.id` already existed
override: true # Should it be added an if condition? Should it be added a remove processor?
- rename:
field: teleport.audit.region
target_field: cloud.region
ignore_missing: true
ignore_failure: true
ignore_failure: true # it could already exist this field
# in case it fails previous rename processor, remove the field (not defined in the package)
- remove:
field: teleport.audit.region
ignore_missing: true
- rename:
field: teleport.audit.stdout
target_field: teleport.audit.database.aws.ssm_run.stdout
Expand Down
5 changes: 5 additions & 0 deletions packages/ti_anomali/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "1.25.1"
changes:
- description: Add missing ECS field in intelligence datastream
type: bugfix
link: http://github.com/elastic/integrations/pull/12624
- version: "1.25.0"
changes:
- description: Do not remove `event.original` in main ingest pipeline.
Expand Down
6 changes: 6 additions & 0 deletions packages/ti_anomali/data_stream/intelligence/fields/ecs.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# This definition could be removed once Kibana constraint is updated
# to 8.15.2 or higher. "ecs@mappings" component template would define
# the correct dynamic template for it.
- external: ecs
name: threat.indicator.modified_at

1 change: 1 addition & 0 deletions packages/ti_anomali/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -180,6 +180,7 @@ An example event for `intelligence` looks as following:
| labels.is_ioc_transform_source | Indicates whether an IOC is in the raw source data stream, or the in latest destination index. | constant_keyword |
| threat.feed.dashboard_id | Dashboard ID used for Kibana CTI UI | constant_keyword |
| threat.feed.name | Display friendly feed name | constant_keyword |
| threat.indicator.modified_at | The date and time when intelligence source last modified information for this indicator. | date |


### Anomali ThreatStream via the Elastic Extension
Expand Down
2 changes: 1 addition & 1 deletion packages/ti_anomali/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: ti_anomali
title: Anomali
version: "1.25.0"
version: "1.25.1"
description: Ingest threat intelligence indicators from Anomali with Elastic Agent.
type: integration
format_version: 3.0.2
Expand Down
5 changes: 5 additions & 0 deletions packages/ti_custom/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "0.7.1"
changes:
- description: Add mapping for threat.indicator.url.original in transform
type: bugfix
link: http://github.com/elastic/integrations/pull/12624
- version: "0.7.0"
changes:
- description: Add mapping for log file fingerprint.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,8 @@
type: keyword
- name: threat.indicator.url.full
type: keyword
- name: threat.indicator.url.original
type: wildcard
# Below fields to be moved into base-fields.yml after kibana.version changed to >= 8.14
# Related to fix: https://github.com/elastic/kibana/pull/177608
- name: event.module
Expand Down
Loading