Skip to content

feat(telemetry): Introduce Windows Kernel Process provider #520

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

rabbitstack
Copy link
Owner

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

This provider is fundamentally employed to enrich the process state with additional attributes such as integrity level and token elevation info. It also serves as a mechanism to populate process modules that might not be present when the event from
a non-kernel logger session is emitted.

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?


Yes. We should clearly communicate a set of new process attributes. More specifically, process token integrity level, token elevation type, and the flag that indicates if the process token is elevated.

This provider is fundamentally employed to enrich the
process state with additional attributes such as integrity
level and token elevation info.
If the event arrives from the provider and the process
state hasn't been populated with the expected module,
we leverage the internal load image event to append the
module.
@rabbitstack rabbitstack linked an issue Jun 26, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Obtain process token integrity level
1 participant