SentraMind

Primer

Prompt DLP is not a network DLP with a new name

A TLS session to an approved AI destination can carry text a network control never sees as a file. Prompt DLP judges that text before submit.

Network controls and prompt controls watch different objects

Network DLP is built around flows, files, and destinations. It can record that a session reached a host, and it can inspect a file a proxy managed to extract. A prompt often matches neither description. The text rides inside a TLS session the organisation has already allowed, and it may never land as a file anyone stored.

The network layer remains necessary beside that gap. Proxy and DNS metadata are the specified input for AI usage observability, and that plane is coming next. Prompt inspection does not retire the proxy. An estate that switched the proxy off because a prompt control existed would leave the observability design with nothing of its own to read.

Judgment is placed before the text is submitted

GenAI Prompt DLP is there to judge the text before submit. The useful moment is the one prior to handoff. A record written after the destination already holds the body documents an exposure that has happened, which is a different control from a block that stops the handoff.

The POC marks GenAI Prompt DLP available for evaluation, and the evaluation runs on the paths that actually reach a verdict. Synthetic text in a demonstration produces a decision about that text and that snapshot. The result is not an incident tally drawn from a live estate, and this page does not invent one. Where a path is still a stand-in, the stand-in keeps its name in the narration.

Approval of the host leaves the body under policy

Allowing a destination means the business has permitted the session. The body inside the session is a later question, and the compiled snapshot still answers it. The same snapshot can log, warn, or block on text sent to a host that is already approved. Host approval and text judgment are sequential, and the second step still runs.

The snapshot can only return an action the precedence allows. The order is exception, then rollout stage, then the rule. Destination approval is not a mute switch that skips that order, and a hallway agreement that never becomes an exception, a stage, or a published rule does not change the action. Operators who want a different outcome change one of those three and publish.

A browser demonstration is not a Windows agent estate

The Windows endpoint agent is absent in this phase. What stands in for fleet inventory is simulated, so the screen does not prove heartbeats or tamper detection on a live host. A browser demonstration can still reach a verdict and show it. The honest name for that path is a POC demonstration with those stand-ins attached.

Coverage stops where the path stops. Desktop clients, IDE plugins, and direct API callers are not intercepted by the browser path. This page also does not treat the demonstration as a binding between a person and a machine certificate. Traffic the browser path never sees is a question for metadata observability, which is still coming next, and for egress controls the estate already runs.

Metadata observability is a separate promise

The observability plane is specified to ingest metadata, not a copy of the prompt. Current demos of volume are fed by a synthetic log generator. A real query over those generated rows still describes a simulated source. Aggregation does not promote the generator into live discovery.

The two planes answer different questions, and the maturity labels keep them apart. Prompt DLP judges text and is available for this evaluation, inside the endpoint limits above. Observability counts destinations from metadata and is coming next. A single sentence that merges them has dropped both the input and the label, and it is the sentence this primer is written to retire.

How to read this

How to read this
Read it asWhich meansDo not read it as
Prompt text inside an allowed TLS session Judged before submit A file the proxy already saw
Approved destination Still subject to log, warn, or block An unmonitored host
Browser demonstration A POC path with named stand-ins A finished Windows agent estate

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

Next in this series

Evidence is ciphertext at rest