-
Notifications
You must be signed in to change notification settings - Fork 70
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
new(rules): Exfiltrating Artifacts via Kubernetes Control Plane #139
Conversation
@incertum: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Rules files suggestionsfalco_rules.yamlComparing Major changes:
Minor changes:
Patch changes:
|
Just added the missing labels /area maturity-incubating |
a066c1b
to
7938bb4
Compare
Rules files suggestionsfalco_rules.yamlComparing Major changes:
Minor changes:
Patch changes:
|
1 similar comment
Rules files suggestionsfalco_rules.yamlComparing Major changes:
Minor changes:
Patch changes:
|
Hey @incertum could you rebase this PR, please? |
042302b
to
d7a039d
Compare
Signed-off-by: Melissa Kilby <[email protected]>
d7a039d
to
b920ec2
Compare
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.
Hi @incertum I agree on the use case and it's something we need in the ruleset. I also agree on keeping the rule in incubating level and disable by default for now. Let's evaluate the noise.
LGTM!
LGTM label has been added. Git tree hash: 5e8154ca31c0edc8b0be016dcc62475b61085e23
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: darryk10, incertum, leogr 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 |
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area rules
Proposed rule maturity level
/area maturity-incubating
What this PR does / why we need it:
Many of the existing rules focus on sensitive files in the traditional Linux sense, which might not align well with containerized applications.
Moreover, exfiltrating artifacts from for example Kubernetes goes beyond just the usual ways of malware, interactive access or RCE. It also involves the control plane, which attackers can target if they've gained unauthorized access, such as through stolen credentials. For instance, they might use commands like
kubectl cp
. However, this kind of activity isn't expected to be the norm in production settings. This presents an opportunity to create a broad rule that can catch such behavior without having to individually profile application-specific secrets or artifacts that attackers might try to lift from the container's file system, if applicable.See #138.
This new rule could not only benefit from feedback, but also expanded testing.
@darryk10 @loresuso @LucaGuerra
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: