-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Security_Solution][Endpoint] Resolver leverage ancestry array for queries #69264
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
Changes from all commits
facb497
97c359d
29cb1a0
2e33743
ba93305
cb467d7
5031536
b804ddb
d63287b
db8c3fd
7155add
89d0df6
e6e6749
1050a56
8f46bea
0060c24
db147d8
3f8c433
882b2f9
f8e898f
e253fed
b732114
0bf79ca
78a18f9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -300,6 +300,12 @@ export interface AlertEvent { | |
| thread?: ThreadFields[]; | ||
| uptime: number; | ||
| Ext: { | ||
| /* | ||
| * The array has a special format. The entity_ids towards the beginning of the array are closer ancestors and the | ||
| * values towards the end of the array are more distant ancestors (grandparents). Therefore | ||
| * ancestry_array[0] == process.parent.entity_id and ancestry_array[1] == process.parent.parent.entity_id | ||
| */ | ||
| ancestry: string[]; | ||
| code_signature: Array<{ | ||
| subject_name: string; | ||
| trusted: boolean; | ||
|
|
@@ -469,6 +475,14 @@ export interface EndpointEvent { | |
| name?: string; | ||
| pid?: number; | ||
| }; | ||
| /* | ||
| * The array has a special format. The entity_ids towards the beginning of the array are closer ancestors and the | ||
| * values towards the end of the array are more distant ancestors (grandparents). Therefore | ||
| * ancestry_array[0] == process.parent.entity_id and ancestry_array[1] == process.parent.parent.entity_id | ||
| */ | ||
| Ext: { | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We use a capital here to avoid collisions with ecs core since the ancestry array is a custom extension field.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was wondering what |
||
| ancestry: string[]; | ||
| }; | ||
| }; | ||
| user?: { | ||
| domain?: string; | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these changes are because the origin node is now included in the ancestry map.