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

Filebeat CEF processor/module mapping exception for source.user.group #17216

Closed
adriansr opened this issue Mar 24, 2020 · 1 comment · Fixed by #17220
Closed

Filebeat CEF processor/module mapping exception for source.user.group #17216

adriansr opened this issue Mar 24, 2020 · 1 comment · Fixed by #17220
Labels

Comments

@adriansr
Copy link
Contributor

For confirmed bugs, please report:

Indexing any CEF event with the sourceUserPrivileges(spriv) or destinationUserPrivileges (dpriv) extensions will cause an index error:

Cannot index event [...] (status=400): {"type":"mapper_parsing_exception","reason":"object mapping for [source.user.group] tried to parse field [group] as object, but found a concrete value"}

Because those fields are mapped to source.user.group and destination.user.group, which are objects under ECS. The correct mapping would be source.user.group.name and destination.user.group.name.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

adriansr added a commit to adriansr/beats that referenced this issue Mar 24, 2020
Extensions spriv/dpriv were mapped to {source|destination}.user.group
instead of {source|destination}.user.group.name.

This caused a mapping exception when attempting to ingest CEF logs that
used those extensions.

Fixes elastic#17216
adriansr added a commit that referenced this issue Mar 24, 2020
Extensions spriv/dpriv were mapped to {source|destination}.user.group
instead of {source|destination}.user.group.name.

This caused a mapping exception when attempting to ingest CEF logs that
used those extensions.

Fixes #17216
adriansr added a commit to adriansr/beats that referenced this issue Mar 24, 2020
Extensions spriv/dpriv were mapped to {source|destination}.user.group
instead of {source|destination}.user.group.name.

This caused a mapping exception when attempting to ingest CEF logs that
used those extensions.

Fixes elastic#17216

(cherry picked from commit 99f483e)
adriansr added a commit to adriansr/beats that referenced this issue Mar 24, 2020
Extensions spriv/dpriv were mapped to {source|destination}.user.group
instead of {source|destination}.user.group.name.

This caused a mapping exception when attempting to ingest CEF logs that
used those extensions.

Fixes elastic#17216

(cherry picked from commit 99f483e)
adriansr added a commit that referenced this issue Mar 24, 2020
Extensions spriv/dpriv were mapped to {source|destination}.user.group
instead of {source|destination}.user.group.name.

This caused a mapping exception when attempting to ingest CEF logs that
used those extensions.

Fixes #17216

(cherry picked from commit 99f483e)
adriansr added a commit that referenced this issue Mar 24, 2020
Extensions spriv/dpriv were mapped to {source|destination}.user.group
instead of {source|destination}.user.group.name.

This caused a mapping exception when attempting to ingest CEF logs that
used those extensions.

Fixes #17216

(cherry picked from commit 99f483e)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants