Machine identity lifecycle

Tie creation, rotation, suspension and retirement to a workload owner.

01 / The operating case

What changes in a real workflow?

A deployment creates a new workload identity for an agent and is later decommissioned.

Trace the authority boundary
  1. 01Owner
  2. 02Agent + workload
  3. 03Task context
  4. 04Action decision

02 / Decision contract

What the executor must check

Issue identity with an owner and purpose, rotate credentials, suspend on compromise and retire at teardown.

InputPrincipal · task · action · target
DecisionGrant ancestry · policy · current state
ResultEnforce · record · verify outcome

03 / Failure and evidence

What goes wrong, and what can be proven?

Failure mode

The workload disappears but its identity and grant remain active.

Evidence to retain

Capture issuance, rotation, use, suspension, retirement and failed post-retirement calls.

04 / Canonical scope

Why this reference stands alone

Credential lifecycle covers secrets and tokens; this page owns principal state.

Technical artifact

Principal state must outlive ephemeral credentials

Conceptual trace
CREATED → ACTIVE → SUSPENDED → RETIRED
credential K1 rotated to K2 during ACTIVE
principal P remains stable for audit joins
RETIRED rejects both K1 and K2

Run the denial test

Decommission the workload, then replay its last unexpired token. Retirement must stop access even when token signature and expiry are valid.

Primary references

Read the underlying material

Architecture discussion

Choose one consequential action and make its boundary explicit.

Request a Conversation