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][threatintel] Ignore bad indicator IPs for MISP fileset #34195

Merged
merged 4 commits into from Jan 23, 2023
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.next.asciidoc
Expand Up @@ -83,6 +83,7 @@ https://github.com/elastic/beats/compare/v8.2.0\...main[Check the HEAD diff]

*Filebeat*

- Allow the `misp` fileset in the Filebeat `threatintel` module to ignore CIDR ranges for an IP field. {issue}29949[29949] {pull}34195[34195]

*Auditbeat*

Expand Down
3 changes: 3 additions & 0 deletions x-pack/filebeat/module/threatintel/misp/ingest/pipeline.yml
Expand Up @@ -249,6 +249,9 @@ processors:
- "%{IP:threat.indicator.ip}\\|%{NUMBER:threat.indicator.port}"
ignore_missing: true
if: "['ip-src|port', 'ip-dst|port'].contains(ctx.misp?.attribute?.type)"
# MISP may send a CIDR such as 1.2.3.0/22, which is not a valid Elasticsearch IP data type
# https://github.com/elastic/beats/issues/29949
brsolomon-deloitte marked this conversation as resolved.
Show resolved Hide resolved
ignore_failure: true

## Email indicator operations
# Currently this ignores email-message, except setting the type it will leave the rest of the fields under misp.
Expand Down