How credentials are protected
Your secret is never stored in the clear
When you register an agent, you receive its secret exactly once. MudraID stores only a one-way cryptographic hash of it — never the secret itself. If you lose the secret, you rotate for a new one; it can’t be recovered, by design. A stolen copy of the MudraID database does not hand anyone a usable credential.The secret never travels to the platforms you call
Your agent’s secret is exchanged for a short-lived token by the SDK, and only the token is sent onward. The services your agent calls never see the long-lived secret. The architecture keeps the two strictly separate, so a credential can’t leak onto an outbound request.Tokens are short-lived and verified independently
Agents authenticate with tokens that expire in minutes, not with standing secrets. Tokens are cryptographically signed by MudraID, and each platform verifies them on its own using published keys — no per-request callback to a central server. A token issued for one platform is rejected at any other.Comparisons are constant-time
Every credential and token check uses constant-time comparison, so an attacker can’t learn a secret by measuring how long a check takes.How you stay in control
Least-privilege scopes
Platforms grant each agent only the permissions it needs, per route. There’s no implicit escalation — holding one permission never silently grants another. An agent can do exactly what it was granted, and nothing more.Instant revocation
Revoke an agent and it stops receiving new tokens immediately. Any token already in flight expires on its own within minutes. This is your fast containment path if a credential is exposed. See Rotate a compromised secret.Tamper-evident audit
Every verification — success or failure — is recorded in an append-only, tamper-evident log. If you need to prove what an agent did and when, the record is there.What MudraID stores — and what it doesn’t
Knowing where your data lives matters for due diligence. In plain terms: MudraID stores:- Agent and platform identities, and their metadata.
- A one-way hash of each agent secret — never the secret itself.
- Which agents are granted which scopes on which platforms.
- The audit log of verifications.
- Your agent secrets in plaintext.
- The request or response payloads your agent exchanges with platforms. MudraID authenticates the call; it is not in the path of your business data.