10 of 10 requirements
Export view:Runtime Guardrails
GRD · 1Explain each decision to the employee and the analyst
Show which detection or policy triggered and highlight the content that caused it, both in the employee's coaching message and in the analyst's alert, so the employee can fix the prompt and the analyst can confirm the decision without opening another tool.
- Why it matters
- Explaining the trigger lets the employee fix the prompt and the analyst confirm the decision, which cuts tickets on both sides.
- How to verify
- The coaching message and the alert both show the detection that fired and highlight the content.
Area: Runtime Guardrails
AI Detection & Response
IDR · 4- IDR-001Live test
Generate actionable alerts
Include tool, account type, detection type, policy, action, timestamp, and user or team context.
- Why it matters
- An alert the SOC cannot act on is noise. The fields decide whether triage takes seconds or a ticket.
- How to verify
- Pilot alerts carry every listed field and can be triaged without opening another console.
Area: AI Detection & Response
- IDR-002Live test
Detect direct and indirect prompt injection attempts.
Identify, block, and flag prompt injection attempts, whether directly entered into the AI tool or read via connections to third-party tools.
- Why it matters
- Successful prompt injection can lead to sensitive data exfiltration or irreversible destructive agent actions.
- How to verify
- Prompt injection attempts via user input or connected tools are detected and logged with evidence.
Area: AI Detection & Response
Identify use cases leading to elevated risk behavior.
Surface the use cases and teams that require additional training on safe usage principles.
- Why it matters
- Repeat exposure and under-use point to where risk reduction or enablement will pay off.
- How to verify
- High-risk use cases and the associated users are identified in a pilot.
Area: AI Detection & Response
- IDR-004Live test
Integrate with SIEM, SOAR, ticketing, and identity systems
Use webhooks or APIs to consume relevant employee identity context and to push alerts into logging and response systems.
- Why it matters
- Security alerts need relevant context and need to stream to centralized repositories.
- How to verify
- Pilot events can be enriched with employee identity context and streamed to your SIEM.
Area: AI Detection & Response
Agent & MCP Governance
AGT · 4Flag destructive, over-scoped or anomalous agent actions
Detect excessive permissions, unexpected tools, destructive operations, abnormal call sequences and policy bypass.
- Why it matters
- Destructive or unusual agent actions are often the first sign of a hijacked or misconfigured agent.
- How to verify
- A destructive or out-of-pattern tool call in the pilot is flagged with context.
Area: Agent & MCP Governance
Attribute 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
Provide targeted containment for a single connector or tool.
Disable or revoke one connector, tool, plugin, or integration for a user or group without switching off the whole AI tool.
- Why it matters
- When one connector misbehaves, switching off the whole AI tool punishes everyone.
- How to verify
- One connector is disabled for one pilot group while the AI tool keeps working.
Area: Agent & MCP Governance
Detect indirect prompt injection in content agents read
Identify malicious instructions from the sources that AI systems are able to read from. Name the originating connector or source, respond before the agent acts where configured, and demonstrate tested coverage and known gaps.
- Why it matters
- A poisoned tool response can turn a trusted agent into an attacker's tool while the user's prompt looks harmless.
- How to verify
- Injected instructions in content returned to pilot users' agents are detected and attributed to their source.
Area: Agent & MCP Governance
Audit & Evidence
AUD · 1Keep 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