SentraMind

Feature

GenAI Prompt DLP, inside the current POC boundary

What the Sentry evaluation covers today, which endpoint paths are stand-ins, and what a buyer should not infer from a browser demo.

The boundary is two sets of paths

GenAI Prompt DLP is available for a POC evaluation, under the name Sentry on the crew pages. The boundary of that evaluation is the set of paths that reach a verdict, plus the set that are still stand-ins. A briefing that mentions only the first set has described a different product than the one under evaluation.

The deterministic detectors behind a verdict are real and replayable: national identifiers for the five markets, payment numbers, and secrets, under the policy snapshot. The action is the snapshot’s action. A detector names a class of text. When the snapshot’s action is log-only, the match is recorded and the request continues. That split is the POC boundary in a single decision.

What the browser path actually shows

The browser extension reaches the verdict service through a loopback relay that holds a leaf from the software machine CA. The actor is stored as unattributed, because there is no client token binding the person to the call. A rule that would warn and then ask the person to confirm is clamped to a hard block on this path. Both facts belong on the evaluation note next to any blocked paste in the demonstration.

Enforcement here is demonstrated on a synthetic site. The coverage-matrix wording for the path is renderer-assisted. The network backstop applies when the extension is force-installed, and the published comparison is that this is weaker than the enterprise connector path. Paste, drag, attach, and print through that connector are not what this build proves. A worker-hosted socket is a further named gap. A demo that collapses all of those into “the browser is covered” has left the record.

Callers the extension never sees

Desktop clients, editor plugins, and direct API callers are not intercepted by the extension. If that traffic is visible in this POC, it is visible as metadata in the AI-usage pipeline, fed here by a synthetic log source, so the mechanism can be shown and the volumes cannot. Where such traffic is blocked, the block is an egress control the organisation operates.

The endpoint inventory that might sit beside a prompt story is a simulated fleet. Heartbeats and tamper detection on a live host are outside what that fleet can prove. An evaluation can still run the synthetic prompts, inspect the verdict, and read the evidence envelope. It says, in the result, which of those sentences the fleet did not support.

A blocked sample is not an incident count

A blocked paste in a demonstration is evidence about that synthetic prompt, that snapshot, and that path. It can be repeated. It can be shown to change when the snapshot changes, which is the property that makes the control plane worth testing. It is not a count of incidents stopped for any organisation, ministry, or sector, because no such count has been collected.

The same restraint applies to quality. No precision or recall on a real corpus is published for these detectors, and the encoder stand-in adds no quality figure. Mixed-language prompts are ordinary input in this region, and they are unmeasured too. The accurate sentence is that the prompt matched, or did not, under the rules that were loaded.

Policy remains the decision

The snapshot is versioned. Changing it writes a new version and moves a pointer, and both the viewer and the verdict path read the active one. An evaluation that wants to see the boundary should change a rule, replay the same prompt, and watch the action change. A viewer-only edit that leaves enforcement alone would be a defect.

Generative models stay off this path. If a sentence in the briefing needs one to explain a block, the sentence is about a different design. The block the POC can show comes from a deterministic match and a rule. The limit, the stand-in label, and the synthetic input sit in the same paragraph as that block.

How to read this

How to read this
Read it asWhich meansDo not read it as
In the POC Paths that reach a real verdict Every endpoint story on the page
Named stand-ins Extension limits stay in the limitations record A count of incidents stopped
Who decides The policy snapshot The detector, when the snapshot says log

Product statements on this page follow the POC maturity ladder. A coming-next or roadmap item is not available for the current evaluation.