Add event-driven memory syscall telemetry
This commit is contained in:
parent
893409b549
commit
a51478fa22
18 changed files with 589 additions and 32 deletions
|
|
@ -64,10 +64,12 @@ against cached process and socket data:
|
|||
|
||||
### Event Detection
|
||||
|
||||
An optional bcc eBPF `execve` monitor feeds a declarative rule engine. This
|
||||
closes the polling gap for short-lived commands and supports custom TOML rules
|
||||
without code changes. Failure is fail-safe: if the probe cannot load, polling
|
||||
continues.
|
||||
Optional bcc eBPF monitors feed event rule engines. The `execve` stream closes
|
||||
the polling gap for short-lived commands and supports custom TOML rules without
|
||||
code changes. The syscall stream watches short-lived memory and anti-analysis
|
||||
behavior: RWX `mprotect`/`mmap`, `memfd_create`, sensitive `ptrace`, seccomp,
|
||||
cross-process memory access, and memory locking. Failure is fail-safe: if a
|
||||
probe cannot load, polling continues.
|
||||
|
||||
### Integrity and Tamper-Evidence
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue