feat(evasion): Evasion scanner architecture #532
Merged
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
rabbitstack
force-pushed
the
evasions-scanner
branch
from
17d67b4 to
3d8befa
Compare
This changeset establishes the architecture for the evasion scanner. Evasion scanner piggybacks on top of different evasion detectors such as direct syscall (being the first evasion behaviour implemented). When the evasion behaviour is detected, the event is decorated with such evasion in its metadata.
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 is the purpose of this PR / why it is needed?
This changeset establishes the architecture for the evasion scanner. Evasion scanner piggybacks on top of different evasion detectors, such as direct syscall (being the first evasion behaviour implemented).
When the evasion behaviour is detected, the event is decorated with such evasion in its metadata. The purpose of this metadata is to serve as an input for the future filter field that will yield a list of evasions for the detection rules to match.
What type of change does this PR introduce?
/kind feature (non-breaking change which adds functionality)
Any specific area of the project related to this PR?
/area other
Special notes for the reviewer
Does this PR introduce a user-facing change?