5d245f6569
First minimally working version with plugins + rule loading/rule evaluation: - In the falco engine, hold rulesets for plugins in a map from plugin id to falco ruleset. - Add new methods "add_plugin_filter" to rules.cpp/falco_engine that adds a filter for a given source and compiled filter. This isn't strictly necessary, as the plugin filterchecks are added when a plugin is registered, but it more cleanly separates filters for syscalls and plugins. - When loading rules, if the source is not syscall or k8s_audit, assume it's a plugin filter and call add_plugin_filter. - In process_sinsp_event, if the event type is PLUGINEVENT_E, use the plugins rulesets map instead of m_sinsp_rules, looking up the appropriate source from the plugin. This doesn't handle extractor plugins yet and I only tested the very minimal happy path but I did get rules loaded and working.
Cloud Native Runtime Security.
Want to talk? Join us on the #falco channel in the Kubernetes Slack.
Latest releases
Read the change log.
| development | stable | |
|---|---|---|
| rpm |  |
 |
| deb |  |
 |
| binary |  |
 |
The Falco Project, originally created by Sysdig, is an incubating CNCF open source cloud native runtime security tool. Falco makes it easy to consume kernel events, and enrich those events with information from Kubernetes and the rest of the cloud native stack. Falco has a rich set of security rules specifically built for Kubernetes, Linux, and cloud-native. If a rule is violated in a system, Falco will send an alert notifying the user of the violation and its severity.
Installing Falco
If you would like to run Falco in production please adhere to the official installation guide.
Kubernetes
| Tool | Link | Note |
|---|---|---|
| Helm | Chart Repository | The Falco community offers regular helm chart releases. |
| Minikube | Tutorial | The Falco driver has been baked into minikube for easy deployment. |
| Kind | Tutorial | Running Falco with kind requires a driver on the host system. |
| GKE | Tutorial | We suggest using the eBPF driver for running Falco on GKE. |
Developing
Falco is designed to be extensible such that it can be built into cloud-native applications and infrastructure.
Falco has a gRPC endpoint and an API defined in protobuf. The Falco Project supports various SDKs for this endpoint.
SDKs
| Language | Repository |
|---|---|
| Go | client-go |
| Rust | client-rs |
| Python | client-py |
What can Falco detect?
Falco can detect and alert on any behavior that involves making Linux system calls. Falco alerts can be triggered by the use of specific system calls, their arguments, and by properties of the calling process. For example, Falco can easily detect incidents including but not limited to:
- A shell is running inside a container or pod in Kubernetes.
- A container is running in privileged mode, or is mounting a sensitive path, such as
/proc, from the host. - A server process is spawning a child process of an unexpected type.
- Unexpected read of a sensitive file, such as
/etc/shadow. - A non-device file is written to
/dev. - A standard system binary, such as
ls, is making an outbound network connection. - A privileged pod is started in a Kubernetes cluster.
Documentation
The Official Documentation is the best resource to learn about Falco.
Join the Community
To get involved with The Falco Project please visit the community repository to find more.
How to reach out?
- Join the #falco channel on the Kubernetes Slack
- Join the Falco mailing list
- Read the Falco documentation
Contributing
See the CONTRIBUTING.md.
Security Audit
A third party security audit was performed by Cure53, you can see the full report here.
Reporting security vulnerabilities
Please report security vulnerabilities following the community process documented here.
License Terms
Falco is licensed to you under the Apache 2.0 open source license.