-
Notifications
You must be signed in to change notification settings - Fork 367
Support for BPF-LSM for policy enforcement #484
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
Comments
Can I work on this? I could start on December 20, 2021. I have experience in LSM eBPF while implementing a research prototype with @nam-jaehyun. |
Thank you for the interest. Currently, we are in the phase of analyzing whether BPF LSM can be used for existing policy constructs that are presently fulfilled by AppArmor. @weirdwiz, can you share the analysis xls and may be we can split up the analysis work? WDYT? @nam-jaehyun @weirdwiz |
Thank you for the reply. Ok, then please let me know when the analysis ends. I want to participate in the analysis, but I have to focus on other things until December 20, 2021. |
The design document used for BPF-LSM. |
Feature Request
Currently, KubeArmor supports AppArmor for policy enforcement. SELinux has several limitations on what can be achieved from enforcement point of view.
The new LSM on the corner, the BPF-LSM shows a lot of promise. It essentially will allow KubeArmor to insert eBPF bytecode at LSM hooks. BPF-LSM could do away with the limitations of AppArmor, SELinux internal policy constructs and allow for flexible way of enforcing user-specified policies on containers/hosts.
Why BPF-LSM for KubeArmor?
The primary limitation with BPF-LSM is that it is supported only with latest kernel versions.
Task list:
Is your feature request related to a problem? Please describe the use case.
The primary use-case is to get better coverage and more flexible policy engine.
Describe the solution you'd like
A detailed design document needs to be prepared for handling this.
Which images from cloud providers currently support BPF-LSM?
CC: @daemon1024 @weirdwiz @nam-jaehyun
The text was updated successfully, but these errors were encountered: