Incident Management
Contains a misbehaving agent immediately — revoke its mandate, fail closed, and keep the signed record.
What it does
Incident Management contains a misbehaving agent immediately: revoke its mandate to strip its authority, fail closed so anything it attempts is blocked, and route open questions to the escalation queue. Every containment action leaves the same signed, anchored evidence, so the incident is reviewable after the fact.
Inside Incident Management
The core functions this engine provides across the Trust Fabric.
Incident Management composes with the Trust Fabric
Every engine is independently useful and interoperates through one API-first Trust Fabric — so identity, evidence, policy, risk and certification stay consistent across your AI estate.
Related engines
Event Fabric
The signal backbone — verification and status webhooks, escalation polling and evidence-flush events.
- Verification / contact webhooks
- Escalation status polling
- Evidence batch flush
- Real-time trust signals
Security Architecture
Security-by-design: signed, fail-closed, PII encrypted at rest, only commitments on-chain, and quantum-resistant channels.
- Ed25519 + hybrid post-quantum
- Encryption at rest (AES-256-GCM)
- On-chain commitments, not PII
- Fail-closed by default
Deployment Architecture
Runs on Hedera (testnet or mainnet), self-hostable, with configurable, sovereign HCS topics.
- Hedera testnet / mainnet
- Self-hostable / sovereign
- Configurable HCS topics
- Cloud / on-prem / federated
See Incident Management in action
Book a demo and see how the platform establishes trust across your AI systems.