Added dangerous commands/background activity catching rules #1646
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
Added new comment for agent preparation
Added rule for dangerous powershell commands + Added rules with level 2 for less critical commands
Corrected log catching (on level 2) of powershell background activity (e.g. on startup or error output). So less mails without importance are sent by ossec.
Or is not needed anymore in rule 20503 due to a second regex ( \w+).
|
Excellent work on this one! |
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.
Added rule for dangerous powershell commands +
Added rules with level 2 for catching less critical background activity commands like powershell starting or error printing for less wrong mail warnings.