Checklist · Delivery

Release day: deploy and roll back

What to confirm before, during and after a production release, including the exact moment to stop and roll back.

Owner: Release managerTime: 30 min plus the releaseISO 27001 A.8.32ISO 27001 A.8.31ISO 27001 A.8.15

0 of 21

Before the release

The change record is approved and names the release window, the owner and the rollback owner.
The exact build that passed staging is the one being released; same digest, not a rebuild.
CI is green on the release commit, including security scans.
Database migrations are backward compatible with the previous version, so rollback does not need a restore.
A fresh backup or snapshot exists and its timestamp is noted in the change.
Feature flags for risky changes default to off.
Support and stakeholders know the window; no conflicting changes are scheduled.

During the release

Deploy gradually (canary or blue-green) and watch error rate, latency and saturation at each step.
Health checks pass on every new instance before it receives traffic.
Migrations ran once, completed and are recorded; no manual hot-fixes on servers.
Smoke tests cover login, the main business path and one write operation.
Security-relevant behaviour verified: authentication, authorization on a restricted route, TLS.

Roll back immediately when

Error rate or latency passes the threshold agreed in the change for more than the agreed minutes.
Any data corruption, authorization bypass or secret exposure is suspected.
A migration fails partway through and the state is not clearly recoverable.
The rollback owner calls it. No debate during the window; analysis comes after.

After the release

Dashboards watched for at least one full business cycle or the agreed observation period.
Feature flags enabled in stages and watched at each stage.
Change record closed with the actual times, the result and any deviations.
Old versions and temporary access (break-glass, debug ports) removed.
Follow-ups from the release are ticketed with owners, including anything that nearly went wrong.

Adjust it to your environment before relying on it. A finished list shows a routine was followed; it does not guarantee nothing was missed. ISO references show where a list helps, not that it satisfies a control.

See these as tasks in Cisodium All checklists

Klar til at komme
videre end klassisk GRC?

14 dages gratis prøve. Intet betalingskort. Cloud eller on-premises.

Book demo Tal med salg →