-
Notifications
You must be signed in to change notification settings - Fork 474
[windows] Windows Defender Data stream overhaul to GA #11249
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
Ready for review and tests. |
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform) |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Made a few corrections. Please review and test now. |
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.
changes LGTM, but I guess this will fully process only a subset of Windows Defender events. Are the other IDs unimportant or there's just no documentation for them?
packages/windows/data_stream/windows_defender/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
packages/windows/data_stream/windows_defender/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
Great question! I targeted all the IDs I observed in my test environment. My hope is that after this beta version of the data stream is out there I can use it at a larger scale and narrow in on more IDs. The problem is that I can't tell what fields and what type of data is expected in the data from the MS docs. Also, this hits the primary ones of interest for sure (malware detected/prevented). It will process most but there will be some casualties, I am sure. Without a full list of Event IDs and their actual field names to expect, it is hard to get this 100% :/ |
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.
Couple of minor comments, otherwise seems good to me
packages/windows/data_stream/windows_defender/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
packages/windows/data_stream/windows_defender/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
packages/windows/data_stream/windows_defender/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
…file path extractions.
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.
Logic looks fine, can't comment on the windows-specific fields though.
/test |
Looks like pipeline tests failed. I will test locally to see what is going on. |
Doesn't appear that the generated test files were pushed. I will get those pushed as soon as I can. |
Ready for tests again! |
/test |
@taylor-swanson could you validate the changes in 3de2f48 please? |
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
windows_defender |
30303.03 | 16949.15 | -13353.88 (-44.07%) | 💔 |
To see the full report comment with /test benchmark fullreport
|
💚 Build Succeeded
History
|
I think the test results are good.
|
Package windows - 2.2.0 containing this change is available at https://epr.elastic.co/search?package=windows |
Good observations. I did reorder because I wanted the system test to use this more practical event in the docs. Also when I generated improved json that maps closer to the real world, I used it as is and didn't try to put them back in the right order. As for the user fields, those were likely residual fields from other windows integrations that this one didn't really use so I capitalized on what actual event fields are being used in the event IDs I was able to generate for my tests. I will be cautious next time keeping these event IDs in the proper order. Thanks for the review! |
* Defender Data stream overhaul to GA * Adjust pipeline to ensure event type is applied * Update Readme * Improve test data with event_data blocks, switch to GSUB and SET for file path extractions. * Generated new JSON test files
* Defender Data stream overhaul to GA * Adjust pipeline to ensure event type is applied * Update Readme * Improve test data with event_data blocks, switch to GSUB and SET for file path extractions. * Generated new JSON test files
Proposed commit message
Overhaul Windows Defender data stream in the Windows integration to make it GA.
Added many ECS fields and removed un-needed fields/processors
Checklist
changelog.yml
file.Screenshots