FEEDBACK LOOP — monitoring alerts, overdue rotations, failed recovery tests and compromise lessons return to PLAN and ACCESS CONTROL, and revise the key policy that let them through
The six states are the key states in NIST SP 800-57 Part 1 §7, used here only as a vocabulary. Each state names the lifecycle stages on the model tab that act on it, so you can move between the two. Every transition should be recorded in the key's metadata and audit log.
A key is created in pre-activation, used while active, may be suspended, is deactivated once it should no longer protect new data, and ends destroyed. At any point it can become compromised, and from there it is only ever destroyed.
Will follow the dependency model on the GOV Assured DevSecOps operating model: an AND/OR tree showing what "keys are protected through their full lifecycle" depends on — HSM-backed KMS, IAM, audit logging, SOC monitoring, backup, the inventory and the recovery runbooks — with as-is and to-be coverage. Scores would be illustrative.
A later section. The core model stays vendor-neutral; this tab will map each of the twelve stages to how the three services implement it, with each row linked to the provider's own documentation. Proposed rows:
| Stage | Question per provider |
|---|---|
| 02 Generate | HSM protection levels and their FIPS 140 validation; import options |
| 04 Access control | Key policy / RBAC model; separating encrypt, decrypt and administer |
| 06 Rotate | Automatic rotation support and limits by key type |
| 07 Monitor | Native audit log for key use and administration |
| 08 / 10 Disable and destroy | Disable, soft-delete, purge protection and deletion waiting periods |
| 11 Recover | Redundancy, backup and cross-region options |