Infrastructure · Infrastructure Resilience · 08
Secure maintenance workflows
Secure maintenance workflows define how routine and emergency maintenance on critical infrastructure is requested, approved, scheduled, performed, verified and recorded, so that maintenance does not become the cause of the outage or the security incident it was meant to prevent. They are needed when maintenance is performed ad hoc, when changes have caused outages, when vendor engineers work unsupervised in sensitive environments, when a regulator or customer requires change control evidence, or when the same window is used for several uncoordinated tasks. The workflows produce a change and maintenance procedure fit for the environment, pre-work checks and rollback plans, supervision and access rules for third parties, and the records that show maintenance was controlled.
Scope
What the review covers.
- Change request, risk assessment and approval
- Scheduling and maintenance windows with conflict checks
- Pre-work verification: backups, rollback plan, communications
- Third-party and vendor access rules and supervision
- Execution checklists and post-work verification
- Records for audits and post-incident review
Deliverables
What you receive.
| Deliverable | Form |
|---|---|
| Maintenance procedure | Request to record, fit for the environment |
| Checklists | Pre-work, execution, post-work verification |
| Third-party access rules | Supervision, credentials, logging |
| Change records | Evidence of controlled maintenance |
Prerequisites
What we need from you.
- The current change process, if any, and the systems it must cover
- Vendor and third-party maintenance arrangements
- Agreement on approval authority and windows
Related
Where this sits.
- Infrastructure Resilience Service
- Infrastructure Hub
- Asset and configuration review Also
- Recovery testing Also
By David Selakovic · Published 2026-10-16 · Revised 2026-10-16 · Reviewed every 180 days
Questions
Asked before engaging.
Will this slow maintenance down?
It adds a check before work starts and a verification after. In our experience it prevents more time lost to failed changes than it costs.
How are emergencies handled?
With an expedited path that still records what was done and why, and reviews it afterward.
Does this cover cloud infrastructure?
Yes. Change control applies to cloud configuration as much as to a rack.