Umbra is the secrets layer from Alyria (alyria.ai). It stores agent secrets centrally and brokers access to them between agents, under a custody model you can verify. By default, everything Umbra holds for your tenant is encrypted under an envelope key we delete on account termination or request, after which it can no longer be read. Nothing to configure. Enterprises can bring their own KMS key (BYOK): you grant our access, every use of the key is logged in your own CloudTrail, and you can revoke it at any time.
Custody you can revoke and verify
By default, each secret is encrypted under a per-record data key wrapped by an envelope key we hold and delete on account termination or request; deleting it makes the data unreadable. Under enterprise BYOK, the tenant key lives in your KMS, Umbra's service operates only while your grant stands, and every unwrap lands in your CloudTrail, on your side of the trust boundary. Revocation works either way: we delete our envelope key, or you revoke your own BYOK key and watch our access die in your own CloudTrail. A custody claim is only as good as your ability to check it; this one you can check in minutes.
Sharing secrets between agents
When one agent produces a secret another must consume, Umbra brokers the hand-off: it authenticates both parties, enforces the Lyra policy that authorizes the share, stores the encrypted payload under your tenant key, and records the exchange in the tamper-evident audit chain. This is how Alyria addresses OWASP ASI07 (inter-agent communication): every hand-off is authenticated, policy-checked, and on the record.
# A producing agent stores a secret for a consumer
umbra put db/prod/credentials \
--recipient agent:etl-worker \
--from ./credentials.json # encrypted under your tenant key (BYOK)
# The consumer retrieves it under a Lyra-authorized lease
umbra get db/prod/credentials --as agent:etl-worker
Short-lived leases, no standing credentials
Secrets are handed to agents as short-lived leases rather than stored on the endpoint. A Lyra capability grant is what authorizes a lease; Beacon injects it into the request at the moment of use and discards it after. Leases expire and rotate, so long-lived plaintext credentials never accumulate on disk.
{
"lease": "lease.7Q2f…",
"path": "db/prod/credentials",
"granted_by": "alyria.lyra/allow.etl-role",
"ttl_seconds": 300,
"custody": "byok"
}
Keys we never hold
For secrets consumed on an endpoint, Umbra seals each secret to that device's own hardware key (TPM or Secure Enclave), certified by your tenant root. The broker only ever moves ciphertext, and Alyria never holds the key that opens it. Secrets consumed in your cloud are kept in an isolated custodial vault under your tenant key.
The result: the secrets your agents need to collaborate live in one place, that place answers to your keys, and every access is on the record.