Cherry-pick #18223 to 7.x: Disable host fields for "cloud", panw, cef modules #19074
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.
Cherry-pick of PR #18223 to 7.x branch. Original message:
What does this PR do?
This changes the default configuration of Filebeat to not add
host
fields to events thatoriginated in other places. The
host
field is defined in ECS as "host on which the event happened" but for data pulled from cloud APIs for data forwarded to Filebeat from other sources (PANW, CEF) thishost
field is inaccurate.The affected "cloud" modules are azure, aws, googlecloud, o365, and okta. By default they will
tag events with
cloud
. This causes the module to not addhost.name
at the input state. And then the default configuration for Filebeat was updated to add awhen
condition to theadd_host_metadata
processors to skip events containing thecloud
tag.For PANW and CEF when data is forwarded to Filebeat from another host/device (this is most of the time) you don't want Filebeat to add
host
. So by default this modules add aforwarded
tag to events that behaves the same as thecloud
tag. If you configure the module to not include theforwarded
tag (e.g.var.tags: [my_tag]
) then Filebeat will add thehost.*
fields.And for PANW I added some additional static
observer.*
fields.Why is it important?
We want Filebeat to follow Elastic Common Schema. And setting
host
with the correct value is part of that. By setting (or not setting host) we can better interpret events. Without this change the Filebeat host is being attributed as the source of many cloud based audit/login events.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Run this config from the x-pack/filebeat dir and verify that events do not contain
host
.Related issues
Relates: #13920
Requires: #18159