-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat][New Module] Adding support for Microsoft Defender ATP #19197
Conversation
Pinging @elastic/integrations (Team:Integrations) |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
55abde5
to
707a9c7
Compare
Pinging @elastic/siem (Team:SIEM) |
b0d7969
to
1444813
Compare
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 little changes.
I'll look at the golden files see if I can get those generate.
field: json.description | ||
target_field: rule.description | ||
ignore_missing: true | ||
if: (ctx.json?.description).length() < 1020 |
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.
optional. I'm wondering if we should copy the first 1019 chars, not skip if over 1019.
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.
I think that the sentence would just break off at that point, it would be half a sentence. I think that its just to ensure it never hits the limit as it was the only field that can in very niche usecases maybe include too much info. It wouldn't stop any of the events I have seen, and its more to drop it on ingest rather than creating an error in elasticsearch due to the field size limit (1024?)
x-pack/filebeat/module/microsoft/defender_atp/test/defender_atp-test.json.log-expected.json
Outdated
Show resolved
Hide resolved
b0ff380
to
b9e0092
Compare
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
run tests |
jenkins run tests |
d88d542
to
9e8ecd7
Compare
This is a list of Defender ATP fields that are mapped to ECS. | ||
|
||
[options="header"] | ||
|======================================================================| |
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.
This is great info to have in the docs.
…g it ready for review
…s and resolving some null fields
…nce done. Updating field docs and running mage fmt update
…ded in separate PR
9e8ecd7
to
00b9f63
Compare
jenkins run tests |
jenkins run tests |
This has a docs build issue that needs fixed.
|
…stic#19197) What does this PR do? This PR adds the initial beta support for Microsoft Defender ATP. Why is it important? Adds new products to the supported list for filebeat Co-authored-by: Lee E. Hinman <lee.e.hinman@elastic.co> (cherry picked from commit fead071)
…Microsoft Defender ATP (#19907) * [Filebeat][New Module] Adding support for Microsoft Defender ATP (#19197) What does this PR do? This PR adds the initial beta support for Microsoft Defender ATP. Why is it important? Adds new products to the supported list for filebeat Co-authored-by: Lee E. Hinman <lee.e.hinman@elastic.co> Co-authored-by: Marius Iversen <pillus@chasenet.org> (cherry picked from commit fead071)
…stic#19197) What does this PR do? This PR adds the initial beta support for Microsoft Defender ATP. Why is it important? Adds new products to the supported list for filebeat Co-authored-by: Lee E. Hinman <lee.e.hinman@elastic.co>
What does this PR do?
This PR adds the initial beta support for Microsoft Defender ATP.
Why is it important?
Adds new products to the supported list for filebeat
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
Related issues
Reviewers:
The documentation for the incoming JSON fields is available here:
https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/alerts