))
Episode #34 - A trace-based approach to runtime security
Manage episode 376676885 series 3298179
Content provided by ink8r. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by ink8r or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Spyderbat continuously records ALL runtime context in an environment (from Kernel to Cloud) while providing causal linkage (recording both good & bad events alike). Alerts can then be traced along the resultant causal chain that's created. Normal behaviors can then be safely ignored, allowing practitioners to focus on more toxic combinations ONLY (i.e., Alerts-to-Traces).
Practitioners can then group behaviors for another order of magnitude reduction in alerts.
To do this, Spyderbat has developed the following algorithms:
- Guardian - Records context to determine and visualize aggregate event significance in the environment. Guardian is the backbone that surfaces risk while addressing drift by comparing running applications against prior versions
- Flashback - Replays the sequence of activities within/across containers at the earliest warning signs of trouble
- Scout - Maps to Mitre Attack Matrix and Kubernetes Threat Matrix and identifies attacks based on suspicious behaviors.
- Interceptor - Acts as automatic guardrails to protect known-good processes, extracts attackers, and rolls back misconfigurations.
Collectively this delivers on the value chain from causality through enforcement.
45 episodes
Share
