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

[SIEM] Update signals index ECS mapping to 1.6-dev, add endpoint alert fields #65740

Merged
merged 8 commits into from
May 14, 2020

Conversation

marshallmain
Copy link
Contributor

Summary

This is a stopgap change to start integrating the SIEM signals schema with the endpoint alert schema. This schema was built using the ECS tooling and the custom yaml schemas found at https://github.com/elastic/endpoint-app-team/tree/master/custom_schemas. When the ECS tooling upgrades are finished (elastic/ecs#837 and elastic/ecs#820) we can add yml files for the signal fields and generate the entire mapping with the ECS tooling.

At some point we should move the yml files into the kibana in the SIEM folder, but when we do we should remove them from the endpoint-app-team repo so we don't have multiple copies that could be out of sync.

Checklist

Delete any items that are not applicable to this PR.

For maintainers

@marshallmain marshallmain added v8.0.0 release_note:skip Skip the PR/issue when compiling release notes Team:Endpoint Response Endpoint Response Team v7.9.0 labels May 7, 2020
@marshallmain marshallmain requested review from a team as code owners May 7, 2020 17:51
@elasticmachine
Copy link
Contributor

Pinging @elastic/endpoint-response (Team:Endpoint Response)

@marshallmain
Copy link
Contributor Author

@elasticmachine merge upstream

@marshallmain marshallmain marked this pull request as draft May 7, 2020 22:12
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

@@ -2516,4 +4276,4 @@
"refresh_interval": "5s"
}
}
}
}
Copy link
Member

Choose a reason for hiding this comment

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

Missing newline?

@FrankHassanabad
Copy link
Contributor

@elasticmachine merge upstream

@FrankHassanabad
Copy link
Contributor

Tested by going to this directory:

x-pack/plugins/siem/server/lib/detection_engine/scripts

And running:

./hard_reset.sh
 ./post_rule.sh 
./post_rule.sh ./rules/queries/query_with_everything.json

And then looking at each rule run and ensuring that the expected histograms and data looks correct.

Copy link
Contributor

@FrankHassanabad FrankHassanabad left a comment

Choose a reason for hiding this comment

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

👍 Thanks for the ECS upgrade!

@marshallmain marshallmain marked this pull request as ready for review May 11, 2020 14:21
@FrankHassanabad FrankHassanabad added release_note:enhancement and removed release_note:skip Skip the PR/issue when compiling release notes labels May 11, 2020
@FrankHassanabad FrankHassanabad changed the title Update signals index ECS mapping to 1.6-dev, add endpoint alert fields [SIEM] Update signals index ECS mapping to 1.6-dev, add endpoint alert fields May 11, 2020
@FrankHassanabad
Copy link
Contributor

@elasticmachine merge upstream

@@ -441,6 +444,141 @@
}
}
},
"dll": {
"properties": {
"code_signature": {
Copy link
Contributor

Choose a reason for hiding this comment

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

@marshallmain Are we going to address splitting these (trusted/untrusted) in a later PR?

Copy link
Contributor Author

@marshallmain marshallmain May 12, 2020

Choose a reason for hiding this comment

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

I'm hoping to address it with the ECS team. I think multiple code signatures is something we should address at the ECS level rather than making our own custom changes to it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thinking about it more, addressing at the ECS level may take some time. I'd like to merge this so we can start and then merge more changes in future PRs.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sounds good, thanks!

@marshallmain
Copy link
Contributor Author

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@marshallmain marshallmain merged commit 11d2374 into elastic:master May 14, 2020
@marshallmain marshallmain deleted the add-alert-mapping branch May 14, 2020 00:14
@spong
Copy link
Member

spong commented May 15, 2020

@marshallmain -- you should be good to backport to 7.x now that #66221 has been merged 🚀

marshallmain added a commit to marshallmain/kibana that referenced this pull request May 15, 2020
…t fields (elastic#65740)

* update ECS schema to 1.6-dev, add endpoint alert fields

* use updated endpoint team schemas

* add newline

* remove extra options

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label May 18, 2020
@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label May 19, 2020
marshallmain added a commit that referenced this pull request May 19, 2020
…t fields (#65740) (#66789)

* update ECS schema to 1.6-dev, add endpoint alert fields

* use updated endpoint team schemas

* add newline

* remove extra options

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@MindyRS MindyRS added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Sep 23, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:enhancement Team:Endpoint Response Endpoint Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM v7.9.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants