Fast Start
What you will have in minutes
A locally running, ECZ-ID-backed agent scaffold with resolver-verifiable identity hooks, a credential manifest, and Resolver verification ready to run.
What you do first — in order
What comes back from TrustOps
- Agent ECZ-ID(s)
- Credential manifest (JSON, discovery only)
- API keys issued in TrustOps
Success looks like
Resolver returns a resolver-verifiable state for your Agent ECZ-ID. You can share it with any party without an account.
1What This Kit Builds
An operations monitoring and incident response agent with resolver-verifiable identity chains at every decision point. This agent detects anomalies, coordinates incident response, manages escalation workflows, and produces identity-anchored post-incident reports.
2Who It Is For
Operations teams, SREs, and developers building automated incident response systems. Ideal for organisations running critical infrastructure where every response action must be traceable to a resolver-verifiable identity.
3Why ECZ-ID Matters Here
During incidents, multiple agents and humans take actions under time pressure. Without resolver-verifiable identity, post-incident review becomes forensic guesswork. ECZ-ID ensures every action in the response chain carries resolver-verifiable identity.
4Architecture
Anomaly Detection Interface
Integrates with monitoring systems to detect operational anomalies with identity context.
Incident Coordinator
Manages incident lifecycle from detection through resolution with resolver-verifiable identity at every step.
Escalation Engine
Identity-aware escalation routing that maintains provenance through every escalation level.
Response Chain Tracker
Tracks every action taken during incident response with identity-anchored provenance.
Alert Router
Routes alerts with resolver-verifiable identity context to appropriate responders and systems.
Post-Incident Reporter
Generates comprehensive post-incident reports with complete identity-anchored action logs.
5Build Steps Overview
Trust Map
Required Passports
Recommended Passports
Relevant Packages
What Each Enables
6TrustOps Credentialing Checkpoint
TrustOps Credentialing Checkpoint
Pause here to acquire your required ECZ-ID trust objects
This is a designed pause point in your build process. Before continuing, you need to acquire the required ECZ-ID passports and credentials from TrustOps. This midpoint credentialing approach ensures your agent is built with resolver-verifiable identity from the start—not bolted on after the fact.
Required Passports
- ECZ-ID Business Passport
- Agent Credential
Recommended Passports
- Cyber Resilience Passport
- IoT Device Passport
- Risk & Policy Passport
Relevant Packages
What You Must Acquire in TrustOps
What You Bring Back from TrustOps
9Return and Complete Integration
With your TrustOps credentials in hand, return here to complete the final build steps.
10Verify Through Resolver
Verify agent identity
Query the operations agent’s ECZ-ID through Resolver.
Trace incident response
Follow a complete incident response through Resolver, verifying identity at each action.
Verify escalation chains
Confirm every escalation carried correct identity context.
Audit post-incident report
Verify the complete post-incident report through Resolver.
11Deploy Into Your Environment
ECZ-ID-backed agents are portable. Your resolver-verifiable identity travels with your agent regardless of deployment target after TrustOps and Resolver checks. No vendor lock-in.
12Limits & Non-Claims
- This kit does not provision credentials. All credentialing happens through TrustOps.
- This kit does not replace your monitoring stack. It integrates with existing monitoring systems.
- Incident detection quality depends on monitoring source quality and configuration.
- Response actions are logged and verified but not automatically executed without configuration.
- Post-incident reports are as complete as the identity hooks configured.
Ready to Build This Agent?
Start with the build steps above, credential through TrustOps, and deploy your resolver-verifiable agent anywhere.