Skip to content

Conversation

@rabbitstack
Copy link
Owner

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

If the process termination event arrives, and the sequence contains CreateThread events where the event pid and the pid in the parameters differ, the sequence can be expired when the remote process terminates.

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?


If the process termination event arrives, and
the sequence contains CreateThread events where the event pid and the pid in the parameters differ, the sequence can be expired when the remote process terminates.
@rabbitstack rabbitstack added the rule-engine Anything related to the rule engine label Mar 20, 2025
@rabbitstack rabbitstack merged commit a94d08a into master Mar 28, 2025
12 of 13 checks passed
@rabbitstack rabbitstack deleted the expire-sequence-remote-thread-process branch March 28, 2025 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rule-engine Anything related to the rule engine

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants