x-pack/filebeat/module/okta: add extended okta.debug_context.debug_data handling#31676
Merged
efd6 merged 1 commit intoelastic:mainfrom May 23, 2022
Merged
x-pack/filebeat/module/okta: add extended okta.debug_context.debug_data handling#31676efd6 merged 1 commit intoelastic:mainfrom
efd6 merged 1 commit intoelastic:mainfrom
Conversation
Contributor
Contributor
|
This pull request is now in conflicts. Could you fix it? 🙏 |
Contributor
|
This pull request is now in conflicts. Could you fix it? 🙏 |
Contributor
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
marc-gr
approved these changes
May 23, 2022
chrisberkhout
pushed a commit
that referenced
this pull request
Jun 1, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
This is the beats cognate for elastic/integrations#3362 which adds additional handling of the debug_context.debug_data object and particularly the risk level field that is in that object.
Why is it important?
This adds important fields for threat risk assessment.
Checklist
I have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs