Repository navigation
does falco mTLS webserver settings also covers k8saudit plugin endpoint #3952
Replies: 1 comment
|
No—the Falco core webserver TLS settings do not turn the k8saudit plugin's port 9765 into an mTLS server. They are two separate servers:
The current k8saudit source makes the distinction clear:
Source:
Therefore For a secure deployment today, terminate mTLS in a sidecar/proxy in the Falco Pod: Configure the audit webhook kubeconfig with:
Have the proxy require and verify that client certificate, bind/expose only the proxy port, and keep the plugin port loopback-only or unreachable through NetworkPolicy. If NodePort is unavoidable, also restrict it at the node firewall/security-group layer to control-plane source addresses. A feature request belongs in So your reading is correct: native mTLS for the audit webhook is not covered by the existing Falco webserver settings; use a terminating proxy now and open a k8saudit-plugin feature request for first-class support. |
Uh oh!
There was an error while loading. Please reload this page.
Sorry this might seems to be a duplication of #3951 but i didn't see that "Discussions" tab was available on the falco core repo when redacting the issue.
Just let me know if i need to close it or close the current discussion.
Purpose
I would like to have some details and/or clarifications regarding the mTLS configuration in Falco and if it also enables mTLS for the k8saudit plugin endpoint (default port 9765) or not.
Those clarifications could be transcripted accordingly in documentation to be more explicit if it seems legit, the reason why i issued issue #3951 first.
Context
I want to deploy falco with both syscall and audit-logs sources on a Rancker RKE2 cluster and to avoid some complexity, i wanted to configure
dnsPolicy: ClusterFirstWithHostNeton the kube-apiserver as described in kubernetes documentation Kubernetes.io | DNS for Services and Pods | pod-s-dns-policy and reference an in-cluster (clusterIP) service audit-webhook to reach falco k8saudit endpoints.It works smoothly on kubernetes vanilla, but it seems not quite possible, easy nor recommended on a Rancher RKE2 cluster environement so i'm studying an alternate way to do that by referencing a nodePort service (which don't require dns resolution of internal services) in the audit-webhook.yaml file.
As nodePort service may expose falco publicly to outside of the cluster i would like to implement mTLS between kube-apiserver and falco k8saudit endpoint to lower the risk induced by the nodePort service public exposition.
After some research, i found that mTLS is configurable in falco chart in 2 areas:
Certificate used as client certificate when communicating with falcosidekick, global http_output section and appropriate lines L1214 , L1217 and L1220
Certificate used as client certificate when communicating with falco webserver receiving events, global certs section and appropriate lines L495 , L497 of client subsection
In the same time k8saudit plugin readme seems to indicate that the plugin itself embeds another webserver, different from the falco (core) one:
TL;DR: do thoses settings (2nd topic of the above numbered list) also enables mTLS for k8saudit plugin endpoint (default port 9765) or should a FeatureRequest be raised in k8saudit plugin repo to specificly handle mTLS at k8saudit plugin level ?
Thanks in advance for your details and clarifications.
All reactions