Platform

One loop, five surfaces.

Security is a continuous operation, not a control that is installed once.

Sentinel observes the AXIS ecosystem, verifies what it receives, detects what is wrong or absent, enforces policy at the boundary, preserves the record, and coordinates recovery. Each surface below owns part of that loop.

Observe

Continuous telemetry from every AXIS service and edge.

Verify

Signed SCEF telemetry, checked before it is trusted.

Detect

Anomaly, policy violation, and absent signal alike.

Protect

Policy enforced at the identity and tenant boundary.

Preserve

Evidence written down before it can be lost.

Recover

Continuity coordinated, state restored, result verified.

Enforcement

Guard

Security is active, continuous and policy-driven.

Guard enforces policy at the boundary: identity, tenant and workspace isolation, privileged activity control, secure execution limits and automatic response to anomalous behaviour.

policy-evaluation
tenant-boundary
privileged-session
execution-limit

Open Guard →

Visibility

Watchtower

Loss of visibility is itself a security event.

Watchtower tracks expected telemetry against received telemetry. A service that goes quiet is not assumed healthy — a coverage gap is raised, scored and worked like any other finding.

coverage-ratio
signal-gap
ingestion-lag
source-health

Open Watchtower →

Validation

Range

Failure is tested before production finds it.

Range is the mandatory adversarial validation environment. Guard, recovery, tenant isolation, prompt-injection resistance, evidence integrity and Sentinel's own control plane are exercised against controlled scenarios.

scenario-result
control-efficacy
regression
coverage-delta

Open Range →

Record

Evidence

Evidence survives the incident.

Ledger, Trace and Pulse. A durable event history, the means to reconstruct how a decision propagated, and the current operational state — with raw evidence preserved separately from its searchable index.

ledger-write
trace-span
pulse-sample
integrity-check

Open Evidence →

Recovery

Continuity

Security remains operational under pressure.

Safe Mode and COLOSSEUM coordination. Under a severe incident Sentinel preserves control, identity and evidence capture rather than shutting everything down, and verifies recovery once state is restored.

safe-mode-state
preservation-job
recovery-drill
restore-verification

Open Continuity →

Safe Mode

The state Sentinel enters when things are worst.

Safe Mode is not an outage. It is a deliberate posture that keeps identity, read access, evidence capture and incident response available while restricting the operations that could compound an incident.

How Safe Mode works

Command

Where all five surfaces report.

Sentinel Command is the operational surface: system status, security events, infrastructure health, tenant isolation, visibility coverage, evidence state, recovery readiness and incident state, on one screen.

Open Sentinel Command