Okta processing pipeline #49
Merged
Conversation
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
Adds a new pipeline to handle the following details about the Okta System Log events when imported into Loki: - Use the `json` parser - Convert lower-cased field names into camelCase - Append `event_` to all fieldnames Includes a short test to validate expected behaviour.
Added an additional check for displayMessage, which is used in some rules.
Pull Request Test Coverage Report for Build 4762698865
💛 - Coveralls |
|
LGTM! I just wonder if |
romain-gaillard
approved these changes
Apr 20, 2023
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.
When Okta System Log data is ingested into Loki, it is generally ingested as raw JSON data, and appearing within a top-level "event" object. In addition, the Sigma rules that target this log data use field names that are entirely lower-case, whilst Loki preserves the camelCase of them.
To resolve these discrepancies, this PR adds a new pipeline to the backend which sets the parser for the generated query appropriately, maps the affected field names into camelCase, and appends
event_to all field names.