Skip to content

Cherry-pick #21795 to 7.x: [Filebeat][New Module] Threat intel module for filebeat#24039

Merged
P1llus merged 2 commits intoelastic:7.xfrom
P1llus:backport_21795_7.x
Feb 15, 2021
Merged

Cherry-pick #21795 to 7.x: [Filebeat][New Module] Threat intel module for filebeat#24039
P1llus merged 2 commits intoelastic:7.xfrom
P1llus:backport_21795_7.x

Conversation

@P1llus
Copy link
Copy Markdown
Member

@P1llus P1llus commented Feb 15, 2021

Cherry-pick of PR #21795 to 7.x branch. Original message:

What does this PR do?

This PR adds a new module for threat intel, using each TI source as a fileset.

Why is it important?

Adds possibility to ingest Threat Intel data to be used for security usecases

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Resolves #23406

* inital MVP commit for threat intel module for filebeat

* Fixing typos based on PR comments

* adding converter for larted field

* adding concept for a new MISP module

* setting correct field type for misp group sharing id

* setting timestamp to age of attribute timestamp

* stashing initial support for AlienVault OTX

* add threatintel.otx to timestamp bypass for testing

* stashing upcoming changes for new httpjson format

* updating settings with pagination

* big overwrite of the whole module to fit the new TI ECS fields, add new test data, and make the ingest pipelines more sturdy

* update default url for anomali

* updating field names based on feedback

* final commit fixing certain bugs, adding the missing field mapping etc

* updating field defintion, it had a duplicate field

* updating the anomali config to access the header in a safer way, allowing for special characters

* added stripping of null values and made sure it looked at the correct document field

* updating field mapping to default_field false

* updating default config descriptions

* disable default_field for top group

* updating changelog

* adding fallback for uri_parts when using older ES version

* updating test_modules to ignore timestamps

* adding support for uri_parts for all relevant ingest pipelines, and fallbacks

* updating default config templates and docs based on PR comments

* Update x-pack/filebeat/module/threatintel/_meta/docs.asciidoc

Co-authored-by: Adrian Serrano <adrisr83@gmail.com>

* mage update

Co-authored-by: Adrian Serrano <adrisr83@gmail.com>
(cherry picked from commit 70d00b9)
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Feb 15, 2021
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Feb 15, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #24039 updated

  • Start Time: 2021-02-15T15:23:29.670+0000

  • Duration: 57 min 18 sec

  • Commit: 233ccc9

Test stats 🧪

Test Results
Failed 0
Passed 12970
Skipped 2047
Total 15017

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 12970
Skipped 2047
Total 15017

@P1llus P1llus merged commit 6db5806 into elastic:7.x Feb 15, 2021
@zube zube bot removed the [zube]: Done label May 17, 2021
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 this pull request may close these issues.

3 participants