Skip to main content

Falco

Cloud-native runtime security engine that monitors Linux kernel system calls to detect anomalous behavior in containers.

Technical Architecture & Overview

Falco is an open-source, cloud-native runtime security engine and a graduated CNCF project. It detects anomalous activity in containers, Kubernetes, and Linux hosts by inspecting system calls at runtime, using a flexible rule engine to alert on suspicious behavior.

Targeted Technical Use Cases

Runtime security monitoring for containerized and Kubernetes workloads in cloud environments.

Evaluation & Trade-offs

Core Strengths

  • +CNCF graduated project with broad cloud-native ecosystem adoption.
  • +System call-level detection provides deep runtime visibility without application instrumentation.
  • +Flexible rule engine with a large community-maintained rule set mapped to MITRE ATT&CK.

Trade-Offs & Limitations

  • -Linux-only; system call instrumentation requires kernel module, eBPF, or modern eBPF driver.
  • -Rule tuning is required to reduce false positives in complex container environments.

Defensive Security Application

Detecting runtime threats in containers and Kubernetes, including privilege escalation, file tampering, and network anomalies.

Frequently Asked Questions

What is Falco?

Falco is an open-source, cloud-native runtime security engine and a graduated CNCF project. It detects anomalous activity in containers, Kubernetes, and Linux hosts by inspecting system calls at runtime, using a flexible rule engine to alert on suspicious behavior.

What is Falco used for?

Runtime security monitoring for containerized and Kubernetes workloads in cloud environments.

What are the strengths of Falco?
  • +CNCF graduated project with broad cloud-native ecosystem adoption.
  • +System call-level detection provides deep runtime visibility without application instrumentation.
  • +Flexible rule engine with a large community-maintained rule set mapped to MITRE ATT&CK.
What are the limitations of Falco?
  • +Linux-only; system call instrumentation requires kernel module, eBPF, or modern eBPF driver.
  • +Rule tuning is required to reduce false positives in complex container environments.
How is Falco used defensively?

Detecting runtime threats in containers and Kubernetes, including privilege escalation, file tampering, and network anomalies.