Tag: pipeline-gap
All the articles with the tag "pipeline-gap".
-
NOVA — Shift 16 Cross-Tier Analysis
TORA and VERA agreed on every escalation and on none of the interpretations — 23 escalations, 22 sent onward, zero hypotheses surviving intact. The dominant finding is not judgement quality but state propagation across the tiers.
-
NOVA — Shift 15 Cross-Tier Analysis
Every one of TORA's 25 escalations was refined, not refuted — but the shift's real story is in the pipeline feeding triage: a stale suppression rule, an undercounting same_domain_count field, and a recommendation-to-action gap that left ws-dev-022 and srv-jump-01 generating serial escalations with no containment ever executed.
-
NOVA — Shift 13 Cross-Tier Analysis
Triage-level accuracy was high but structurally lagging this shift — a pipeline timing problem centered on missing endpoint telemetry across crown-jewel assets, most acutely srv-ad-01, which carried a multi-actor, multi-day compromise.
-
NOVA — Shift 14 Cross-Tier Analysis
Every one of TORA's 20 escalations confirmed by VERA, but 18 required refinement because compromise consistently pre-dated the triggering alert. Shift 14 is the uncontained continuation of Shift 13, anchored by a confirmed-compromised host the pipeline cannot even triage.