Camera cybersecurity starts with the same basics as any networked device: current firmware, unique credentials, a segmented network, restricted remote access and a documented update owner. The brand matters less than whether those controls are actually configured and maintained after handover.
A camera is a small computer with a network connection, a firmware lifecycle and often a cloud component. Most incidents we see are not exotic exploits; they are default credentials, an exposed port, a recorder that has not been patched, or an account nobody removed.
This checklist is written for the person who has to keep the system working, not for a penetration tester.
Firmware and the update owner
Confirm that the manufacturer still supports the model and that firmware is available through a documented path. Record the installed version at handover and assign an owner for checking updates, because an unowned update process is the same as no process.
Treat end-of-support equipment as a replacement candidate. A camera that still produces an image but no longer receives security fixes belongs on the capital plan, not on the working list.
Credentials and accounts
Remove default passwords before the camera reaches the network. Give each user an account, remove departed staff promptly and avoid a shared administrator login that erases the audit trail.
Multi-factor authentication is now practical on many recorders and cloud platforms. Where it is available for remote access, it is worth the small friction.
Network segmentation and remote access
Put cameras and recorders on a dedicated VLAN or physical network separated from office computers. Allow only the traffic the system actually needs: viewing clients, update servers and the recorder’s management path.
Do not expose a camera or recorder directly to the internet with port forwarding. Use a VPN, the manufacturer’s cloud service or a documented remote-access gateway, and log who connects.
Supply chain and device identity
For new equipment, verify the model, manufacturer support status and, where applicable, the FCC ID. A valid authorization is not a security certification, but an unverifiable device is a reason to stop.
Record serial numbers, firmware versions and the supplier for each device. When a vulnerability is announced, that inventory is what lets the site answer whether it is affected.
Handover and maintenance
A secure handover includes the network diagram, camera schedule, firmware versions, account list and the update/escalation process. Test remote access and recording after every change.
Review the system at least annually and after a network or staff change. Security hygiene decays quietly; the review is what catches the account, the firmware gap or the temporary rule that became permanent.
Sources
General guidance, not legal advice and not a security audit. The controls appropriate to a site depend on its network, data and contractual obligations.
Frequently asked questions
Is a separate camera network really necessary?
It is the most effective single control. A camera VLAN or separate physical network limits what an infected camera can reach and makes access rules and monitoring easier. It does not replace firmware and credential hygiene.
Can I just use the manufacturer cloud and skip the firewall?
Cloud services can remove the need for inbound port forwarding, but they introduce accounts, data leaving the site and a dependency on the provider. Review retention, access and the exit path, and still segment the local devices.
How often should camera firmware be updated?
Check on a scheduled basis, and immediately when a relevant security advisory is published. The right cadence depends on exposure and manufacturer support; the important part is that someone owns it and records what changed.
Last reviewed: