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.

Illustrative render. The layers are real; this picture is not a live system.
- 01ObserveContinuous telemetry from every AXIS service and edge.
- 02VerifyTelemetry checked at the gateway before it is trusted.
- 03DetectAnomaly, policy violation, and absent signal alike. (Shield operates here)
- 04ProtectPolicy enforced at the identity and tenant boundary. (Shield operates here)
- 05PreserveEvidence written down before it can be lost.
- 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.
- AssembledAssembled. The core sits inside its layers, and the record plate holds all of it from beneath.
- 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.
- Read outwardRead outward. A release passes every layer in turn, and each one writes what it saw to the plate beneath.


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.
The six layers, close

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.

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.

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.

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

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

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
Sentinel CommandShield
Illustrative tenant
Sentinel is watchingProtected 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.
Mark floor for this classification: STRONG
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
- RequestedA protected download of the document, under the session above.
- AuthorisedOne single-use grant, recorded before any bytes move.Granted once
- ServedEvery gate re-checked at the moment of release. The grant is consumed.Served once
- 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
| Document | Classification | Mark floor | Latest release |
|---|---|---|---|
| Board pack, draft | CONFIDENTIAL | STRONG | Served once |
| Customer export | RESTRICTED | STRICT | Withheld: the required mark cannot be carried |
| Design review notes | INTERNAL | ATTRIBUTION | Granted once, not yet served |
| Public price sheet | PUBLIC | MINIMAL | Public tier: anonymous render |
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.
A document is classified confidential. Classification decides who may read it and whether a download may be granted at all.
An operator in a real, signed-in session asks for a protected download of the document.
A single-use grant is recorded before any bytes move: who, under which session, for which object, under which policy.
At the moment of release every gate is checked again, the bytes are served, and the grant is consumed.
A second request on the same grant is refused, and the refusal is recorded.
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.

| Format | Carries | Survives | Removed by |
|---|---|---|---|
| HTML |
| 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. |
| 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 |
| Copying: the mark is an invisible frame after the visible text. | Retyping, and a screenshot of the text. |
| CSV |
| 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.

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.
Protected content and the routes it can leave by.
- Classification and protected downloads
- Copy and print within protected content
- Scraping and extraction patterns
- Session attribution
Copy and print initiated in protected content where the tier permits collecting it, visibility changes, page-initiated display capture, server-side cadence and enumeration patterns, and download requests.
How strong a conclusion may be, never stronger than its weakest basis; whether a protected download is authorised at the moment of release; and which words Sentinel may say, each conditional on a recorded fact.
Authorise a protected download to a real operator session and serve it exactly once, bind a watermark to a render so a leaked artefact can be traced to it, record copy, print and extraction as evidence, and say plainly: SENTINEL IS WATCHING.
A browser cannot see an operating-system screen capture, so Shield never claims to have detected one.
- I SEE YOU. is reserved for a complete attestation from a trusted endpoint provider.
- A watermark attributes. It does not prevent.
- A network address is a source, never a person's location.
Shield signals and decisions, watermark renders, protected download grants and their consumption, and scraping and extraction conclusions with their basis: read views of what Shield already recorded.
Shield's signals enter through First Light within the protection tier, its records are preserved by Evidence, its responses are bounded by Guard's attestation ceiling, and its words reach a visitor only through Presence.
It withholds rather than overstates. A heuristic basis caps the conclusion whatever sits beside it, a download is released only after every gate is re-checked, and a failed audit is shown as failed.
A contract test walks every event registry for forbidden capture claims, the voice rules are pure functions under test, and end-to-end checks cover downloads, copy and print, and extraction.
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
- Registries refuse capture claims
- Voice rules under test
- 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.
