Platform / Architecture

One behavior layer, many consumers.

Nexora structures security activity before detection so every downstream system can reason over the same representation. [architecture]

Architecture overview Seven telemetry sources on the left feed a single emphasised behavior layer in the centre, which in turn feeds six consumers on the right: detection, hunting, correlation, investigation, AI agents and response. Endpoint, Kubernetes and AI agent sources are drawn solid because they are supported today; network, identity, cloud and email are drawn dashed because they are not supported yet. The point of the drawing is that no consumer owns the representation. One behavior layer, many consumers Endpoint Kubernetes AI agent Network Identity Cloud Email Behavior layer structured / typed evidence-aware Detection Hunting Correlation Investigation AI agents Response Each consumer reasons over the same representation, so none of them owns it. Solid sources are supported today; dashed sources are not supported yet.
Telemetry sources (supported ones solid, not yet supported ones dashed) feed one behavior layer, which serves detection, hunting, correlation, investigation and response.
01 / Architecture

The layer has one job

Convert fragmented telemetry into typed behavior without belonging to any individual detector. This keeps representation concerns separate from detection logic and presentation.

[architecture]
02 / Architecture

Inputs remain attributable

Observations from every supported source retain their evidence identity. A behavior does not erase where its supporting material came from.

[architecture]
03 / Architecture

Consumers remain independent

Rules, models, threat hunters and investigators can evolve without each creating a competing definition of the same activity.

[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