Governance & compliance

Automatic secret rotation

Would rotate each class of secret through a crash-safe sequence, with proof that the old key is refused.

RoadmapEngine edition 5f8ea3af

What it does

Not reachable in this release. A rotation state machine and an inventory of secret classes exist as a library, but no route, command or schedule drives them against a live secret.

How it works

The machine moves a class of secret through overlap, rollout, verification, revocation and evidence. It persists each phase as a versioned record so that a crash resumes from the last phase, it records a rotation as complete after, and not before, the old key is shown to be refused and the new key to serve, and it never falls back to an old or default key when the new one is missing. The evidence record is sealed with a MAC under a key the operator supplies. An inventory lists 21 secret classes and reports each as rotated, not rotated or provider-owned. None is reported as rotated by a production binding in the shipped server, and the registry gate stays open.

What exists today in the server is narrower. The platform signing secret has its own two-step command, project keys are replaced together by an HTTP route, and one-time-code hashing accepts several keys during a changeover. Other secret classes have no rotation command in this release.

Limits

  • Not reachable in this release.
  • The seal on an evidence record shows the record was written by the machine to a holder of the evidence key. It is not a signature that a third party can check.

Evidence

  • On this siteAvailable now: signing-secret rotation
  • Tests44 library tests exist (phase order, crash resume, no fallback to an old key, sealed evidence, class inventory); none drive a live secret

Test coverage is listed as present in the engine repository at this edition. This page does not report test results.

KynetraDB is in private preview

This is not available in the preview. Request a preview to discuss the current scope.