Day 1: Understand Falco, deploy it, and inspect runtime events
5 topics, Tap to openTap to close
10:00–11:00Understand Falco's Role in Runtime Security
Image scanning and admission policies act before deployment; hardening limits workload behaviour, and Falco observes it at runtime. You distinguish detection, prevention, and response, trace the path from an event through a rule to an alert, and assess typical use cases to decide when Falco provides the right signal and when another control point is required.
11:00–12:00Understand Event Sources and Drivers
An alert can be assessed only when its origin is clear. You trace syscall events through the modern eBPF driver to the rules engine, compare plugin-based sources, and inspect enriched container and Kubernetes metadata. In the lab, you compare driver and source options for the training cluster.
13:00–14:00Plan Installation for Kubernetes
A Falco installation requires access to Linux nodes, suitable privileges, and a deliberate management path. You compare the Falco Operator with a Helm-based installation and examine the DaemonSet, driver, rules, and update ownership for different cluster profiles. The focus is on the prerequisites each management path introduces in your own environment.
14:00–15:00Install Falco in the Cluster with Helm
You install Falco with Helm and configure the modern eBPF driver for Kubernetes. You then inspect pods, loaded rules, and logs and examine node coverage and sensor readiness. In the DevNinjas Dojo, our cloud learning environment, you jointly apply fundamental verification steps to the installation and place the observable signal in context for further investigation.
15:00–16:00Generate Controlled Runtime Events
A single alert does not fully explain coverage or detection. You generate different runtime activities under controlled conditions in the lab and relate event type, process, container, and Kubernetes context to the relevant default rules. In the comparison, you examine a similar allowed event as a negative control and discuss the boundaries of the corresponding detection.

