ASD ISM 1801 Monthly restart of network devices
What it says
Network devices are restarted at least monthly.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEnsure network devices are restarted every month to maintain optimal performance.
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.
Free. Save your status, tasks and notes.
Why it matters
Without regular device restarts, networks can become sluggish or crash, leading to disrupted operations, financial loss, and reduced productivity.
How to implement
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.
Keep it running
Regularly review the restart logs to identify any recurring issues and adjust the restart strategy for optimal network performance.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
the restart schedule: Request a copy of the calendar or schedule that shows planned restart times for network devices.
Look at
the frequency and timing of the scheduled restarts.
Good evidence
shows a consistent monthly schedule that avoids disruption during peak hours.
- Check 2 of 5What an auditor asks for
Ask for
email communications to staff: Request past emails that communicated the restart schedules to staff.
Look at
clear, consistent communication that aligns with the restart schedule.
Good evidence
includes regular notifications sent well in advance of each restart date.
- Check 3 of 5What an auditor asks for
Ask for
the logs that show software updates were checked during restarts.
Look at
both the date of the updates and any action taken, like installations.
Good evidence
shows updates were checked and applied every month.
- Check 4 of 5What an auditor asks for
Ask for
the reboot logs: Request logs detailing each restart of network devices.
Look at
logs that include specific dates, times, and any noted issues or anomalies.
Good evidence
shows all devices were restarted on schedule with no recurring issues.
- Check 5 of 5What an auditor asks for
Ask for
documentation of how redundancy is maintained during restarts.
Look at
backup devices or plans outlined in the documentation.
Good evidence
includes clear contingency strategies ensuring limited disruption during scheduled restarts.
Mappings
Closest match in ISO/IEC 27001: A.8.20, Network and network devices security, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.20.
ISM-1801 requires network devices to be restarted at least monthly, a specific operational practice that helps clear volatile, memory-resident compromises and unsaved changes from network devices. It is one concrete way of meeting Annex A 8.20, which requires networks and network devices to be secured, managed and controlled. Annex A 8.20 covers network security management as a whole, whereas ISM-1801 addresses only the restart frequency of network devices.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.