-
Notifications
You must be signed in to change notification settings - Fork 468
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
m365_defender,microsoft_defender_endpoint: drop empty event sets #5164
Conversation
🌐 Coverage report
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
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.
LGTM 👍🏼
Package m365_defender - 1.5.1 containing this change is available at https://epr.elastic.co/search?package=m365_defender |
Package microsoft_defender_endpoint - 2.8.1 containing this change is available at https://epr.elastic.co/search?package=microsoft_defender_endpoint |
This is a port of elastic/integrations#5164. (cherry picked from commit 429bdeb)
…34947) This is a port of elastic/integrations#5164. (cherry picked from commit 429bdeb) Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com> Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
What does this PR do?
The adds checks for empty event sets returned by the MS API and drops documents that have not event.
The change is also added to the deprecated M365 Defender log data stream after off-line discussion with @jamiehynds as there have been a number of reports of this in that package and the change is trivial.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots