Repository navigation
Idea: a 'response sidecar' for Falco - ransomware kill-path (Rust/eBPF, standalone) #4025
BartoszOsiej
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Falco team,
Falco is the de facto standard for runtime detection - and deliberately
doesn't respond. I've been building the other half: Talus, a
response engine for Linux ransomware (Rust/aya, no kernel modules,
self-hosted, single binary). When ransomware behavior shows up, it
SIGKILLs the offending process in the same second - with guardrails so
you never kill the host by accident.
Design write-up: https://dev.to/bartoszosiej/killing-ransomware-from-inside-the-kernel-writing-the-response-engine-for-an-ebpf-monitor-in-rust-5gfi
Repo: https://github.com/BartoszOsiej/talus-process-monitor
Question for the maintainers and users here: does a "response sidecar"
for Falco users make sense at all (Falco detects -> Talus kills, scoped
to ransomware behavior only)? Or does response belong upstream in the
Falco rules/action model?
Genuinely asking for feedback - tear the design apart, that's the point
of this post. Worst case this becomes a good "why not" discussion for
anyone considering response automation.
Bartosz Osiej - Hartwell Labs
All reactions