Rollback procedure executed successfully in staging or production within last 3 months

A rollback procedure that exists on paper but has never been executed is not a rollback procedure — it is a hypothesis. SOC 2 A1.3 and NIST CP-4 require that recovery procedures be tested, not just documented. Teams that have never exercised rollback discover gaps (missing permissions, undocumented dependencies, wrong migration commands) during an active production incident, extending recovery time from minutes to hours. ISO 25010 reliability.recoverability requires verified recovery capability, not theoretical capability.

Schedule a rollback drill and document it in your DEPLOYMENT.md or an incident log file.

# Rollback Drills

## 2026-02-15 — Quarterly Drill
- Deployed v2.1.0 to production
- Triggered rollback to v2.0.9
- Time to rollback: 8 minutes
- Migration rollback succeeded: yes
- Health checks passed: yes
- Gaps found: SSH key for prod DB was missing from on-call docs (fixed)
- Status: PASSED

Run drills monthly or quarterly depending on deployment frequency. Treat gaps found during the drill as P2 action items — document and fix them before the next drill. The goal is a rollback that takes under 15 minutes with any engineer on-call, not just the one who wrote the procedure.