Insights · Field note · Infrastructure and resilience
Secure maintenance windows
Maintenance is when controls are loosened on purpose. Most incidents traced to maintenance come from a window that never properly closed.
A maintenance window is a scheduled period in which systems are changed, and in which accounts are enabled, ports opened, alerts silenced and configurations altered to make the work possible. A secure window governs the whole cycle: the plan and rollback documented, the loosened controls listed with their restore actions, authorization recorded, backups confirmed, identities of those performing work verified, monitoring coverage maintained, every action logged, and at closure every loosened control restored and independently verified. The closure verification is the step that matters most and the one most often skipped, because by then everyone is tired and the change worked.
In detail
What the evidence shows.
Before the window
The change request states what will be done, to what, for how long, with what expected result and what rollback. The loosened-control list names every account, rule, port and alert that will be changed to enable the work, each with its restore action. Authorization comes from the change authority and the affected service owners. Backups or snapshots are confirmed restorable.
During the window
Only the listed changes are made. Every action is logged. Monitoring stays on, or compensating observation is arranged where alerts must be suppressed. Vendor and remote technicians are verified before they act. Acceptance tests confirm the change did what it should.
Closing the window
Every item on the loosened-control list is restored and the restore is confirmed. Temporary access is removed. A second person verifies configuration, access, alerts and ports independently. Asset and configuration records are updated. The change record is closed with outcome and deviations.
Why this is a security control
NIST SP 800-53 and SP 800-171 both carry maintenance requirements for exactly this reason: maintenance is a sanctioned bypass of controls, and the bypass must end. The secure maintenance window checklist walks through each step; see secure maintenance workflows and the glossary entry for secure maintenance window.
Sources
Primary references.
- NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations (configuration management, maintenance and physical protection families)
- NIST SP 800-171 Rev. 2, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (maintenance and physical protection requirements)
- Performance Data engagement observations (first-hand: David Selakovic); method described under Infrastructure Resilience and Partner and White-Label Delivery.
By David Selakovic · Published 2026-10-16 · Revised 2026-10-16 · Reviewed every 180 days