-
Notifications
You must be signed in to change notification settings - Fork 909
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
Add PIDs to default rules #2211
Conversation
Signed-off-by: Kyle Smith Hanna <kyle.smithhanna@spyderbat.com>
Welcome @spyder-kyle! It looks like this is your first PR to falcosecurity/falco 🎉 |
/milestone 0.33.0 |
lgtm |
LGTM label has been added. Git tree hash: e00fe2f3810e8744eed92f90e9411085d98db91a
|
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: darryk10, FedeDP, leogr, spyder-kyle The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Kyle Smith Hanna kyle.smithhanna@spyderbat.com
What type of PR is this?
/kind rule-update
Any specific area of the project related to this PR?
/area rules
What this PR does / why we need it:
As I said in the issue, this PR adds the
proc.pid
to all the default rules, allowing for unique identification of rule trigger causes. It is not feasible without this change to combine Falco data with other data sources in most cases.Which issue(s) this PR fixes:
Fixes #2209
Special notes for your reviewer:
Does this PR introduce a user-facing change?: