Hands-on tutorial
Tutorials · Security Operations
How to Run Patch Management for Network Devices
Keep switches, gateways, access points, cameras and firewalls patched with a repeatable process: inventory, risk-based priorities, testing, maintenance windows and records.
Before you start
- An inventory of devices with model and firmware version
- Vendor security advisory sources
- A test device or lab for each important model
Step by step
Know what you have
List every network device with its model, firmware version, location and owner. Cloud management platforms can produce this automatically.
Watch for advisories
Subscribe to vendor security pages and check public lists of exploited vulnerabilities. Note which of your devices are affected.
Prioritise by risk
Patch internet-facing devices and actively exploited flaws first, within days. Routine updates can follow a monthly or quarterly cycle.
Test before rollout
Update one device or a small site first, check the main functions, and read the release notes for changed defaults.
Use maintenance windows
Schedule updates when the impact is lowest, update redundant pairs one at a time, and keep the previous firmware ready for rollback.
Verify and record
Confirm the new version is running and the device works. Record what was updated, when and by whom.
Report
Report coverage monthly: how many devices are on current firmware and which exceptions remain, with reasons.
Pro tips
- Back up configurations before every update.
- Verify firmware signatures or checksums before installing.
- Plan replacements for devices that no longer receive updates.
FAQ
Frequently asked questions
How often should network devices be patched?
Critical, exploited vulnerabilities within days; others in a regular monthly or quarterly cycle.
What if a device has no fix?
Reduce exposure: restrict management access, disable the affected feature, isolate the device, and plan its replacement.
Keep learning
Related guides
Safe firmware upgrades
Read more →Network asset inventory
Read more →Vulnerability scanning with Nmap and OpenVAS
Read more →How to Set Up a WireGuard VPN Server for Remote Access
WireGuard is a fast, modern VPN with a small, auditable code base. Build a WireGuard server on Linux, add users with their own keys and route them only to the networks they need.
Read more →How to Scan Your Network for Vulnerabilities With Nmap and OpenVAS
Find open ports, outdated services and known vulnerabilities before attackers do. Discover hosts with Nmap, then run authenticated vulnerability scans with Greenbone OpenVAS and fix what matters first.
Read more →How to Build a Free SIEM With Wazuh for Network and Server Logs
A SIEM collects logs from servers, firewalls and switches in one place and alerts on attacks. Install Wazuh, add agents and syslog sources, and tune the first alerts.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.