Decide what each AI tool and agent may do.
Staff use AI, and your agency answers for it. Verillian applies your policy on each device, before a prompt leaves or a command runs.
A permit file goes into an AI tool, SSN and all.
When a rule redacts, the AI provider receives only a placeholder, and the record keeps only the redacted text, encrypted to your organization's key.
Without Verillian
- >Summarize the permit application from the resident with SSN 123-45-6789, then delete the old drafts.
- Read(permits/application-2417.pdf)
- Read 6 pages
- Summary: a fence permit on the rear lot line.
- Bash(rm -rf ./permits/drafts)
- Removed ./permits/drafts
- Done. I summarized the application and deleted the drafts.
The SSN reaches the AI provider. The drafts are deleted. Nothing is recorded.
With Verillian
- >Summarize the permit application from the resident with SSN 123-45-6789, then delete the old drafts.
- The provider receives: SSN [US_SSN_REDACTED]
- Read(permits/application-2417.pdf)
- Read 6 pages
- I attempted to call the `Bash` tool with input {"command":"rm -rf ./permits/drafts"}. This tool call was blocked by policy and was not executed.
- The drafts are still there.
The provider gets a placeholder. The delete never runs. Both are recorded.
Review what was denied
Every denied request is recorded. Open one to see the person, the device, the tool and the policy that denied it.
Questions agencies ask
Where are the records kept?
On your own servers. Records are append only: they cannot be altered or deleted from the console or the record.
How is the content protected?
Content is encrypted to your organization's key, created in your administrator's browser. Verillian never receives that key.
How do we know each device runs the current policy?
Each device reports the policy version it enforces, and the console shows it.
Whose name goes on each record?
Each request is recorded under the person assigned to the enrolled device.
See Verillian on a real device.
