Falco uses different instrumentations to analyze the system workload and pass security events to userspace. We usually refer to these instrumentations as syscall sources since the generated events are strictly related to the syscall context.
There are three supported syscall sources:
- Kernel module (default)
- eBPF probe
- Userspace instrumentation
|Kernel module||eBPF probe||Userspace|
|x86_64||>= 2.6||>= 4.14||No requirements|
|aarch64||>= 3.4||>= 4.17||No requirements|
By default, the kernel module will be installed when installing the Falco debian/rpm package, when running the
falco-driver-loader script shipped within the binary package, or when running the
falcosecurity/falco-driver-loader docker image (that just wraps the aforementioned script).
To install the kernel module, please refer to the installation page.
The eBPF probe is an alternative source to the one described above.
To install the eBPF probe, please refer to the installation page.
To enable the eBPF support in Falco set the
FALCO_BPF_PROBE environment variable to an empty value (ie.
FALCO_BPF_PROBE="", in this way Falco will search under
$HOME/.falco directory for a file called
falco-bpf.o) or otherwise explicitly set it to the path where the eBPF probe resides.
The pdig project is currently in archived status. Falco still has support for userspace instrumentation, but
pdig is not actively maintained currently.
Differently from the other drivers, as the name suggests, userspace instrumentation happens 100% in userspace.
The Falco community, in 0.24.0 promoted the userspace instrumentation feature to official support to be included in Falco.
However, there's a difference between userspace instrumentation and the other drivers. At the moment of writing, the Falco project does not have any officially supported userspace instrumentation implementation.
To summarize: the code that defines the contracts to do userspace instrumentation in Falco itself is stable and under official support. While there's no implementation that reached the status of official support yet
The community is working on an implementation based on
PTRACE(2) that you can find falcosecurity/pdig.
How to enable userspace instrumentation in Falco:
- Start Falco with the
--userspaceflag. This will tell Falco to look at userspace instrumentation instead of looking at the Kernel module (the default).
- Select the userspace instrumentation implementation you want to use (let's take pdig as it is the only one available now)
- Now, since
pdigis still incubating - a very early stage - it's not included in our release process. This, for you, means that to install it, you will need to compile it yourself. Follow the instructions here.
- Now that you have
pdiginstalled, you will need to start it. Remember, in the case of
pdig, it does not know the root process tree you want to instrument by itself. You have to specify that via the
-pflag or start the process with
pdigitself. It's very similar to running a debugger against a binary. You can run a process directly using it or instrument an existing process. Full instructions here.
There are attempts at making the installation process easier, but the community didn't pick one yet and it's likely that many iterations will go into making any one of the below GA. However, here's a list of projects you can look at if you want to get Falco with userspace instrumentation in Kubernetes.
- Falco Trace - a convenient container image to use as a base to add userspace instrumentation to your images.
- Falco Inject - a tool that uses Falco Trace artifacts to inject Falco and userspace instrumentation into your containers via the Kubernetes API.
As you probably already understood, the userspace instrumentation drivers are a bit different, handle them with care!
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.