-
Notifications
You must be signed in to change notification settings - Fork 19
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
Effective Process Parents, and File/Registry Effective Processes #263
Conversation
… & registry events
/test |
I'm curious about when we should make changes in endpoint-package repo. As member of our team we all add fields/information to events/alerts, then I'm guessing we're all responsible of changing endpoint-package? |
I answered @Trinity2019's question elsewhere. |
/test |
I'm not sure exactly how I got a green build this time, but I at least had to:
|
I confirmed with Protections that this is a reasonable schema, at least to start. We can add more fields later if necessary. |
Change Summary
These fields contain information about an effective process.
The effective process is the process that requested the a specific action, without directly performing it.
Effective Parent Processes
Processes can have effective parents that differ from their regular parents.
For example, on Windows,
wmic process call create notepad
will askWmiPrvSE.exe
to launchnotepad.exe
.WmiPrvSE
will benotepad
's parent, but thewmic
will be the effective parent.Effective Processes
Events can have effective processes that differ from their regular processes.
For example, on Windows,
reg add \\localhost\HKLM\Software\Foo /v Data /t REG_SZ /d 123
will result in a registry event from the Remote Registry service (
svchost.exe
).In this case, the effective process will be
reg.exe
.Sample values
See below for an example process creation event for
wmic process call create notepad
. Note the addition ofprocess.Ext.effective_parent
and how it differs fromprocess.parent
:Full event here
Release Target
This is targeting the 8.4.0 release.
Q/A
For mapping changes:
make
after making the schema changes, and committed any generated files (inschema/
,generated/
)