AppArmor Landlock Kernel modules Disadvantages? Policies are declarative and pre-defined, not dynamically programmable Rules are written in a policy language, compiled/loaded into the kernel Can’t easily change enforcement logic based on runtime conditions without reloading
Application Userspace Monitor 👁️ Kernel Compromised Application Kernel | User space 🐛 Bad action attempted syscall (execve, etc.) Event detected Compare event with policy 🔒 ⚠️ Event is out of policy
for observability and security Tetragon leverages eBPF for real-time security monitoring and enforcement The usability and flexibility of Tetragon make it a valuable tool for modern Linux security Open Questions We looked into a "single system", what about the other parts of usual infrastructure? How to deploy Tetragon at scale? How to know what to put into the policy?