One observing form stands over a small family of estates. Each estate is its own business. All of them are in its sight.

About

The layer that watches the rest.

Always on guard.Always watching.

AXIS Sentinel is the security, observability, evidence and resilience layer for the services you run. It watches what you connect, keeps the boundaries between customers, preserves what happened, and coordinates recovery when something goes wrong.

Seven statements, each tied to something Sentinel does.

  1. In sight: light reaches as far as the Sentinel's sight does.

    What we hold to

    You cannot protect what you cannot see.

    Protection starts with knowing what exists, what is reporting and how each report is known. A control that cannot see its subject is a hope, not a control.

    In SentinelFirst Light admits every observation through one trust boundary and records how it is known, and Watchtower holds an expectation of what each registered deployment should report.

    First Light

    In sight: light reaches as far as the Sentinel's sight does.

  2. A source that goes quiet is a finding.

    What we hold to

    Loss of visibility is a security event.

    Silence is not health. When a source stops reporting, the quiet is itself a finding, and it is worked like any other.

    In SentinelA source that goes quiet becomes a finding in Watchtower, which also reports on its own health as a separate fact.

    Watchtower

    A source that goes quiet is a finding.

  3. Authority has edges, and the edges are visible.

    What we hold to

    Authority must have boundaries.

    Every person, service and automation that can act on a company needs a defined scope and a ceiling on what it may do, decided before it acts.

    In SentinelGuard passes every request through identity, scope, policy and authority before it decides, with tenant isolation at the data path and graded operator authority.

    Guard

    Authority has edges, and the edges are visible.

  4. The record outlasts the response.

    What we hold to

    Evidence must survive the response.

    Preservation happens before remediation. The record of what occurred must outlast the response to it.

    In SentinelEvidence keeps a hash-chained Ledger of what happened, a Trace of how, and a Pulse of what is true now, with raw evidence preserved apart from its searchable index. Evidence storage is verified per deployment.

    Evidence

    The record outlasts the response.

  5. A ceiling a person set sits above every automated action.

    What we hold to

    Automation must not outrun governance.

    Software and AI agents act faster than people, and their mistakes travel just as fast. Autonomy is acceptable only inside authority that a named person defined. Anything stronger than that authority needs the named person before it is taken.

    In SentinelIn Guard, the strength of what Sentinel actually witnessed sets a ceiling on how hard it may respond, however confident an automated step may be. Anything stronger needs a named person.

    How Guard decides

    A ceiling a person set sits above every automated action.

  6. Recovery is trusted when it is checked, and not before.

    What we hold to

    Recovery must be verified.

    Prevention is never absolute, so the way back has to be proven as well. A recovered system is not trusted until its state has been checked.

    In SentinelContinuity requests preservation, records the outcome and holds an incident open until recovery is verified. Sentinel protects and verifies. Preservation and restore stay a separate mandate.

    Continuity

    Recovery is trusted when it is checked, and not before.

  7. A scheduled pass, every minute, without waiting for anyone to be awake.

    What we hold to

    Security must operate continuously.

    Security is not a control installed once. It is an operation that observes, verifies, responds and tests itself without waiting for a person to be awake.

    In SentinelVisibility is evaluated on a regular schedule, and Range exercises the controls, including Sentinel's own control plane, on demand and in CI.

    Range

    A scheduled pass, every minute, without waiting for anyone to be awake.

The loop

Six states, continuously.

  1. Observe

    Continuous telemetry from every service and edge you connect.

  2. Verify

    Telemetry checked at the gateway before it is trusted.

  3. Detect

    Anomaly, policy violation, and absent signal alike.

  4. Protect

    Policy enforced at the identity and tenant boundary.

  5. Preserve

    Evidence written down before it can be lost.

  6. Recover

    Continuity coordinated, state restored, result verified.

Governance

Protection and recovery stay distinct.

Sentinel protects and observes. Preservation and restore stay a separate mandate, and the two are never merged. A preservation outcome is recorded as what an operator attested, and is labelled as such.

Why it matters

Every company becomes more complex than any one person can watch.

The doctrine above is the answer to that moment, and to everything before it. The case for needing it, stage by stage, is on one page.