Monthly Restart of Network Devices
Ensure network devices are restarted every month to maintain optimal performance.
Plain language
Reboot your network devices once a month to keep them running smoothly. If you don't, these devices can get sluggish or even fail, causing dropped connections and frustrated staff or customers.
Framework
ASD Information Security Manual (ISM)
Control effect
Preventative
Classifications
NC, OS, P, S, TS
ISM last updated
June 2026
Control Stack last updated
18 June 2026
E8 maturity levels
N/A
Guideline
Guidelines for networkingOfficial control statement
Network devices are restarted at least monthly.
Why it matters
Without regular device restarts, networks can become sluggish or crash, leading to disrupted operations, financial loss, and reduced productivity.
Operational notes
Regularly review the restart logs to identify any recurring issues and adjust the restart strategy for optimal network performance.
Implementation tips
- The IT team should create a schedule for restarting all network devices like routers and switches. Use a simple calendar tool to set monthly reminders, avoiding peak business times.
- The IT manager should inform staff about the restart schedule. Send a monthly email update, reminding everyone that brief outages might happen during these times.
- System administrators should check for software updates during each restart. Use the device's built-in update feature to look for and install any new updates that improve performance.
- The IT support team should document each restart. Keep a log with dates, times, and any issues noticed before or after restarts, to track patterns or recurring problems.
- The IT team should plan for redundancy during restarts. Ensure backup devices or alternate systems are in place to maintain critical operations, even during scheduled downtimes.
Audit / evidence tips
- Askthe restart schedule: Request a copy of the calendar or schedule that shows planned restart times for network devicesLook atthe frequency and timing of the scheduled restartsGoodshows a consistent monthly schedule that avoids disruption during peak hours
- Askemail communications to staff: Request past emails that communicated the restart schedules to staffLook atclear, consistent communication that aligns with the restart scheduleGoodincludes regular notifications sent well in advance of each restart date
- Askthe logs that show software updates were checked during restartsLook atboth the date of the updates and any action taken, like installationsGoodshows updates were checked and applied every month
- Askthe reboot logs: Request logs detailing each restart of network devicesLook atlogs that include specific dates, times, and any noted issues or anomaliesGoodshows all devices were restarted on schedule with no recurring issues
- Askdocumentation of how redundancy is maintained during restartsLook atbackup devices or plans outlined in the documentationGoodincludes clear contingency strategies ensuring limited disruption during scheduled restarts
Cross-framework mappings
How ISM-1801 relates to controls across ISO/IEC 27001, ISO/IEC 42001, Essential Eight, and ASD ISM.
ISO 27001
| Control | Notes | Details |
|---|---|---|
layersPartially 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.
Related ASD ISM controls in Networking
See all Guidelines for networking controls, or browse the full ASD ISM library.