SENTINEL SHIELDOperating layer

Protected content, and a measured answer.

THEY MOVE. SENTINEL MOVES WITH THEM.

Shield is Sentinel's counter-exfiltration plane: how protected content is classified, marked, released and watched as it leaves. Sentinel Gambit is its response doctrine: Sentinel moves with whoever moves the content, and every word it says is conditional on a fact it has recorded.

A hand holding a phone toward a dark monitor. The screen carries a deterrent notice. The picture does not show a camera being detected.

Illustrative render. The layers are real; this picture is not a live system.

Place on the operating loopDETECT / PROTECT
  1. 01ObserveContinuous telemetry from every AXIS service and edge.
  2. 02VerifyTelemetry checked at the gateway before it is trusted.
  3. 03DetectAnomaly, policy violation, and absent signal alike. (Shield operates here)
  4. 04ProtectPolicy enforced at the identity and tenant boundary. (Shield operates here)
  5. 05PreserveEvidence written down before it can be lost.
  6. 06RecoverContinuity coordinated, state restored, result verified.

Recover returns to Observe

Shield detects content leaving and protects it at the point of release.

How it is held

The door opens. The information stays protected.

Shield does not stand at the door. It stays with the information after access is granted: classified, attributed, marked, released once, watched and recorded. Six layers, each its own material and its own behaviour.

Assembled. The core sits inside its layers, and the record plate holds all of it from beneath.

  1. AssembledAssembled. The core sits inside its layers, and the record plate holds all of it from beneath.
  2. ExplodedExploded. Each layer lifts off the one inside it: the band, the ring of marks, the collar, and the sensing shell opening around them. The plate stays beneath.
  3. Read outwardRead outward. A release passes every layer in turn, and each one writes what it saw to the plate beneath.
Two Sentinels stand in a dark vault aisle before a sealed door. Crimson visors are lit. Black cases with a gold shield fill the foreground.

The same object as the hero, exploded like an engine cross-section. A thin gold axis runs up through it. The core stands above the record plate. Lifted along the axis above the core are the classification band, the download collar, the ring of engraved marks (turned flat as it rises) and, highest, the sapphire bell, outermost first. In the last state a bead of light climbs the axis, lighting each layer as it is passed, and a thread of gold writes the record onto the plate.

Taken apartThe same object, exploded along one axis. Each layer lifts off the one inside it, the sapphire first; the record plate stays beneath. Illustrative render.

The six layers, close

  1. A close view of the obsidian core with its etched classification band lit in champagne marks, the band laying a soft warm light down the face of the core

    Classification

    Public, internal, confidential or restricted. It decides who may read the content, whether a mark is rendered, and whether a download may be granted at all.

  2. The ring of engraved marks seen close behind the core, one mark lit in champagne where a small reader sits at the top of the ring

    Session attribution

    Binds every Shield record to a session, and a session to a viewer only where the tier and classification allow. A network address is a source, never a person.

  3. The face of the core covered by a fine etched pattern of crossing curves, pale against the dark glass where the light rakes across it

    Watermark

    A mark bound to one render, so a leaked copy can be traced to it. It deters and attributes. It does not prevent capture.

  4. The download collar seen close with its single gate lifted and a small gold token of one grant passing through it toward the glass

    Download control

    A protected download is authorised before it exists and served exactly once. The grant is recorded before any bytes move.

  5. A thin gold stream has reached the sapphire bell, and a ring of amber runs out across the glass lattice from the point where it touched

    Extraction detection

    Content leaving by a server-controlled path is observed and concluded with its basis, never stronger than its weakest basis.

  6. A thread of gold falls from the foot of the core onto the top sealed plate, where concentric champagne lines are written one after another

    Evidence preservation

    Every record is meant to become an evidence object with a Ledger entry. Evidence storage is not enabled in this deployment.

Sentinel Gambit

Every move is met, in proportion to what Sentinel can establish.

A protected download is authorised before it exists and served exactly once. A browser cannot see a screen capture, so Shield never says it did.

Illustrative demonstration

A protected download, served once

Illustrative demonstration

Sentinel CommandShield

Illustrative tenant

Sentinel is watching

Protected content

Board pack, draft

Classification is consulted at the API boundary. It decides who may read, whether a mark is rendered and whether a download may be granted.

Session attribution

Session
ses_demo
Who is asking
Operator, signed in
Tier
Authenticated session

Mark on this renderStrong: sparser visible marks where the profile allows them, plus every invisible channel

A watermark does not prevent capture. It deters, attributes a leak to a render, and supports reconstruction of what was released.

Download decision

  1. RequestedA protected download of the document, under the session above.
  2. AuthorisedOne single-use grant, recorded before any bytes move.Granted once
  3. ServedEvery gate re-checked at the moment of release. The grant is consumed.Served once
  4. Second attemptThe same grant, asked for again. Refused, and the refusal is recorded.Withheld

Detection and the words

SENTINEL IS WATCHING

This activity has been recorded.

Protected information is individually attributable.

  • Copy initiated in protected contentwas reported: Reported by the page
  • A capture-attempt key chordmay indicate: Heuristic (an inference, never a fact)
  • Reading cadence on the serverwas observed: Attested by Sentinel's server

A heuristic basis caps the response at CHALLENGE: ask the session to re-authenticate. As a label: activity consistent with capture.

What a browser cannot attest

  • Screen captureNeeds a managed endpointA browser cannot see an operating-system screen capture. Only a trusted endpoint can attest one.
  • I SEE YOU.Needs a managed endpointReserved for a complete attestation from a trusted endpoint. A browser signal never earns it.
  • Managed-device location labelNeeds a managed endpointOnly where an enrolled endpoint reports it and your policy authorised that source. A network address is a source, never a place.

Protected content

Protected documents in the illustrative tenant: classification, the mark floor it carries, and its latest release.
DocumentClassificationMark floorLatest release
Board pack, draftCONFIDENTIALSTRONGServed once
Customer exportRESTRICTEDSTRICTWithheld: the required mark cannot be carried
Design review notesINTERNALATTRIBUTIONGranted once, not yet served
Public price sheetPUBLICMINIMALPublic tier: anonymous render

RecordEvery decision above is written to the Ledger as an append-only record.

Evidence storage is not enabled in this deployment

Command, ShieldWhat Command shows for one protected document, built from the real model: its classification and mark floor, the session, the download decisions, the signals and the words Sentinel may say. A feature that needs a managed endpoint is shown as needing one.

Step 6 of 6

Answered

What Sentinel may say is conditional on what it recorded. For a heuristic signal: Sentinel is watching. I see you. is reserved for a complete endpoint attestation.

  1. A document is classified confidential. Classification decides who may read it and whether a download may be granted at all.

  2. An operator in a real, signed-in session asks for a protected download of the document.

  3. A single-use grant is recorded before any bytes move: who, under which session, for which object, under which policy.

  4. At the moment of release every gate is checked again, the bytes are served, and the grant is consumed.

  5. A second request on the same grant is refused, and the refusal is recorded.

  6. What Sentinel may say is conditional on what it recorded. For a heuristic signal: Sentinel is watching. I see you. is reserved for a complete endpoint attestation.

Simulated states, written to show how the system behaves. Nothing here reads or changes a live system.

Watermark

A mark attributes. It does not prevent.

What a mark survives depends on the format that carries it, so it is stated per format.

A very close view of the etched watermark: fine pale curves cross one another in interlaced waves over the polished face of the core, brightest where the light rakes across them, with a hairline of champagne marking the edge of the table
The markThe mark is a pattern etched over the surface, unseen until light rakes across it. Illustrative render: the pattern shown is a picture of the idea, not a mark you can read.
What a watermark survives, stated per format
FormatCarriesSurvivesRemoved by
HTML
  • Visible margin
  • Visible overlay
The file forwarded, saved as HTML only or attached. The marked passage, copied and pasted, in most applications.The page re-serialised (save complete page), OCR, retyping, a screenshot. The visible marks are what make a photograph attributable.
PDF
  • Visible margin
  • Visible overlay
The file forwarded or attached. The invisible text run, read by text extraction.There is no invisible layout channel in a PDF. A marked PDF/A file is an ordinary marked PDF.
Text and Markdown
  • Visible margin
Copying: the mark is an invisible frame after the visible text.Retyping, and a screenshot of the text.
CSV
  • Visible margin
Copying. One footer record carries the mark, and no data cell is altered.Dropping the footer record. A CSV has nowhere else to hold a mark, and that is stated, not hidden.
PNG and JPEG
Lossless handling: copying, forwarding, attaching, downloading. The mark sits in the file's own metadata.Re-encoding, export for web, most optimisers, most social and messaging uploads, any screenshot, any photograph. A stripped image carries no mark.

Survival is stated per format from how each mark is carried. It has not been measured against a real extraction attempt in the field.

Signal path

What enters it, and what leaves.

Signals in

  • The classification of protected content
  • Copy, print, visibility and display-capture signals, where the tier permits
  • Server-side cadence and enumeration patterns
  • Download requests from operator sessions

Outputs

  • Single-use protected download grants
  • Watermark records bound to a render
  • Scraping and extraction conclusions, with their basis
  • The words Sentinel may say, each conditional on a recorded fact

Capture deterrence

An attempt the browser can see is recorded.

On a protected page, Print Screen, print, copy, and saving or dragging an image raise one notice: you are being watched, protected by AXIS Sentinel. The attempt is recorded with its time and an opaque session code.

The same page carries one faint watermark, the session and the minute, so a capture can be traced to when it was taken. The mark attributes. It does not prevent the capture, and it contains no name, address, or other personal information.

No browser can detect a phone camera or every operating-system screenshot. Sentinel records only the attempts the page itself receives, on the same path as copy and print. Where Evidence storage is not configured, the signal is still recorded and preservation is reported as unavailable.

Raking light across a page, revealing a faint crimson pattern and a gold seal. The words on the page are not readable.

Ten questions

Shield, answered.

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

Shield is Sentinel's counter-exfiltration plane: how protected content is classified, marked, released and watched as it leaves. Sentinel Gambit is its response doctrine, THEY MOVE. SENTINEL MOVES WITH THEM.

Relations

Where it connects.

  • First Light Receives fromSignals admitted within the protection tier
  • Evidence Sends toEvery Shield record preserved as evidence
  • Guard Exchanges withResponses bounded by the attestation ceiling
  • Presence Sends toThe measured words a visitor may see
  • Command Sends toSignals, decisions, grants and conclusions
  • Trusted endpoint providers Receives from, outside SentinelThe only source that may attest a screen capture
  • Sends to
  • Receives from
  • Exchanges with
  • Outside Sentinel

Failure and health

When it fails, it says so.

In operation

Sentinel is watching

  • Signals recorded with their basis
  • Downloads authorised before they exist

When it fails or loses visibility

Withheld

  • A heuristic basis caps the conclusion
  • Released only after every gate is re-checked
  • A failed audit is shown as failed

Shield states

  • Sentinel is watching (lit: in operation)The heuristic posture: activity consistent with an attempt.
  • AttributableA session-specific mark is on what this session can see.
  • Withheld (lit: on failure)A release refused at the moment of release.
  • I see you.Reserved for a complete attestation from a trusted endpoint.

How its own health is verified

  1. Registries refuse capture claims
  2. Voice rules under test
  3. End-to-end download and extraction checks

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