Insights ยท Checklist

Secure maintenance window checklist

Maintenance is when controls are loosened on purpose. This checklist governs the window from authorization to closure, so that nothing opened stays open and nothing changed goes unrecorded.

01Observe02Fortify03Verify04Evidence05Sustain

How to use it

Before the first step.

  • One checklist per window; retained as the change record.
  • Closure is verified by someone other than the person who did the work.

Steps

Each one owned and evidenced.

#StepOwnerEvidence
01Document the planned work, systems affected, expected duration and rollback plan.Change requesterChange request
02Obtain authorization from the change authority and the owners of affected services.Change authorityApproval record
03Identify every control to be loosened: accounts, ports, rules, alerts; record each with its restore action.Change requesterLoosened-control list
04Confirm backups or snapshots of affected systems are current and restorable.IT operationsBackup confirmation
05Verify the identity and authorization of every person performing work, including vendors and remote hands.Change authorityAccess authorization record
06Confirm monitoring coverage during the window, or compensating observation where alerts are suspended.Security operationsMonitoring note
07Open the window: enable access and make the listed changes only; log every action.EngineerWork log
08Test the change against acceptance criteria.Engineer with service ownerTest record
09Close the window: restore every loosened control from the list; disable temporary access.EngineerRestore confirmation per item
10Verify closure independently: configuration, access, alerts, ports.Second engineerVerification record
11Update configuration and asset records to reflect the change.Change requesterUpdated records
12Close the change record with outcome, deviations and any incidents.Change authorityClosed change record

By David Selakovic · Published 2026-10-16 · Revised 2026-10-16 · Reviewed every 180 days

Tell us what must not fail.

Discuss a Requirement โ†’