7 of 7 requirements
Export view:Support the AI tool approval and review lifecycle
Define and track unapproved versus approved AI tools and MCP servers.
- Why it matters
- Without a governed approval path, teams route around the control.
- How to verify
- Walk a tool or MCP server request from intake to a recorded decision.
Area: AI Security Posture Management
Runtime Guardrails
GRD · 1Turn acceptable-use policy into enforceable scenarios
Express AUP rules as policies and demonstrate enforcement.
- Why it matters
- An acceptable-use policy only matters if it can be enforced and shown to be enforced.
- How to verify
- Three clauses from your AUP are expressed as policies and successfully tested in your pilot.
Area: Runtime Guardrails
Agent & MCP Governance
AGT · 1Attribute every connector and tool call alert to a person
Answer which server and tool were called, by whom, using which identity, every time an alert or intervention fires.
- Why it matters
- Without attribution, an agent action cannot be investigated or tied to accountability.
- How to verify
- Every pilot tool call alert shows the tool used, the surface, the user identity, and the result.
Area: Agent & MCP Governance
Audit & Evidence
AUD · 3Keep a configurable record of each conversation
Record the prompts, responses, uploaded files and tool calls that make up each conversation, with content capture set per policy: full, partial, metadata-only or none, in line with privacy and retention rules.
- Why it matters
- The conversation, not the single prompt, is the unit an investigator or auditor needs to see.
- How to verify
- Show one pilot conversation's record at full, partial and metadata-only capture settings.
Area: Audit & Evidence
- AUD-002Walkthrough
Export audit and forensic evidence
API, CSV, webhook or evidence package suitable for audit and incident response use.
- Why it matters
- Evidence has to leave the console in a form legal, HR and auditors can use.
- How to verify
- Export an evidence package for one pilot incident.
Area: Audit & Evidence
Restrict and audit access to raw prompt content
Provide RBAC controls over who can read full prompt content, and record each access to it.
- Why it matters
- Raw prompts are among the most sensitive data the control holds, so access must be limited and logged.
- How to verify
- Only an authorized role can open full prompt content, and each access is recorded.
Area: Audit & Evidence
Separate administrative roles, and authenticate them through enterprise SSO
Separate policy, approval, administration, investigation and exception duties; authenticate administrators through enterprise SSO; apply least-privilege roles over policy, alerts, raw prompts, exports and dashboards; and record administrative and investigative actions.
- Why it matters
- Whoever can change policy or read prompts holds a lot of power, so roles must be separated and every action recorded.
- How to verify
- Show separate policy, investigation and exception roles, SSO login and the record of an admin action.
Area: Platform, Privacy & Assurance