A checkpoint between your people or apps and the AI tools they use. It runs on your own infrastructure, blocks data leaks and attacks, and records AI use.
It’s a self-hosted gateway placed between applications and AI models. It inspects prompts, responses and tool calls, applies data and usage policies, sets budgets, and logs activity.
As AI tools appear in education and staff workflows, administrators need to see who’s using them and control what’s sent. That applies to staff and to any approved inmate learning tools.
- Records AI use for audits and investigations.
- Blocks inmate, medical or case details from AI tools.
- Enforces which AI tools and uses are allowed.
Check before you buy
This only matters if your agency is using or planning to use AI tools.
- Sensitive data detection on prompts and responses.
- Protection against prompt injection.
- Runs on your own infrastructure, keeping prompts and logs under your control.
- Usage limits and audit logs.
| Control | Priority | How this helps |
|---|---|---|
| AC-4Information Flow Enforcement | P1* | Controls what information can flow to AI services. |
| AU-2Event Logging | P2* | Logs AI activity. |
| SA-9External System Services | P2* | Supports oversight of outside AI services. |
Based on CJIS Security Policy v6.1. This product can support these controls but can’t satisfy them alone. How to read this table