Fix Dedup Period for Crowdstrike.Detection.passthrough #1445
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
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.
Background
The dedup period for this rule was set to 0 minutes, causing the backend to revert to the default of 1 hour. Since the behaviour for 0 dedup minutes is not strictly defined, this PR changes the dedup to 1 hour to preserve the same functionality customer's are already experiencing. We believe there's no need to shorten the dedup period, since the
dedupfunction in the rule code itself is already returning a sufficiently unique value.Follows from ASK-1133.
Changes
DedupPeriodMinutesfrom0to60Testing