[Rule Tuning] Update Okta rules to include Agent index pattern #295
Conversation
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
threat-punter
added
v7.10.0
Domain: Cloud Workloads
Integration: Okta
11 tasks
brokensound77
approved these changes
Sep 15, 2020
Contributor
brokensound77
left a comment
brokensound77
left a comment
There was a problem hiding this comment.
This LGTM
As a note, validation for any non ECS (module-specific) fields passes due to the inclusion of the filebeat-* index. So if a module specific rule ever targets a logs-* index exclusively, it may not pass validation (We would need to update the validation)
threat-punter
deleted the
update-okta-rules-for-ingest-manager-compatibility
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Issues
#255
Summary
This PR updates our prebuilt Okta rules to include the Elastic Agent index, `logs-okta*.
Contributor checklist