AXIS SENTINEL WATCHTOWERCore system

Sentinel knows when it has stopped seeing.

Loss of visibility is itself a security event.

Watchtower holds an expectation of what every registered deployment should report and compares it with what actually arrives. Silence is not assumed to be health: a source that goes quiet becomes a finding, and Watchtower reports on its own health as a separate fact.

A modern tower at night. Its beam cuts one building open and shows a figure inside.
Place on the operating loopOBSERVE / DETECT
  1. 01ObserveContinuous telemetry from every service and edge you connect. (Watchtower operates here)
  2. 02VerifyTelemetry checked at the gateway before it is trusted.
  3. 03DetectAnomaly, policy violation, and absent signal alike. (Watchtower operates here)
  4. 04ProtectPolicy enforced at the identity and tenant boundary.
  5. 05PreserveEvidence written down before it can be lost.
  6. 06RecoverContinuity coordinated, state restored, result verified.

Recover returns to Observe

Watchtower observes what arrives and detects what does not.

A second photograph

The city, read as structure.

The tower and the ridge are the same view. The buildings are drawn as structure. The two photographs are shown apart, because they are not the same pixels.

A modern tower at night. Its beam shows one neighbouring tower as a crimson structural trace.

The grammar of a signal

Steady, uneven, gone. The absence is the finding.

Watchtower does not wait for a source to report a problem, because a source that has stopped cannot. It holds an expectation for every source and reads the shape of what arrives against it.

You cannot protect what you cannot see. A sensor that stops talking is itself a signal.

Every source owes Watchtower a signal at a fixed rhythm, so each source is a rail with a slot for every beat it owes, running from the past toward now. A beat that arrives lights its slot and sends up a filament of light. A beat that does not arrive leaves a hollow ring where it should have been. A monolithic wall stands at now, with one slit for every source: a slit holds light while that source reports and is dark where it has gone quiet. The four states are steady, uneven, stopped, and in sequence, where related sources stop one after another. Reading that last pattern as a possible suppression is a design direction, not built today.

Steady. Every source owes a beat at a fixed rhythm, and every slot is lit all the way to now.

  1. SteadySteady. Every source owes a beat at a fixed rhythm, and every slot is lit all the way to now.
  2. UnevenUneven. One source still reports, but late and in fits. Some slots light, some do not.
  3. StoppedStopped. Its beats end partway along the rail. The slots that should follow stay dark, and the wall of light has a gap.
  4. In sequenceIn sequence. Related sources stop one after another, a staircase of dark slots. Reading that as a pattern is a design direction, not built today.
  1. Full coverage

    Expected telemetry is arriving on its rhythm.

  2. Degraded observation

    Signals late or partial. The picture is incomplete and marked so.

  3. Blind spot

    Expected telemetry has stopped. Not knowing is the finding.

  4. Possible suppression

    Related sources going dark in a pattern, rather than as an ordinary outage.

  • Arrived on time
  • Arrived late
  • Expected, not received
The same stretch of time in every row. Time runs left to right.

The coverage view

Whether Sentinel can still see what it is responsible for.

Every registered deployment is expected to report on a regular rhythm. Command shows when each was last seen, how long it may stay quiet, and why a source changed state.

Three Sentinels stand on separate night rooftops across a city. Their visors are lit crimson. A red beam leaves a tower, and gold shields mark the roofs.
Illustrative demonstration

Watchtower

Visibility, by deployment

Last scheduled passThis minuteCurrent

Registered
Shown
Visible
Shown
Degraded
Shown
Not yet seen
Shown
Disabled
Shown
  1. Primary sitewww.example · production
    On timeExpected reporting rhythm
    Visible
  2. Customer portalportal.example · production
    On timeExpected reporting rhythm
    Visible
  3. Checkoutpay.example · production
    Quiet too longExpected reporting rhythm
    Degraded
  4. Documentationdocs.example · production
    On timeExpected reporting rhythm
    Visible
  5. Partner APIapi.example · production
    Quiet too longExpected reporting rhythm
    Degraded
  6. Status pagestatus.example · production
    On timeExpected reporting rhythm
    Visible
  7. Stagingstaging.example · staging
    Never reportedExpected reporting rhythm
    Not yet seen
  8. Campaign micrositepromo.example · production
    Switched offExpected reporting rhythm
    Disabled
Built from the fields Watchtower holds for a deployment: its visibility, when it was last seen, how often it is expected to report, and the reason recorded with each change. Every value shown is illustrative and nothing here reads a live system.

The estate view

Expected against received.

Signals rise from the estate into the observation field. Step through five snapshots, from full coverage to a possible suppression, and watch where the information disappears.

Illustrative demonstration

Expected against received, across an estate

Possible suppressionDesign direction

Sources are shown as arriving, late or silent; example-app, then example-edge, then service-b silent.

  • Arriving
  • Late
  • Silent

Step 5 of 5

Possible suppression

A third source in the region goes dark, and the silences form a staircase: one source after another, in sequence. A pattern is not an ordinary outage. Correlating related sources like this is a design direction for Watchtower; the demonstration shows how it would read.

  1. Every expected signal arrives on its rhythm. Twelve of twelve sources report in the latest interval, and each ring segment is whole. This is the baseline the other states are read against.

  2. Two sources are still reporting, but late and unevenly. The picture is incomplete and is marked so: the rhythm turns intermittent and the ring segments break, yet nothing has disappeared.

  3. One source stops. Its signal does not fade or turn red: it is gone, and the ring above it is open. Watchtower raises the silence as a finding and reports the cause as unknown, because from the server a closed page, a broken network and a removed agent look the same.

  4. A second source in the same region falls silent soon after the first. Each is its own finding, because today's evaluator works deployment by deployment. Nothing yet says the two are connected.

  5. A third source in the region goes dark, and the silences form a staircase: one source after another, in sequence. A pattern is not an ordinary outage. Correlating related sources like this is a design direction for Watchtower; the demonstration shows how it would read.

Scripted sources and intervals. Nothing here reads or changes a live system. Today Watchtower evaluates registered deployments by the reports they owe; the wider estate drawn here shows how coverage is meant to read.

Every source, expected against received

  • Arrived on time
  • Arrived late
  • Expected, not received
  • Right edge is the latest interval

Showing: Possible suppression

  1. Services

    • service-bRegion EU

      SilentNo signal while it was expected

      Went dark third of the related sources

    • service-cRegion US

      ArrivingOn its rhythm

    • service-aRegion US

      ArrivingOn its rhythm

  2. Edge

    • example-edgeRegion EU

      SilentNo signal while it was expected

      Went dark second of the related sources

    • example-appRegion EU

      SilentNo signal while it was expected

      Went dark first of the related sources

    • payments-serviceRegion US

      ArrivingOn its rhythm

  3. Sites

    • site-primaryRegion US

      ArrivingOn its rhythm

    • site-portalRegion APAC

      ArrivingOn its rhythm

  4. Agents

    • agent-aRegion APAC

      ArrivingOn its rhythm

    • agent-bRegion US

      ArrivingOn its rhythm

  5. Systems

    • identityRegion US

      ArrivingOn its rhythm

    • buildRegion APAC

      ArrivingOn its rhythm

Built today

  • The unit watched is a registered deployment, expected to report on a regular rhythm.
  • A deployment that stays quiet past the time it was given becomes degraded. One that has never reported is not yet seen, and one its owner switched off is counted apart.
  • The same check runs on a schedule and when Command is open, so there are never two answers.
  • Only a change writes: a visibility transition with its reason, a server-observed event and a notification. A deployment already degraded does not raise a new event each pass.
  • The regular reports are protected from ordinary volume, so a busy estate cannot manufacture a false outage.
  • Every pass writes a run record. Only a scheduled pass that finished ok proves the timer is alive.

Design direction, or not built

  • Not builtCorrelating several related sources going dark in sequence as one possible suppression. Today each deployment is evaluated on its own.
  • Not builtEdge and service telemetry as expected sources in the same picture as deployments.
  • Not builtSaying why a source went quiet. Watchtower reports the loss and does not guess the cause.
  • Not builtA watchdog for the watchdog, and alerting or paging routes. The health fact is a read, and nothing polls it on a timer.

Watchtower health

The watcher reports whether it is running.

A monitor that has stopped and still looks calm is worse than none, because someone is relying on it. Watchtower keeps its own record of every pass, and a stale answer is a fact it reports about itself.

Illustrative demonstration

The watcher watches itself

Scheduled passes

Console reads

Last scheduled success
Outside the staleness window
Most recent run
A console read, status ok
Health fact
Stale

Wording reserved for a stale answerSentinel has not checked recently.Not reported as: your sites are degraded.

Step 5 of 5

Command is told plainly

A stale answer is reported as one plain sentence: Sentinel has not checked recently. It is never reported as your sites being degraded, because nothing has checked. An estate that looks calm because nothing is looking is the failure this exists to expose.

  1. A scheduled check runs the evaluator, whether or not anyone has Command open. Every pass writes a run record with its trigger, status, duration and any error. That record is the watcher's own proof of life.

  2. Opening Command runs the same evaluator lazily, so the answer on screen is current. It is recorded as a read pass, and it is never counted as evidence that the scheduler is alive.

  3. The timer stops. Reads carry on while an operator refreshes the page, and the last run now looks recent, but the scheduled lane has gone quiet. Only a scheduled pass counts, so a refresh cannot hide it.

  4. No scheduled pass has completed inside the staleness window. The health fact turns stale. It is a fact about the watcher, separate from every deployment's visibility, and the two are never folded together.

  5. A stale answer is reported as one plain sentence: Sentinel has not checked recently. It is never reported as your sites being degraded, because nothing has checked. An estate that looks calm because nothing is looking is the failure this exists to expose.

Scripted minutes. Nothing here reads or changes a live system. The pass, the run record and the staleness window follow the scheduled check and Command's health read; the marks on the ruler are illustrative.

Signal path

What enters it, and what leaves.

Signals in

  • Agent signals, on a reserved budget
  • Telemetry arrival per deployment
  • The registry of deployments expected to report
  • Its own scheduled run history

Watchtower

OBSERVE / DETECT

Outputs

  • Visibility per deployment: visible, degraded, not yet seen or disabled
  • Server-observed events when visibility is lost
  • Every visibility transition, with its reason
  • Watchtower health: last scheduled pass, status and staleness

Ten questions

Watchtower, answered.

The questions every Sentinel system must answer, in the same order on every system page.

Watchtower is Sentinel's visibility system. It compares the telemetry each deployment should send with what arrives, and treats silence as a finding rather than as health.

Relations

Where it connects.

  • First Light Receives fromSignals and telemetry arrival
  • Evidence Sends toVisibility transitions as server-observed records
  • Presence Exchanges withKept apart: the page's own view and the server's view
  • Guard Sends toConfirmation that telemetry continues after containment
  • Range Receives fromProof that a lost signal degrades visibility
  • Command Sends toVisibility state and Watchtower's own health
  • Sends to
  • Receives from
  • Exchanges with
  • Outside Sentinel

Failure and health

When it fails, it says so.

In operation

Full coverage

  • Signals arrive on their expected rhythm
  • A scheduled pass every minute

When it fails or loses visibility

Blind spot

  • Silence raised as a server-observed event
  • The cause is reported as unknown, not guessed
  • If Watchtower stops: the answer is marked stale ("Sentinel has not checked recently" is the reserved wording)

Watchtower states

  • Full coverage (lit: in operation)Expected telemetry is arriving on its rhythm.
  • Degraded observationSignals late or partial. The picture is incomplete and marked so.
  • Blind spot (lit: on failure)Expected telemetry has stopped. Not knowing is the finding.
  • Possible suppressionRelated sources going dark in a pattern, rather than as an ordinary outage.

How its own health is verified

  1. A run record for every pass
  2. Only scheduled passes prove the timer is alive
  3. Range: a lost signal must degrade visibility

The Sentinel system family

Ten systems, one institution.

Put Sentinel on guard

Choose the protection level built for where your company is today.

View plansStart with Sentinel