Urgent.News

What's breaking now, across thousands of outlets.

Tech

Rotating Credentials Is Not Revoking Them. The Revocation Unit Decides Whether You Can.

The revocation unit decides whether credential rotation can ever be atomic. It is the scope one revoke action removes: a token, an identity, or a trust root. Most teams treat rotation and revocation as one operation. They aren't. Rotation issues new secrets. Revocation removes the authority of everything that could have used the old ones, and it works only if the architecture can name that set…

The revocation unit determines the extent of credential rotation, rather than the two processes being indistinguishable. Rotating secrets creates new credentials, while revocation removes authority from outdated ones, requiring a single action to eliminate the entire set. A rotation may succeed technically, but a survivor credential could still access the replaced secrets.

The revocation unit's scope dictates what it can remove, and that decision should be made during architecture design, not incident response. The revocation unit can be token-based, identity-based, or trust-root-based, each covering different sets of credentials. Reachability is the critical factor, encompassing all credentials that can access any secret within the target set, and it expands with each integration.

A comprehensive revocation requires enclosing the entire reachability graph, including the rotator itself. Atomicity means revocation is a single operation, but a residual window may exist due to caching, lifetimes, and propagation delays. Proving closure is only possible if the affected set can be named and enumerated. A trust-root revocation can invalidate an entire authority domain without listing each credential, but the proof must still demonstrate that all reachable authorities are invalid.

Recovery evidence must be kept separate from the rotated system to prevent it from being overwritten.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Seven posts on DEV, 74 views, and the one comment I never answered

I joined DEV on September 9 and posted seven articles over the next nineteen days. Together they have 74 views and 3 reactions. The last two have zero views each. Zero is a strange number. Not "low".

  • User posted seven articles on DEV between September 10-28
  • Articles collectively garnered 74 views and 3 reactions
  • Two posts received zero views, author analyzed data for reason

More from Friday 2 October →