On a ten-camera system, a firmware update is an afternoon’s work. On a site running hundreds of cameras, several NVRs and a VMS, however, a single badly planned update can knock every camera in a building off recording; the NVR reboots, the new version has disabled the old authentication method, and the cameras don’t reconnect. This guide covers the work after deciding which update is urgent: release notes, configuration backup, test group and wave plan, bulk update methods, rollback and verification. How to decide which vulnerability takes priority is the subject of the camera and NVR vulnerability tracking article.
Before updating: release notes and compatibility
Before downloading the package, the release notes are read line by line. Most field failures come from a line that was in the notes but went unread. Information to look for:
- Vulnerabilities fixed: This is often the reason for the update; record the CVE numbers if present.
- Behavior changes: Services disabled by default (e.g. Telnet, old TLS versions, weak authentication methods such as HTTP Basic), a changed password policy, differences in ONVIF user management. These changes can break the VMS connection.
- Intermediate version requirement: Some manufacturers don’t allow a direct upgrade from a very old version to the latest; you first have to move to a specific intermediate version.
- Downgrade restriction: For security reasons, some manufacturers block downgrading after a certain version. The information is in the release notes or the manufacturer’s support documents; if not, ask the manufacturer.
For urgency, don’t look only at the manufacturer’s severity rating; whether the vulnerability is being actively exploited is more decisive. The US cybersecurity agency’s Known Exploited Vulnerabilities catalog is the primary source for this check. A vulnerability on the list may require speeding up the wave plan.
The second check is VMS compatibility. Enterprise VMS manufacturers publish the model and tested firmware versions in their supported device lists. Check whether the target firmware has been tested together with the VMS version on site. A simple compatibility matrix saves redoing the same research for every update:
| Model | Current version | Target version | VMS support | Note |
|---|---|---|---|---|
| Dome A | x.y.1 | x.y.4 | Tested | No intermediate version needed |
| Bullet B | x.w.2 | x.z.0 | Not on the list | Verify in the pilot |
| NVR C | v.3 | v.5 | Not applicable | v.4 required first |
Configuration backup and inventory
On most devices, an update keeps the configuration. There are versions that don’t, and faults that require a reset; on that day, a device without a backup is rebuilt by hand, as far as anyone can remember. For each device, the following are taken before updating:
- The configuration file exported from the device’s own interface (the “Configuration export/backup” menu with most manufacturers). These files may contain passwords and certificates; store them in a location with restricted access.
- A summary of network settings, stream profiles, event rules, masking areas and user accounts; needed for manual reconfiguration if the file can’t be restored.
- Current firmware version, serial number and location information.
This information is part of the inventory. A wave plan can’t be made without an up-to-date inventory: the impact of a wave can’t be calculated without knowing which camera is connected to which NVR and switch.
Also verify the integrity of the firmware file. If the manufacturer publishes a SHA-256 hash, compare it with the hash of the downloaded file:
# Linux
sha256sum camera_fw_x.y.4.bin
# Windows PowerShell
Get-FileHash .\camera_fw_x.y.4.bin -Algorithm SHA256
Take the file only from the manufacturer’s official download page. A package from a forum or third-party site is a separate risk disguised as a security update.
Test group and wave plan
An update always starts with a small test group. The group includes at least one camera of every model to be updated, preferably from non-critical areas. It’s observed for at least one day–night cycle; recording, events, analytics and night images are checked. A version that looks fine by day may behave differently at the IR transition or in night noise reduction.
Then the waves are planned. The rules of a good wave plan:
- Not all cameras seeing the same area are updated together in one wave; neighboring cameras are spread across different waves so a problem doesn’t leave an area completely blind.
- Critical areas (checkouts, main entrance, perimeter) are left for the last waves; by then the method has been proven.
- Wave size is limited to the number the team can verify and, if necessary, roll back within the maintenance window.
- NVR and recording server updates are planned separately from camera waves; when an NVR reboots, recording of all connected cameras is interrupted.
The plan also covers informing affected parties. Security operators should know in advance which cameras won’t give video briefly at what times; if there’s an alarm monitoring center, connection loss alerts during this period should be marked as expected events. If the recording platform’s “camera offline” notifications are tied to an email or SMS flow, they’re temporarily suppressed for the relevant wave to avoid unnecessary escalation during the maintenance window, and must be re-enabled at the end of the window. This is exactly where the common mistake happens: a notification rule forgotten at closeout silently swallows a real fault weeks later. Write it on the closeout list.
The maintenance window is planned at the workplace’s least critical time, with the security team’s knowledge. Taking a screenshot of the recording status at the start and end of the window makes it easier to prove the duration of the interruption in later reviews.
Bulk update tools and methods
In large corporate camera systems, updating cameras one by one from the web interface is both slow and error-prone; by the twentieth camera, it gets confusing which ones are done. Common methods:
| Method | Example | Watch out for |
|---|---|---|
| Manufacturer device management tool | Axis Device Manager, Dahua ConfigTool, Hikvision Batch Configuration | Limit how many devices the package is sent to at once |
| Updating via the VMS | Some VMS products offer it for supported devices | Check supported models and versions |
| Updating via the NVR | Same-brand cameras connected to the NVR | If the NVR itself isn’t up to date, the package may be incompatible |
| Web interface, one by one | A small number of devices or problem devices | A record must be kept for each device |
Keep the number of simultaneous updates small in a bulk tool. Hundreds of devices downloading the package at once fills the uplinks, timeout errors start and half-finished uploads create the riskiest situation. Separately verify the new version of every device that shows as “successful” in the tool’s report. The report can be wrong.
Rollback scenarios
The rollback plan is written before the update starts and covers these scenarios:
- The device boots but the VMS connection is down: Usually the authentication method or ONVIF user setting has changed. Check the configuration first; if that doesn’t solve it, roll back to the previous version (if there’s no downgrade restriction).
- Video or event behavior has changed: Stream profiles and event rules are compared with the backup.
- The device doesn’t boot: Some manufacturers have recovery procedures (such as loading via TFTP); these are model-specific and applied according to manufacturer documentation. Keeping a spare device on site preserves coverage while recovery is pending.
- Downgrade blocked: The only way is forward; wait for the manufacturer’s next fix release or open a support ticket. That’s why the test group period is extended for versions that block downgrades.
Post-update verification
At the end of each wave, you don’t move on to the next wave until this list is complete:
- The firmware version matches the target version in the inventory.
- The camera is online in the VMS/NVR, main and substreams are received, and the only gap on the recording timeline is at the time of the update.
- Time comes from NTP, the time zone is correct.
- Event rules and analytics triggering have been tested.
- Privacy masks are in place.
- Services the update may have re-enabled (UPnP, P2P cloud, Telnet) have been checked; hardening settings are preserved.
- The night image was checked the following night.
Don’t skip the service check. Some versions restore defaults, and the P2P cloud access you disabled comes back on.
Records and change management
Every update is linked to the camera periodic maintenance plan and a change management record. A simple record template carrying the fields below serves both as audit evidence and as a reference for the next update:
| Field | Example content |
|---|---|
| Change no. / date | Internal change record number, window time |
| Scope | Wave name, device list |
| Old / new version | Per model |
| Reason | CVE, bug fix, VMS compatibility |
| Result | Successful, rolled back, pending |
| Verified by | Name, date |
The change window approach used for network devices can be applied directly to camera updates; for pre-checks and verification steps, see the network change window planning article. For continuous monitoring of camera status after updates, the camera health monitoring guide is complementary. To run the process in a planned, recorded way, see our camera and NVR firmware update management service page.
Frequently asked questions
Does a camera firmware update erase the configuration?
With most manufacturers, a normal update keeps the configuration; some major version upgrades or faults, however, may require a reset. That’s why the configuration file is exported before every update and a summary of key settings is recorded in the inventory.
Is it always possible to go back to an older firmware version?
No. For security reasons, some manufacturers block downgrading after certain versions. This restriction is verified in advance from release notes or with the manufacturer; for versions that block downgrades, the test group period is extended.
Can all cameras be updated on the same night?
Technically yes, but it isn’t recommended. First a test group of each model is updated, then the rollout proceeds in phases with neighboring cameras spread across different waves; that way a problem doesn’t leave an area completely blind.
In what order should NVRs and cameras be updated?
First, dependencies in the release notes are checked. Usually the NVR or VMS is brought to a level that supports the target camera version, then the cameras are updated in waves. Since an NVR update interrupts recording of all connected cameras, it’s done in a separate window.