Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(rules): New Potential injection via .NET debugging rule #367

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rabbitstack
Copy link
Owner

What is the purpose of this PR / why it is needed?

Identifies creation of a process on behalf of the CLR debugging facility which may be indicative of code injection. The CLR interface utilizes the OpenVirtualProcess method to attach the debugger to the remote process.

What type of change does this PR introduce?


Uncomment one or more /kind <> lines:

/kind feature (non-breaking change which adds functionality)

/kind bug-fix (non-breaking change which fixes an issue)

/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)

/kind breaking (fix or feature that would cause existing functionality to not work as expected

/kind cleanup

/kind improvement

/kind design

/kind documentation

/kind other (change that doesn't pertain to any of the above categories)

Any specific area of the project related to this PR?


Uncomment one or more /area <> lines:

/area instrumentation

/area telemetry

/area rule-engine

/area filters

/area yara

/area event

/area captures

/area alertsenders

/area outputs

/area rules

/area filaments

/area config

/area cli

/area tests

/area ci

/area build

/area docs

/area deps

/area other

Special notes for the reviewer


Does this PR introduce a user-facing change?


@rabbitstack rabbitstack added the rules Anything related to detection rules label Oct 10, 2024
@rabbitstack rabbitstack changed the title feat(rules): Potential injection via .NET debugging feat(rules): New Potential injection via .NET debugging rule Oct 10, 2024
@rabbitstack rabbitstack force-pushed the dotnet-debugging-injection-rule branch 2 times, most recently from 5c7fe9a to 4d57a91 Compare October 15, 2024 16:22
Identifies creation of a process on behalf of the CLR debugging facility which may
be indicative of code injection. The CLR interface utilizes the OpenVirtualProcess
method to attach the debugger to the remote process.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rules Anything related to detection rules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant