Cloud Native Runtime Security
Go to file
Lorenzo Fontana 6c5554ca8b docs: add PR 906 to changelog for 0.18.0
Co-Authored-By: Leonardo Di Donato <leodidonato@gmail.com>
Signed-off-by: Lorenzo Fontana <lo@linux.com>
2019-10-31 12:32:39 +01:00
.github update(.github): proposals area into PR template 2019-10-08 16:11:43 +02:00
cmake/modules update: license headers 2019-10-08 16:02:26 +02:00
cpack/debian Add ability to read rules files from directories (#348) 2018-04-05 17:03:37 -07:00
docker docs(docker): version bump to 0.18.0 2019-10-31 12:32:39 +01:00
examples update: license headers 2019-10-08 16:02:26 +02:00
integrations docs(integrations): bump version to 0.18.0 2019-10-31 12:32:39 +01:00
proposals chore(proposals): apply code review about PSP rules proposal 2019-10-14 13:59:15 +02:00
rules rules update: add calico/node to trusted privileged container list; add calico_node_write_envvars macro to exception list of write below etc 2019-10-25 15:18:32 +02:00
scripts update: license headers 2019-10-08 16:02:26 +02:00
test Use falcoctl 0.0.4+ tests for space/dash psp names 2019-10-25 01:57:00 +02:00
tests Add explicit catch2 dependency for tests 2019-10-08 16:12:18 +02:00
userspace Don't pop excess values from stack 2019-10-30 08:52:46 +01:00
.clang-format chore: clang format following the current style 2019-07-03 09:07:00 +02:00
.cmake-format new: cmake format file 2019-07-08 19:05:06 +02:00
.gitignore fix: ignore build files generated by the regression tests 2019-08-13 15:48:06 +02:00
.luacheckrc new: luacheck basic config 2019-07-10 18:49:02 +02:00
.travis.yml Use xenial instead of trusty 2019-10-15 19:45:31 +02:00
.yamllint.conf new: YAML lint configuration 2019-07-10 13:00:03 +02:00
ADOPTERS.md Added more context on Sysdig Secure in Adopters.md 2019-10-10 12:59:03 +02:00
CHANGELOG.md docs: add PR 906 to changelog for 0.18.0 2019-10-31 12:32:39 +01:00
CMakeCPackOptions.cmake update: license headers 2019-10-08 16:02:26 +02:00
CMakeLists.txt update: license headers 2019-10-08 16:02:26 +02:00
CODE_OF_CONDUCT.md docs: markdown code of conduct 2019-09-13 12:57:17 +02:00
CONTRIBUTING.md docs: markdown code of conduct 2019-09-13 12:57:17 +02:00
COPYING docs: update COPYING 2019-10-08 16:02:26 +02:00
falco.yaml update: license headers 2019-10-08 16:02:26 +02:00
GOVERNANCE.md docs: markdown governance 2019-09-13 12:57:17 +02:00
OWNERS new: add @kris-nova to owners 2019-08-13 22:42:43 +02:00
README.md docs: update changelog to 0.18.0 2019-10-31 12:32:39 +01:00

Falco

Latest release

v0.18.0 Read the change log

Dev Branch: Build Status
Master Branch: Build Status
CII Best Practices: CII Best Practices


Falco is a behavioral activity monitor designed to detect anomalous activity in your applications. Powered by sysdigs system call capture infrastructure, Falco lets you continuously monitor and detect container, application, host, and network activity—all in one place—from one source of data, with one set of rules.

Falco is hosted by the Cloud Native Computing Foundation (CNCF) as a sandbox level project. If you are an organization that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details read the Falco CNCF project proposal.

What kind of behaviors 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.
  • 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.

Installing Falco

A comprehensive installation guide for Falco is available in the documentation website.

How do you compare Falco with other security tools?

One of the questions we often get when we talk about Falco is “How does Falco differ from other Linux security tools such as SELinux, AppArmor, Auditd, etc.?”. We wrote a blog post comparing Falco with other tools.

Documentation

See Falco Documentation to quickly get started using Falco.

Join the Community

  • Join the mailing list for news and a Google calendar invite for our Falco open source meetings. Note: this is the only way to get a calendar invite for our open meetings.
  • Website for Falco.
  • Join our Public Slack channel for open source Sysdig and Falco announcements and discussions.

Office hours

Falco has bi-weekly office hour style meetings where we plan our work on the project. You can get a Google calendar invite by joining the mailing list. It will automatically be sent.

Wednesdays at 8am Pacific on Zoom.

License Terms

Falco is licensed to you under the Apache 2.0 open source license.

Contributing

See the CONTRIBUTING.md.