Security model

Monitor the lifecycle, not the secret.

A credential monitor should not become a high-value credential vault by accident. KeyGuardRail’s primary control is collecting less.

Your systemsSecret valueremains in your provider or vault
KeyGuardRailOwner · provider · environment · datesenough context to prevent missed rotation

Data and access

How the boundary is enforced

No secret values

Credential forms accept structured lifecycle metadata only. Secret values remain in the provider or vault that issued them.

Tenant-scoped access

Every inventory query derives its organization from the server session and is enforced again by forced PostgreSQL row-level security.

Hardened sessions

Opaque tokens are stored as HMAC digests in HttpOnly Secure SameSite cookies. Sessions are revocable, expire after twelve hours, and support TOTP MFA.

Append-only evidence

Security-relevant activity is written as immutable audit events with the actor, organization, action, target, and timestamp.

Private data plane

PostgreSQL stays on the internal container network. Runtime, worker, migration, and backup processes use separate least-privileged database roles.

Planned provider access

Future provider connections are read-only wherever possible, narrowly scoped, separately revocable, and encrypted outside the primary database.

Before provider integrations

Requirements for provider integrations

  • 01Independent threat-model review and abuse-case tests
  • 02Envelope encryption with a managed KMS for provider tokens
  • 03Fine-grained integration scopes and revocation runbooks
  • 04Backups, restore drills, alert delivery monitoring, and incident response

Common questions

Security review questions

Does KeyGuardRail store credential values?

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.

How is one workspace separated from another?

Every inventory query derives its organization from the server session and is enforced again by forced PostgreSQL row-level security beneath the application.

How long does a sign-in last?

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.

What record exists of security-relevant activity?

Security-relevant activity is written as immutable audit events carrying the actor, organization, action, target and timestamp.

Has an independent security review taken place?

Not yet. Internal automated checks and recovery drills are completed; independent review remains outstanding. Provider integrations remain planned and require a separate security review.

How do we report a vulnerability?

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

Build a useful inventory without handing over the keys.

Create your workspace