- Notifications
You must be signed in to change notification settings - Fork 513
crowdstrike: add support for EppDetectionSummaryEvent events #12869
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
Conversation
73579d0 to 909cac0 Compare 🚀 Benchmarks reportTo see the full report comment with |
| Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
packages/crowdstrike/data_stream/fdr/elasticsearch/ingest_pipeline/default.yml Show resolved Hide resolved
chrisberkhout left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Warning:
This change needs more tests for coverage of all cases in the event structures that are expected in the new event type.
To be added in the future?
Hopefully to be added in this change. Waiting on availability. |
| Replayed the fdr changes on falcon. Largely the same except that falcon depends on a metadata field that triggers specific pipelines. The approach is to have a preamble pipeline that does the necessary changes and then passes on to the old pipeline. Also added processor for the severity semantics changes. The pipeline tests look odd since (AFAICS) the severities in the test data were fabricated. |
| field: event.id | ||
| description: Concat the fields used in fingerprint. | ||
| tag: set_event_id | ||
| if: ctx.crowdstrike?.id != null || ctx.crowdstrike?.aid != null || ctx.crowdstrike?.cid != null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kcreddy This likely never happens in real situations, but it does happen in tests. In case it actually does ever happen in real data, I think it would be best to not populate the field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@efd6, Sounds good 👍🏼
💚 Build Succeeded
History
cc @efd6 |
|
| Package crowdstrike - 1.58.0 containing this change is available at https://epr.elastic.co/package/crowdstrike/1.58.0/ |
@efd6 what do you need to create those tests? some sample events for real use case? I think I can provide some since I will have some free time and will already get some sample data to contribute with tests on the Cloudflare integration, the hardest thing will be to anonymize the data, but I think it is doable. |
Yes, what's needed is to populate test-falcon-epp-detection-summary.log so that we are covering more of the logic as described in the original issue. I think we are pretty close (and it's difficult to tell from the coverage report). |
| @leandrojmp Just pinging to see if you have had a chance to collect some of those Crowdstrike events. |
| @efd6 I will try to get some sample events today. |
| @leandrojmp How are we going with getting these events? |




Proposed commit message
See title.
Warning
This change needs more tests for coverage of all cases in the event structures that are expected in the new event type.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots