-
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
4d3ebf8
atp MVP push
P1llus 27a60ba
stashing changes for later
P1llus 86e8f72
Initial MVP for Defender ATP
P1llus f344d42
Updating default config
P1llus 443ac5d
some updates, still not complete before more testing with new httpjso…
P1llus 0296140
added new things to the pipeline, sorted them and commented them for …
P1llus 24c655f
updated ingest pipeline with more ECS fields and evidence fields
P1llus cb01b5e
updated pipelines to fix yml indentations and added date_cursor funct…
P1llus 6be6205
mage fmt update
P1llus cbf15f4
applying some new changes for date cursor and rebasing
P1llus 8d6b316
Cleaning up pipelines, adding testdata, updating config fields, makin…
P1llus b46e849
changes to generate golden files
leehinman 31ace16
adding requested changes based on PR comments, fixing some field type…
P1llus e7132bc
adding null checks for evidence subfield
P1llus 37eeb56
updating painless scripts
P1llus db32b3a
mage fmt update
P1llus fc70654
one last styling change, will need to revert the event.test.message o…
P1llus a23be78
update golden files
P1llus fcb1082
updating tests to ignore timestamp and event.ingested
P1llus 00b9f63
temp removing the default text for dashboard, dashboard will be inclu…
P1llus a4e762a
Merge branch 'master' into filebeat_atp_module_mvp
P1llus 937975b
updating docs due to merge with microsoft dhcp
P1llus File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
mage fmt update
- Loading branch information
commit db32b3af6dd4b0df8be9d03d26264c4fb9b663d1
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?)