PatientLock

Discovery field

Cloud clientsLocal runtimesCoding toolsAgent frameworks

AI discovery + governance

ShadowAI

AI discovery, governance + evidence

Which AI tools are present, who is using them, how do they fit policy, and what evidence supports the decision?

ShadowAI finds AI clients and developer tooling from endpoint software evidence, ties those findings to device, identity, and policy context, and keeps discovery separate from any approved remediation.

01

Discover

02

Classify

03

Evaluate

04

Govern

05

Re-observe

06

Prove

How ShadowAI runs

Review detected AI tools against your policy.

Discovery, policy, action, and closure stay separate so the evidence remains clear.

01

Reads AI-client matches from endpoint package inventory and creates organization-specific findings.

02

Keeps policy decisions separate from how a tool is deployed and where its data goes, so local models, managed clients, and cloud clients are not treated as the same thing.

03

Carries policy and remediation information forward without implying that every detected tool can be removed automatically.

04

After remediation, requires fresh endpoint and ShadowAI evidence before closure. A command receipt alone is not enough.

Evidence Continuity

What becomes evidence.

Evidence Continuity keeps the evidence behind the AI finding, the policy decision, any approved action, and the state observed afterward.

Permissions and limits

What stays under customer control.

ShadowAI can detect supported AI clients and keep durable findings. Removal or blocking requires a supported correction path and customer permission. A finding does not by itself change Risk Compression Engine state or create an insurance-impact projection.