Govern the shadow-AI paths RedactWall can measure.
Nobody files a ticket before trying an assistant. It arrives in a browser tab, in a vendor’s new feature, or in a script somebody wrote over a weekend.
What happens in an ordinary week
A support rep submits a customer note on a supported AI site
The measured submission action is governed at send; Disclosures names origins whose pre-submit or typeahead behavior is leaking or not proven.
A transformation-required value appears in the Windows text clipboard
The exact current generation can be replaced or cleared; the agent does not identify where it may be pasted or prove another application did not read it first.
A vendor’s internal tool is configured to route through RedactWall
Requests and responses on that route are checked before forwarding.
The IT director reviews AI application signals from enrolled machines
Installed, declared, seen-running and tool-ran states remain distinct; only tool-ran is positive evidence of use.
What covers it
The coverage table states what each surface does, and Disclosures how far each one is proven today.
Stop the leak. Not the work.
These workflows describe the broader product. The proposed first pilot covers ChatGPT text in managed Chrome and a separately verified Anthropic gateway path.
- Pilot starts with one governed path
- Coverage follows the path you deploy
- Evidence states what it does not prove