kubectl-sudo VS falco

With the kubectl-sudo plugin, kubectl commands that require more extensive rights can be executed explicitly as a member of the admin group. This reduces the chance of accidentally modifying or deleting resources on the cluster, for example when running scripts or being in the wrong namespace.

Bootkube - bootkube - Launch a self-hosted Kubernetes cluster kubectx + kubens - Switch faster between clusters and namespaces in kubectl kube-shell - Kubernetes shell: An integrated shell for working with the Kubernetes kuttle: kubectl wrapper for sshuttle without SSH - Kubernetes wrapper for sshuttle kubectl sudo - Run kubernetes commands with the security privileges of another user K9s - Kubernetes CLI To Manage Your Clusters In Style! Ktunnel - A cli that exposes your local resources to kubernetes KubeOperator - Run kubectl command in Web Browser. https://kubeoperator.io/ Vimkubectl - Manage any Kubernetes resource from Vim https://www.vim.org/scripts/script.ph KubeHelper - KubeHelper - simplifies many daily Kubernetes cluster tasks through a web interface.

https://github.com/falcosecurity/falco

Like snort, but looks at system calls.

From one noob to another - I had a lot of fun setting up Falco (https://falco.org) and creating custom policies & alerts.

Falco is a well-known open source security solution originally created by Sysdig. It’s a CNCF incubating project and one of the few (as far as I can tell) options on this list that uses eBPF to scan for vulnerabilities.

Use some kind of SIEM or Falco to alert you to threats (you can't stop them, but a human can always intervene)

Falco, is a security project that can help you detect threats from within your cluster.

https://falco.org/ is a security-focused monitoring and alerting with an eBPF option

On the cgo side I want to highlight two talks: one from Loris Cro about dealing with cross-complition difficulties, that the usage of cgo brings, using the Zig language and the other from Jason Dellaluce and Leonardo Grasso about how to extend Falco, a Kubernetes threat detection engine, which is written in C++, with plugins written in Go, explaining the challenges of integrating cgo in both C and Go.