Feature Request: Reloading configuration without restarting Falco

[mumoshu]

Hey! Thanks a lot for maintaining an awesome project.

I'd like propose this feature, either an ability to reload falco config without restarting, or graceful restarting. So that Falco won't drop events while restarting, which is nice for completeness of monitored activities.

Use-case

My specific use-case for this feature is "falco-operator".

Operator is a common idiom in Kubernetes to pair CRD with a Kubernetes controller, so that CRUD to the custom resources result in updating the state of the app on which the operator is operating.

More specifically, "falco-operator" works by watching changes in custom resources containing falco rules. Any falco rules contained in custom resources are concatenated and form a complete falco config file, that is reloaded into falco.

The benefit of this operator is that, now you can delegate management of falco rules to anyone who uses the Kubernetes cluster, including not only securit yengineers but also application developers.

However, falco requiring a restart to reload the configuration file results in intermittent suspends in behavioral monitoring. I think this is a slight security issue itself. Alternatively, I can make the operator to buffer custom resources changes, batch them, to restart falco less frequently. But it isn't a perfect solution.

[henridf]

Hi @mumoshu very cool to hear you're working on a Falco Operator! Look forward to seeing that.

We're looking at ways to support hot-reloading of config but it requires some pretty invasive changes, so I wouldn't expect it to happen in the near-term.

My recommendation would be to start off with your alternate approach with buffering/batching.

[mumoshu]

Hey. Thanks for your explanation and the recommendation! I do start with the alternative approach.

[mumoshu]

@henridf JFYI, here's my quick and dirty implementation of falco-operator, with the suggested approach of buffering changes for certain periods until actual restarts 😃

A hot-reloading feature in falco would still help it continuously enforce rules.

[henridf]

@mumoshu will take a look at the operator, thanks!

leaving this issue open to track the hot-reloading feature.

[mstemm]

A fix for this is in #457. On SIGHUP falco will entirely restart its main loop, closing the device for the kernel module and re-reading all config, etc. from scratch.