Cameras Don't Belong on the Internet

Cameras Don't Belong on the Internet

Why security cameras should have no internet connection, and how to keep remote access without one.

The Default Setup

Most security cameras sold today expect an internet connection. Setup means installing the manufacturer's app and scanning a QR code, and within minutes the camera is streaming footage through the manufacturer's servers to your phone.

One of our customers is an AV integrator who supports smart home systems across hundreds of residential sites. When they started, each site had port forwarding rules on the ISP modem so they could manage customer devices remotely. When the integrator switched ISPs, a technician had to visit every site and redo the port forwarding. That one change cost hundreds of truck rolls.

Cameras also carry a privacy risk that most network devices don't. In the 2021 Verkada breach, attackers reached live feeds from about 150,000 cameras at customer sites. The exposed feeds came from inside hospitals, clinics, a county jail and Sandy Hook Elementary School.

The industry treats port forwarding, UPnP, cloud relays and manufacturer backends as the cost of remote access. Each of them exposes the camera, and remote access works without any of them.

How Cameras Get Exposed

UPnP

Universal Plug and Play (UPnP) lets a device open ports on your router without asking. Many cameras enable it by default, so a new camera can open a port in your firewall and accept connections from the internet as soon as it is plugged in.

You never approve that port, and it won't appear among the port forwarding rules you created. This is one way cameras end up on Shodan, a search engine that scans the public internet and indexes the devices it finds on open ports.

Port Forwarding

Port forwarding maps a port on the router to the camera's local IP address so you can connect from outside. For one camera at one site, it takes a few minutes.

Across dozens of sites, the rules accumulate and are rarely documented. When the ISP resets or replaces a modem, the rules are lost, and a technician has to drive out and enter them again.

Every forwarded port also exposes the camera's software directly to the internet. A web server's access log shows that every public IP address receives connection attempts from automated scanners throughout the day. The web interface on an inexpensive camera is not built to withstand that.

Cloud Relays

Most consumer cameras send video through the manufacturer's cloud. You can't audit those servers, so you are trusting the manufacturer to encrypt the video, store it securely, manage access keys correctly and keep attackers out.

Large brands have failed at this. Wyze had two incidents in six months in which customers could see other customers' camera feeds. The second, in February 2024, affected about 13,000 accounts. Ring employees viewed customers' private videos, which led to a settlement with the US Federal Trade Commission in 2023.

Some manufacturers now analyze footage in the cloud to detect people and vehicles. Any video their servers can analyze is also available to anyone who compromises those servers.

Default Credentials and Firmware

Camera web interfaces often ship with default passwords such as admin/admin or admin/1234, and many are never changed. Some cameras serve RTSP on port 554 with no password at all, so anyone who can reach the camera can pull a live feed.

Camera firmware is closed and rarely audited. Security researchers regularly find hardcoded keys, plaintext credentials and debug interfaces left in production builds. Hikvision and Dahua, two of the largest camera manufacturers, are barred from US federal procurement under the NDAA over security concerns. A $40 camera with unpatched firmware and an open port is the kind of target automated scanners are built to find.

A Shodan search for RTSP or webcam returns hundreds of thousands of exposed devices worldwide. Most of them need no exploit at all. They are reachable from the internet and use either no password or the default one.

None of these exposures apply to a camera that has no route to the internet.

Take Them Off the Internet

The most effective fix is to remove the camera's internet connection entirely.

Configure the camera with a local IP address and leave the default gateway and DNS server empty. With no route outside its own subnet, the camera can talk to devices on the local network and nothing else. It can't contact the manufacturer's servers, and nothing on the internet can reach it.

Firmware vulnerabilities remain, but only someone already on the local network can exploit them.

Remote Access Without Exposure

An offline camera still has to be viewable from somewhere else, or it isn't much use.

Put a gateway on the same LAN as the cameras. The gateway can be a Raspberry Pi, a spare PC or any machine already on site. It connects outbound to an encrypted WireGuard network. The cameras stay isolated. The gateway reaches them over the LAN, and you reach the gateway through the encrypted tunnel.

Any machine running Netrinos can act as a gateway. It projects each camera and NVR on its LAN onto the private network with its own name and IP address. From a laptop or monitoring station anywhere, you open a camera's web interface or RTSP stream at that address. No ports are open on the router, and the video never passes through the camera manufacturer's servers.

For larger deployments, Netrinos Edge runs on dedicated hardware and manages hundreds of sites from a central dashboard.

The gateway only makes outbound connections, so it works behind NAT, CGNAT, double NAT and cellular links. When the ISP swaps the modem, changes the public IP or resets the router to factory settings, the gateway reconnects on its own. The cameras are unaffected, because they never had an internet connection to lose.

Our AV integrator customer now runs Netrinos Edge gateways at each site. The cameras have no internet access, and each one has its own address on the encrypted network. Technicians in the field reach any camera at any site from a laptop. When an ISP resets a modem, the gateway reconnects and the cameras keep recording, so nobody has to drive out.

That deployment has been in production for over two years, and its cameras have never been on the internet.

For multi-site deployments where every network is 192.168.1.x, see how overlay addressing solves the conflicting subnet problem.