AXIS SENTINEL GUARDCore system

Policy, enforced at the boundary.

NOTHING CROSSES THE BOUNDARY WITHOUT AUTHORITY.

Guard is Sentinel's governed authorization and containment system. Every request passes identity, scope, policy and authority before a decision is made, and the strength of what Sentinel actually witnessed sets a ceiling on how hard it may respond.

A Sentinel standing in a rain-lit corridor before a steel door whose lock burns crimson.
Place on the operating loopPROTECT
  1. 01ObserveContinuous telemetry from every service and edge you connect.
  2. 02VerifyTelemetry checked at the gateway before it is trusted.
  3. 03DetectAnomaly, policy violation, and absent signal alike.
  4. 04ProtectPolicy enforced at the identity and tenant boundary. (Guard operates here)
  5. 05PreserveEvidence written down before it can be lost.
  6. 06RecoverContinuity coordinated, state restored, result verified.

Recover returns to Observe

Guard is where the loop acts: policy enforced at the identity, tenant and workspace boundary.

Doctrine

Four sentences, each enforced at a station.

They are Guard's own words, and each one is a check a request must pass. A station can narrow a request, hold it for proof, or end it.

  1. 03 PolicySecurity is active, continuous and policy-driven.
  2. 01 IdentityNothing crosses without identity.
  3. 02 ScopeNothing acts without scope.
  4. 04 AuthorityNothing escalates without authority.

The decision

Every request passes the same five stations.

Identity, scope, policy, authority, then a decision. Choose a request to see the record Guard writes for it, and where its path narrows, waits or ends. There are six decisions and no two share a shape.

Illustrative demonstration

Choose a request

The request

Allowed: Operator session

Add a note to an open incident in its own tenant.

  1. IdentityWho is asking?Who is askingOperator, signed inPassedThe session resolves to an authenticated operator, once, when it is loaded.
  2. ScopeWithin which boundary?Tenant and siteOwn tenant, from membershipPassedThe tenant comes from the operator's membership, never from the request.
  3. PolicyIs it permitted?PolicyIncident note, within the rolePassedAn incident note is within the role, and stays available under Safe Mode.
  4. AuthorityWho stands behind it?How it is known, and who authorized itRole is sufficientPassedThe role is sufficient. No elevation is asked for.
  5. DecisionWhat happens?DecisionAllowedAllowedAdmitted as asked. The note is written together with its audit entry, in one batch.

AllowedIdentity, scope, policy and authority all held.

Simulated requests, written to show how Guard decides. Nothing here reads or changes a live system.

Guard decision recordWho asked, within which scope, under which policy, with whose authority, and what was decided: the five facts every decision carries, each beside the column of the record it comes from.

The authority ceiling

Guard's autonomy is bounded by what Sentinel can prove.

The strength of the evidence sets how hard Guard may respond without a person. Repetition never raises it: reports from a page are still one page's opinion.

  1. BlockA named person
  2. Revoke sessionA named person
  3. RestrictNot built
  4. ThrottleA named person
  5. ChallengeGuard may
  6. ObserveGuard may

The column is Guard's authority ladder. A ring of light, the ceiling, lies at the highest response Guard may take without a person for the evidence it holds. Plates at or below it are lit champagne; plates above it keep a cool platinum line, because only a named person may take them. Reported or inferred: the ceiling lies at challenge. Reported again and again: points of light rise toward the ceiling and are absorbed at it, and it does not move. Server observed: the ceiling rises one rung, to throttle. Edge observed: the ring is dashed and the plates are ghosts, because no edge attestation path exists.

Reported or inferred. A site's agent said so, or Sentinel inferred it. Guard may observe and challenge on its own; anything above the ceiling waits for a named person.

  1. Reported or inferredReported or inferred. A site's agent said so, or Sentinel inferred it. Guard may observe and challenge on its own; anything above the ceiling waits for a named person.
  2. Reported, repeatedReported again and again. Repetition never raises the ceiling: reports from a page are still one page's opinion.
  3. Server observedServer observed. Sentinel witnessed it itself, so the ceiling rises one rung, to throttle. Throttle is in policy, but no provider can enact it today.
  4. Edge observedEdge observed. An edge could prove it cryptographically and the ceiling would reach block. No edge attestation path exists, so this level is not built.
  1. ObserveBuiltRecording what was seen. Always available.
  2. ChallengeBuiltAsks a source to prove itself once. Recoverable, and bounds who may pass.
  3. ThrottleBuilt, limitedIn policy, but no provider can enact a true throttle today. The adapter refuses rather than substitute a challenge.
  4. RestrictNot builtNo application integration exists to act through.
  5. Revoke sessionBuilt, limitedBy a named commander, on a Sentinel console session. A session on a protected site is out of reach.
  6. BlockBuilt, limitedAutonomous block needs edge attestation, which is not built. A commander may block one address for a limited time, through a provider.

Beyond the ceiling, a person

  1. Guard

    Within the ceiling

    • Challenge a source on inferred or site-reported evidence.
    • Throttle on server-observed evidence, in policy, where a provider can enact it.
    • Refuse what cannot be evaluated.
  2. Commander

    A named person

    • Revoke a Sentinel console session.
    • Contain one address, with an expiry, through a provider.
    • Engage Safe Mode at a site, a deployment or an incident.
  3. Owner

    A named owner

    • A permanent rule, a range of addresses or a tenant-wide rule.
    • Override the allowlist.
    • Engage Safe Mode across the tenant, or rotate a provider credential.

The allowlist is checked before authority, so an owner's own monitoring is never contained. A request above a role's reach is refused before any provider is touched.

Every response at every strength of evidence

Evidence Sentinel holds

  1. Block
    • Inferred: A person
    • Site reported: A person
    • Server observed: A person
    • Edge observed: Not built
  2. Revoke session
    • Inferred: A person
    • Site reported: A person
    • Server observed: A person
    • Edge observed: Not built
  3. Restrict
    • Inferred: A person
    • Site reported: A person
    • Server observed: A person
    • Edge observed: Not built
  4. Throttle
    • Inferred: A person
    • Site reported: A person
    • Server observed: Guard mayceiling
    • Edge observed: Not built
  5. Challenge
    • Inferred: Guard mayceiling
    • Site reported: Guard mayceiling
    • Server observed: Guard may
    • Edge observed: Not built
  6. Observe
    • Inferred: Guard may
    • Site reported: Guard may
    • Server observed: Guard may
    • Edge observed: Guard may

The ceiling for site reported evidence

Site reported evidence may justify at most a challenge without a person. Throttle and everything above it needs a named person.

Governed containment

A path narrows. It does not snap shut.

One credential anomaly, followed from the first decision to the operator's view. Each step is marked with what the repository does today, because a demonstration must not imply more than exists.

Illustrative demonstration

Credential anomaly, contained

Inside the row of gates, close to one whose iris has narrowed to a small aperture. Large brushed titanium blades fill the frame, and a ring of amber-gold light is held in the opening.A machined titanium gate seen from the side, its iris closed to a set of brushed blades meeting at the centre. A single thin line of crimson runs round the inner lip, and a dimmed ring of gold light rests against the closed blades.Five machined titanium gates stand in a row on a rail, seen at a low angle from the entrance side, the nearest on the right and the others receding to the left. Their irises are open, the decision plate at the far end glows champagne, and all of it is reflected in the polished floor.
The openingThe path narrows around a request held at scope.The closeThe gate comes to rest, closed, and says so once.The recordEvery decision is written, telemetry continues, and the incident reads contained.

In the repository today

Partly built

First Light admits and attests every observation, and Guard reads how strongly it is known. Automated credential-anomaly detection is not claimed: an operator declares the incident, and the credential-compromise playbook recommends the sequence.

Partly built

Tenant isolation is enforced in every read and write. Holding one session short of revoking it, the Restrict rung, has no application integration today.

Built, by a person

An owner lowers a member's role. Under Safe Mode that needs a fresh password confirmation, so a stolen owner session cannot strip the real administrators.

Built, by a person

A commander revokes a Sentinel console session, effective at its next request. A session on a protected site is out of reach: that needs an application integration that does not exist.

Built, provider confirms

A commander requests a rule through the provider. It reads pending until the provider confirms, and failed if it does not. Optional per deployment, tested against real request shapes, not yet exercised against a live account.

Built

A decision and the action it authorised commit in one batch, so neither exists without the other. Preserving the surrounding evidence is a commander's action.

Built

Watchtower runs every minute, whether or not anyone has Command open. Guard does not call it: the confirmation is Watchtower's own next pass. Silence would be raised as lost visibility, not read as calm.

Built

Command reads the incident's status (active, contained, closed), the rule's state and the authority behind each action. This page is a demonstration, not a live console.

Step 8 of 8

Command shows containment

The incident reads contained, the rule reads confirmed, and each action names the authority it required. A person sees, understands, authorizes, acts and verifies.

  1. A privileged credential is used from a source its session has never used. The observation is admitted with how it is known: site reported, server observed or inferred.

  2. The affected session can reach only its own tenant. Guard does not widen it, and a request across the boundary is answered as not found.

  3. The role is lowered. The session keeps read access to what it already held; write and privileged operations leave its reach.

  4. The session's token is revoked and stops working at its next request. The decision is Revoked, and it records who decided and why.

  5. The paths the session could use sideways close. Containment of the source is requested, and a path is shown closed only when it is confirmed.

  6. Every decision so far is already in the Ledger, written in the same batch as the change, with its justification attached.

  7. Containment must not blind Sentinel. Watchtower's next scheduled pass reads the reports again, and telemetry from the contained scope is still arriving.

  8. The incident reads contained, the rule reads confirmed, and each action names the authority it required. A person sees, understands, authorizes, acts and verifies.

Simulated states, written to show how Guard contains. Nothing here reads or changes a live system. The order follows the story: the repository's credential-compromise playbook recommends preserving evidence before anything is rotated or revoked.

Each step against the repository
  1. Credential anomaly detectedPartly builtFirst Light admits and attests every observation, and Guard reads how strongly it is known. Automated credential-anomaly detection is not claimed: an operator declares the incident, and the credential-compromise playbook recommends the sequence.
  2. Session isolatedPartly builtTenant isolation is enforced in every read and write. Holding one session short of revoking it, the Restrict rung, has no application integration today.
  3. Privilege narrowedBuilt, by a personAn owner lowers a member's role. Under Safe Mode that needs a fresh password confirmation, so a stolen owner session cannot strip the real administrators.
  4. Token revokedBuilt, by a personA commander revokes a Sentinel console session, effective at its next request. A session on a protected site is out of reach: that needs an application integration that does not exist.
  5. Lateral path closesBuilt, provider confirmsA commander requests a rule through the provider. It reads pending until the provider confirms, and failed if it does not. Optional per deployment, tested against real request shapes, not yet exercised against a live account.
  6. Event preservedBuiltA decision and the action it authorised commit in one batch, so neither exists without the other. Preserving the surrounding evidence is a commander's action.
  7. Watchtower confirms telemetry remainsBuiltWatchtower runs every minute, whether or not anyone has Command open. Guard does not call it: the confirmation is Watchtower's own next pass. Silence would be raised as lost visibility, not read as calm.
  8. Command shows containmentBuiltCommand reads the incident's status (active, contained, closed), the rule's state and the authority behind each action. This page is a demonstration, not a live console.

Signal path

What enters it, and what leaves.

Signals in

  • Attested observations admitted by First Light
  • Operator sessions, roles and tenant membership
  • Policy, the owner's allowlist and Safe Mode scope
  • Provider confirmations of network rules

GuardPROTECT

Outputs

  • A decision for each request: allowed, constrained, challenged, revoked, contained or refused
  • Containment requests to a network provider
  • A Ledger entry for every decision, written with the change
  • Containment state for Command

Ten questions

Guard, answered.

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

Guard is Sentinel's enforcement system: it decides what an identity, a session or a workload may do at the boundary, and records each decision as it makes it.

  • A governed authorization and containment system, not a firewall.
  • Every decision carries its justification into the Ledger.

Relations

Where it connects.

  1. Receives fromFirst LightAttested observations; the attestation bounds the response
  2. Sends toEvidenceEvery decision and containment, recorded in the same write
  3. Receives fromWatchtowerConfirmation that telemetry continues after containment
  4. Exchanges withSafe ModeHigh-risk operations held within the engaged scope
  5. Receives fromRangeRevocation, isolation and provider-failure scenarios
  6. Sends toCommandDecisions, containment state and the authority each required
  7. Exchanges with, outside SentinelNetwork providerRule requests out; confirmation or refusal back

Failure and health

When it fails, it says so.

In operation

Enforcing

  • Every request evaluated on the request path
  • Rules active only on provider confirmation

When it fails or loses visibility

Fails closed

  • A decision that cannot be evaluated is refused
  • Unreachable provider: rule failed, never active
  • A rule the provider keeps stays shown as enforced

Guard states

  • AllowedIdentity, scope, policy and authority all held.
  • ConstrainedAdmitted with a narrower scope than requested.
  • ChallengedAsked to prove itself before it may continue.
  • RevokedA session or credential withdrawn.
  • ContainedSpread halted at the boundary. Not yet resolved.
  • RefusedNot admitted. The refusal is recorded.
  • Enforcing (lit: in operation)
  • Fails closed (lit: on failure)

How its own health is verified

  1. Range: revocation, isolation, policy tightening, provider failure
  2. Provider state read back, not assumed
  3. A failed blocking scenario blocks the release

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