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

[RFC] Stage 0 - Threat Enrichment #1386

Merged
merged 2 commits into from
May 3, 2021
Merged

Conversation

rylnd
Copy link
Contributor

@rylnd rylnd commented Apr 23, 2021

As documented in the existing threat intel RFC, this proposal aims to solve the threat intel enrichment use case by reusing the threat.indicator fieldset under a new name and as an array of objects, where each object represents an indicator that matched the (now enriched) event, and the matched.* fields on each object provide context for that particular indicator match.

Moving this list of indicators to a new field allows us to:

  • reuse the existing threat.indicator fieldset
  • sidestep the documentation/mapping complexities around when threat.indicator is an object (indicator) vs. when it's an array of objects (enrichment)

Preview of markdown document

Stage 0 (Strawperson) Criteria:

  • Discuss with domain or subject matter experts the utility of these changes
  • Discuss with ECS team whether these changes seem appropriate for ECS

Copy link
Member

@ebeahan ebeahan left a comment

Choose a reason for hiding this comment

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

LGTM for stage 0.

Thanks, @rylnd!

rfcs/text/0000-threat-enrichment.md Outdated Show resolved Hide resolved
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.

None yet

2 participants