Agent Identity & Security
How does Catalyst handle tool authorization for agents running in air-gapped environments where external identity providers are unavailable?
Catalyst supports offline identity provisioning via pre-configured workload identity certificates and local policy files. In air-gapped setups, you define tool authorization policies as YAML or JSON files that are loaded into Catalyst’s local policy engine. These policies are immutable once deployed, preventing tampering. Catalyst still enforces identity-based authorization and logs all tool calls locally, which can be exported for audit when connectivity is restored.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Agent Identity & Security
What is a workload identity for an AI agent and why can't I just use a shared API key?
Explains workload identity for AI agents and the security limits of shared API keys in production.
- Agent Identity & Security
How does Catalyst assign a workload identity to an agent runner like LangGraph or CrewAI?
Describes how Catalyst injects workload identities into framework-agnostic agent runners.
- Agent Identity & Security
What security problems do shared API keys cause when multiple agents run in production?
Lists security problems from shared API keys in multi-agent production environments.