Perform Monthly Restarts of Network Devices
Restart network devices every month to maintain reliability and performance.
Plain language
Network devices, like routers and switches, should be restarted every month to keep them running smoothly and securely. If they're not restarted regularly, these devices could slow down or malfunction, which might lead to network outages or security vulnerabilities.
Framework
ASD Information Security Manual (ISM)
Control effect
Preventative
Classifications
NC, OS, P, S, TS
ISM last updated
Aug 2022
Control Stack last updated
19 Mar 2026
E8 maturity levels
N/A
Guideline
Guidelines for networkingSection
Network design and configurationOfficial control statement
Network devices are restarted on at least a monthly basis.
Why it matters
Neglecting monthly restarts can lead to device sluggishness or failures, risking network outages and potential security breaches.
Operational notes
Schedule monthly reboots in maintenance windows; stagger HA pairs and verify uptime/health post-restart. Record completion and investigate devices that fail to reboot.
Implementation tips
- IT team: Schedule regular monthly restarts for all network devices. Use a calendar reminder or automated task to ensure each device is restarted within the given month without disrupting business operations.
- System administrator: Document the restart procedure for each type of network device. Ensure clear and simple instructions are available, detailing the steps to safely reboot each device.
- IT manager: Communicate the restart schedule to all staff. Inform teams about potential short downtime during device restarts so they are prepared and not caught off guard.
- Helpdesk team: Monitor the network before and after restarts to identify any issues. Check system performance reports and follow up on any anomalies that appear post-restart.
- Procurement officer: Ensure all network devices are under a maintenance agreement that includes support for regular restarts. This ensures any issues can be promptly resolved with the manufacturer's help if needed.
Audit / evidence tips
-
Askthe network restart schedule: Request a calendar or log that shows when each network device was last restarted
GoodA detailed log with device names and restart dates showing monthly restarts
-
Askto see the restart procedures document: Ensure it includes step-by-step instructions for each device type
GoodA comprehensive document that includes all necessary steps and safety measures for device restarts
-
Askcommunication records about restart notifications: Request emails or notices sent to staff about scheduled downtime
GoodEmails sent at least 24 hours before the restarts, clearly communicating the schedule
-
Askperformance reports from before and after restarts: Request system monitoring reports that highlight network performance
GoodReports showing stable or improved performance metrics after restarts
-
Askthe maintenance agreement details: Ensure support covers issues that could arise from restarts
GoodA service level agreement with clear terms on support for restart-related issues
Cross-framework mappings
How ISM-1801 relates to controls across ISO/IEC 27001, Essential Eight, and ASD ISM.
ISO 27001
| Control | Notes | Details |
|---|---|---|
| layers Partially meets (1) expand_less | ||
| Annex A 7.13 | ISM-1801 requires organisations to restart network devices at least monthly as a preventative maintenance activity to sustain reliable op... | |
These mappings show relationships between controls across frameworks. They do not imply full equivalence or certification.