fix: add condition clause in Windows Defender rule #619
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
fukusuket
changed the title
YamatoSecurity
approved these changes
Mar 20, 2024
There was a problem hiding this comment.
@fukusuket Hayabusa is so smart it can detect even without a condition. =)
Thanks for fixing though!
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 Changed
There was no
conditionclause in the Windows Defender rules, so I added it.Sigma.Windows.Hayabusa.Rulerules does not detect logs Velocidex/velociraptor-sigma-rules#24 (comment)For some reason, Hayabusa seems to be able to detect it even if there is no
conditionclause... :)I would appreciate it if you could review when you have time🙏