Cloud Native Runtime Security
Go to file
Lorenzo Fontana 12b7ff9940 build: BUILD_BYPRODUCTS for civetweb
The BUILD_BYPRODUCTS for the civetweb target
is needed so that when Falco is built using Ninja
the falco target can have a reference to
understand what target is building the civetweb lib
and do the build automatically without having to do
`ninja civetweb` first.

Signed-off-by: Lorenzo Fontana <lo@linux.com>
2020-11-16 13:23:27 -05:00
.circleci build: fix build directory for xunit tests 2020-11-05 11:49:40 -05:00
.github build: stale bot adjustements 2020-07-07 12:20:55 +02:00
audits move audit doc 2019-12-17 09:15:41 +01:00
brand docs(brand): documenting Falco color scheme 2020-09-28 15:15:36 +02:00
cmake fix(cmake/modules): patch the max_consumers parameter of the 2020-11-13 09:21:30 -05:00
docker update(docker/tester): split version guessing of Falco version 2020-10-13 07:29:01 -04:00
proposals docs(proposals): new drivers storage obsolate part of existing artifacts storage proposals 2020-10-28 14:11:39 +01:00
rules rule(macro user_known_k8s_client_container): separate list of k8s images 2020-11-11 10:22:45 -05:00
scripts fix(scripts/falco-driver-loader): lsmod usage 2020-11-10 04:11:07 -05:00
test build: fix build directory for xunit tests 2020-11-05 11:49:40 -05:00
tests build: remove civetweb when minimal build 2020-09-10 15:01:07 +02:00
userspace build: remove duplicate item from FALCO_SOURCES 2020-11-10 06:43:15 -05:00
.clang-format chore: clang format following the current style 2019-07-03 09:07:00 +02:00
.cmake-format new: cmake format colums to 120 2020-01-17 19:09:31 +01:00
.gitignore chore: clean up lua from dot files 2020-10-13 05:12:00 -04:00
.luacheckrc chore: clean up lua from dot files 2020-10-13 05:12:00 -04:00
.yamllint.conf new: YAML lint configuration 2019-07-10 13:00:03 +02:00
ADOPTERS.md Add GitLab to ADOPTERS.md 2020-06-30 11:45:58 +02:00
CHANGELOG.md docs: changelog for 0.26.2 2020-11-10 14:10:15 -05:00
CMakeLists.txt build: BUILD_BYPRODUCTS for civetweb 2020-11-16 13:23:27 -05:00
COPYING docs: update COPYING 2019-10-08 16:02:26 +02:00
falco.yaml docs: auto threadiness comment into Falco config 2020-07-07 13:42:09 +02:00
GOVERNANCE.md docs: markdown governance 2019-09-13 12:57:17 +02:00
OWNERS docs: add myself to owners 2020-07-03 16:37:17 +02:00
README.md docs: adding the kubernetes privileged use case to use cases 2020-11-12 14:47:22 -05:00
RELEASE.md feat(docs): Adding meeting notes step to RELASE.md 2020-10-12 11:03:13 -04:00

Cloud Native Runtime Security.


Build Status CII Best Practices Summary GitHub

Want to talk? Join us on the #falco channel in the Kubernetes Slack.

Latest releases

Read the change log.

development stable
rpm rpm-dev rpm
deb deb-dev deb
binary bin-dev bin

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 rule 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?

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.