Agent Secrets Vault

Give agents capabilities, not reusable secrets.

Priority: P1
Phase: Phase 2
Primary owner: Security Eng / Platform
Status: Blueprint

Objective

The safest secret is one the model never sees. Agent Trust Cloud should broker privileged actions so an agent can request an operation without receiving the underlying API key, password or signing secret. This lowers credential leakage risk and makes revocation easier.

What to build

Store or integrate with secret managers for API keys, database credentials, certificates and signing material.
Broker calls using server-side credentials after identity/policy approval.
Issue short-lived scoped credentials when direct tool access is required.
Detect secrets accidentally placed in prompts, memory or logs.

Implementation decisions

Prefer integration with CyberArk, Azure Key Vault, AWS Secrets Manager, Google Secret Manager and HashiCorp Vault over duplicating enterprise vaults.
Encrypt secrets separately from general application data.
Never log raw secret values; redact at ingestion and egress.
Rotate or revoke compromised credentials through connector workflows.

Definition of done

High-risk demo proves a model cannot retrieve the raw secret used for a brokered transaction.
Every secret use maps to agent identity, action and resource.
Secret rotation does not require redeploying every agent when brokered access is used.

Success metrics

Brokered-action percentage
Static secret reduction
Secret exposure detections
Credential rotation time

DESIGN GOAL

Give agents capabilities, not reusable secrets.

This control is specified on page 20 of the blueprint.