[Feature] Provide a governed key-vault and key-lifecycle capability #2

Open
opened 2026-07-30 17:34:18 +02:00 by zemion · 0 comments
Owner

Implement the module-neutral key custody layer after the threat model is accepted.

Acceptance criteria

  • Stable capability contracts cover key creation/import, wrapping, rotation, revocation, destruction scheduling, recovery, and status/provenance.
  • Key material never crosses module capability boundaries as plaintext.
  • Tenant/scope isolation, policy provenance, recent-auth requirements, quorum recovery, and audit-safe events are enforced.
  • Providers can be local development, deployment KMS/HSM, or client-held without callers importing provider modules.
  • Secret values are redacted from logs, APIs, events, exceptions, and diagnostics.
  • Test vectors, failure injection, migration, backup/restore, and key-loss behavior are covered.
Implement the module-neutral key custody layer after the threat model is accepted. ## Acceptance criteria - Stable capability contracts cover key creation/import, wrapping, rotation, revocation, destruction scheduling, recovery, and status/provenance. - Key material never crosses module capability boundaries as plaintext. - Tenant/scope isolation, policy provenance, recent-auth requirements, quorum recovery, and audit-safe events are enforced. - Providers can be local development, deployment KMS/HSM, or client-held without callers importing provider modules. - Secret values are redacted from logs, APIs, events, exceptions, and diagnostics. - Test vectors, failure injection, migration, backup/restore, and key-loss behavior are covered.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-encryption#2
No description provided.