-
Notifications
You must be signed in to change notification settings - Fork 912
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
rules: whitelist GCP's container threat detection image #1959
rules: whitelist GCP's container threat detection image #1959
Conversation
Signed-off-by: Clemence Saussez <[email protected]>
…ion image Signed-off-by: Clemence Saussez <[email protected]>
Welcome @clmssz! It looks like this is your first PR to falcosecurity/falco 🎉 |
Thank you for this, I think this works! @Kaizhe WDYT? |
More info about the proposed image: https://cloud.google.com/security-command-center/docs/how-to-use-container-threat-detection |
LGTM label has been added. Git tree hash: 39bdf1269664d311db07f0829c79edde8f26b7fd
|
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: clmssz, jasondellaluce 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 |
/milestone 0.32.0 |
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:
Container threat detection is a feature of GCP security center that monitors cos nodes for changes and remote access attempts (it kinds of duplicate falco). It spawns a privileged DaemonSet in GKE clusters
kube-system
namespace, hence the need for ignoring this image.Does this PR introduce a user-facing change?: