SentryWatch

Know whether the live system holds.

Sentry assesses supplied public surfaces and verified connected configuration. It ties each judgment to the evidence in scope and reopens it when that evidence or the system changes.

The repository is not the system serving users.

Production security lives in the combination of code, identity, infrastructure, provider configuration, data policy, exposed interfaces, and the release that joined them together.

An external probe can guess at part of that state. A checklist can compare settings to generic advice. Neither tells you whether this specific deployed system preserves the security properties it depends on.

Release and configurationThe exact code and settings serving users now
Intent and observed stateWhether deployed controls still preserve the design
Change and consequenceWhat moved and which security judgment must reopen

A posture assessment grounded in observed state.

Sentry binds the supplied surfaces, connected services, and controls in scope. Public observations and connected provider state remain separate evidence sources, with their limits and freshness visible.

The result is a bounded assessment: what the available evidence supports, what remains unknown, and which changes should reopen the question. Connected assessment reads configuration; it does not change your infrastructure.

Sentry / illustrative posture assessmentIntended workflow

Illustrative example. Shows the intended workflow, not a final product screen or a recorded run.

Control question

Does the supplied administrative surface enforce the intended access restriction?

Observed state

Release
Named application deployment
Identity
User and administrative providers
Data plane
Database, storage, and service policy
Exposure
Domains, routes, and public interfaces

Assessment

In this example, the supplied administrative surface is reachable publicly and its connected provider policy permits access beyond the intended group.

Evidence

The public reachability observation and connected access policy support this control-level judgment. They do not establish the security of the application as a whole.

Reopen when

Identity roles change · a new public route appears · provider policy changes · the release moves the authoritative boundary

Carry security understanding across every material change.

Sentry does not restart from a generic baseline on every run. It maintains the relationship between intended security properties, observed production state, and the changes that can invalidate prior judgment.

  1. 01Start with a URL

    Supply a public URL and the authorized scope to assess what is visible from outside.

  2. 02Connect for deeper evidence

    Add read-only provider connections to assess configuration beyond what public observation can establish.

  3. 03Review the assessment

    Review findings, unknowns, freshness, and coverage limits. Public observations and connected evidence remain distinct.

  4. 04Watch material change

    Reopen only the judgments affected by a new release, configuration shift, or changed threat condition.

At releaseAssess the supplied surfaces and connected controls.
After changeIdentify which prior judgments are invalidated.
Over timeKeep posture tied to current evidence.

Three products. One security model carried forward.

01 / ShapeArchitect

Shape security-sensitive decisions while building.

 02 / InvestigateScanner

Investigate system-level risk across the codebase.

 03 / WatchSentry

Watch deployed posture as the system changes.

Know what is true now.

Maintain an evidence-backed view of deployed posture as the system changes.