No secret values
Credential forms accept structured lifecycle metadata only. Secret values remain in the provider or vault that issued them.
Security model
A credential monitor should not become a high-value credential vault by accident. KeyGuardRail’s primary control is collecting less.
Data and access
Credential forms accept structured lifecycle metadata only. Secret values remain in the provider or vault that issued them.
Every inventory query derives its organization from the server session and is enforced again by forced PostgreSQL row-level security.
Opaque tokens are stored as HMAC digests in HttpOnly Secure SameSite cookies. Sessions are revocable, expire after twelve hours, and support TOTP MFA.
Security-relevant activity is written as immutable audit events with the actor, organization, action, target, and timestamp.
PostgreSQL stays on the internal container network. Runtime, worker, migration, and backup processes use separate least-privileged database roles.
Future provider connections are read-only wherever possible, narrowly scoped, separately revocable, and encrypted outside the primary database.
Before provider integrations
Common questions
No. Credential records are limited to identifiers, provider, environment, ownership, dates, policy intervals and an optional runbook URL. Passwords, API keys, private keys, tokens, certificate bodies and recovery codes are not requested.
Every inventory query derives its organization from the server session and is enforced again by forced PostgreSQL row-level security beneath the application.
Sessions are opaque tokens stored as HMAC digests in HttpOnly Secure SameSite cookies. They expire after twelve hours, are revocable, and support TOTP multi-factor authentication.
Security-relevant activity is written as immutable audit events carrying the actor, organization, action, target and timestamp.
Not yet. Internal automated checks and recovery drills are completed; independent review remains outstanding. Provider integrations remain planned and require a separate security review.
Email security@keyguardrail.com, or use the contact details published at /.well-known/security.txt. Please include enough detail to reproduce the issue.
Start small