Platform / Detection

Detection reads behavior instead of rebuilding it.

Rules, analytics and correlation mechanisms evaluate a shared behavioral object while remaining independent of the representation layer. [architecture]

Telemetry to Response pipeline Five stages run left to right: telemetry, behavior, detection, investigation, response. The behavior stage is emphasised because it is the layer we add between raw signal and detection. The behavior pipeline Telemetry endpoint, Kubernetes, AI agents Behavior structured, typed, evidence-aware Detection rules, models, correlation Investigation cause, effect, relationships Response decided from clear evidence the layer we add
Behavior is built before detection and remains available to every later stage.
01 / Detection

Several mechanisms, one object

Behavior-native rules, correlation, statistical methods and threat intelligence can evaluate the same structured activity.

[architecture]
02 / Detection

A firing remains inspectable

A detection can retain which behaviors supported it, while each behavior retains the evidence from which it was constructed.

[architecture]
03 / Detection

Tuning starts from structure

Detection engineers can inspect context, actions, effects and coverage gaps rather than inferring them from an alert summary.

[architecture]

Next step

Continue from concept to reference.

The documentation describes the shared vocabulary, architectural boundaries and evidence-state semantics used throughout the platform.

Read the documentation