detecting-container-escape-with-falco-rules
FeaturedDetect container escape attempts in real-time using Falco runtime security rules that monitor syscalls, file access, and privilege escalation.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- mukul975
- Repository
- mukul975/Anthropic-Cybersecurity-Skills
- Created
- 8 months ago
- Last Updated
- 2 months ago
- Language
- Python
- License
- Apache-2.0
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
performing-cloud-native-forensics-with-falco
Uses Falco YAML rules for runtime threat detection in containers and Kubernetes, monitoring syscalls for shell spawns, file tampering, network anomalies, and privilege escalation. Manages Falco rules via the Falco gRPC API and parses Falco alert output. Use when building container runtime security or investigating k8s cluster compromises.
detecting-container-escape-attempts
Container escape is a critical attack technique where an adversary breaks out of container isolation to access the host system or other containers. Detection involves monitoring for escape indicators
detect-container-escape
Detection, hunting, and hardening for container escape to the host (MITRE ATT&CK T1611 Escape to Host, Privilege Escalation; related T1610 Deploy Container and T1613 Container and Resource Discovery). Keys off Linux auditd syscall records, CNCF Falco and eBPF runtime sensors, and the Kubernetes kube-apiserver audit log to catch namespace breakout, privileged or sensitive-mount workloads, capability abuse, and host-namespace process execution. Gives the defender view, the exact log sources and fields, a prose detection approach pointing to public rule sources, a hypothesis-driven hunt, seccomp and capability hardening, and the honest blind spots. Use when detecting or hunting container escape, investigating a shell spawned in a container, triaging a privileged pod or hostPath mount alert, monitoring seccomp and Linux capabilities on container hosts, or hardening Docker and Kubernetes against breakout to the node.