Use suspend-aware BOOTTIME waits and owned-container cleanup without changing the workload. Reject missing coverage and preserve producer/report failures. Include runtime/helper regressions, constrained build-job support and live exec-guard crash safety. Document the failed live/idle gates without relaxing thresholds or claiming production acceptance.
Stage 2 increment 2.
- Connect, ptrace and module-load events go to telemetry raw, before the
behavior engine filters them (pid, uid, comm, address/port or target);
the join to processes happens when the data is read.
- Persistence and drop-location writes go to telemetry before any rule
decides on them.
- The exec guard reports every verdict through a new on_observation hook
(allow verdicts and cache hits included; ExecDecision still reports
only non-allow): verdict, answered, scanned, cache hit, degraded, top
rule/severity and latency, as guard_decision records.
Tests: record round-trips; the live exec-guard test checks one
observation per checked exec, including allows and cache hits;
fuzz_telemetry_records covers the new decoders.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fanotify exec-permission guard (audit/enforce, fail-open deadline),
eBPF behavior engine (IOC connections, ptrace, module loads,
download-then-execute) and fanotify persistence watch, with unit tests
and privileged Docker live tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>