VASCOM TECHNOLOGY AUTOMATION CO., LTD
Home › News › How to Segment Company Networks for Cameras and…

How to Segment Company Networks for Cameras and Smart Devices

Learn how to isolate IP cameras and smart devices using VLANs and firewall rules, enable secure remote viewing through a VPN, and restrict access to recorders and management interfaces.

IP cameras, recorders, and smart devices are often connected to the same network as office computers because deployment is quick and configuration is easy. If a device still uses its default password or has a vulnerability, an attacker can exploit it to scan other machines on the internal network. Network segmentation does not eliminate every risk, but it helps limit the scope of access and makes data flows easier to control. To retain remote camera viewing, businesses should open only the necessary services instead of exposing the entire network.

Why low-cost devices should be on a separate network

Many low-cost devices have unclear update schedules, basic management interfaces, and few security options. Installers may also overlook changing passwords, disabling unused services, or checking firmware versions. Not every device has problems, but the reliability of the entire system should not depend on a device that has not been assessed.

When cameras share a network with accounting computers, servers, or storage devices, a compromised camera account can create another point of access to the internal network. Placing cameras and smart devices on a separate network allows businesses to enforce clear rules:

  • Office computers cannot access individual cameras directly.
  • Smart devices cannot connect to shared folders, printers, or internal servers.
  • Only management devices are permitted to log in to configuration interfaces.
  • Viewing and recording traffic passes through the recorder or centralized management software.

How to segment the network for easier operations

Businesses should use a dedicated VLAN for cameras and another VLAN for smart devices if the number of devices or their usage differs. Changing IP ranges alone while still permitting unrestricted routing between networks does not provide isolation; firewall rules are the determining factor.

  1. Create a list of cameras, recorders, Wi-Fi devices, MAC addresses, installation locations, and their corresponding management devices.
  2. Assign wired switch ports to the camera VLAN; create a separate SSID for wireless devices and map it to the correct VLAN.
  3. Use static IP addresses or DHCP reservations for cameras and recorders to make them easier to identify during troubleshooting.
  4. Block access between VLANs by default, then allow only management computers to access the addresses and services required for administration.

Cameras still need DNS, time synchronization, and a connection to the recorder if the system uses these services. Businesses can block cameras’ direct Internet access when cloud services are not used. Businesses should disable UPnP on the router and verify that devices cannot create port forwarding rules on their own.

What needs to be opened for remote camera viewing

The preferred approach is to connect to the company network through a VPN, then use the viewing application to connect to the internal address of the recorder or camera management software. If the recorder already receives video from the cameras, remote viewing devices only need to connect to the recorder, not to each camera.

  • With a VPN: create a rule that allows the VPN address range to reach only the recorder’s IP address and the service ports specified by the manufacturer. Do not grant access to the entire camera VLAN.
  • With a cloud application: allow only the necessary devices to establish outbound connections to the vendor’s service. Use dedicated accounts and strong passwords, and enable multi-factor authentication if available.
  • For device administration: allow access only from the management computer or VLAN; do not expose the management interface to the Internet.
  • For background services: allow DNS and NTP access to the designated servers, and avoid allowing unrestricted Internet access merely so devices can synchronize their clocks.

Do not forward the cameras’ HTTP, RTSP, or ONVIF ports directly to the Internet. If cloud services are mandatory, review the vendor’s documentation to determine which destinations the devices connect to and the extent to which those destinations can be restricted. After configuration, assign different permissions to viewing accounts and setup accounts so that viewers cannot change the system configuration.

Test after segmentation using real-world scenarios

Tests must be run from both the internal network and external locations. It is not enough to confirm that camera feeds still appear on office monitors.

  1. From a computer on the office VLAN, try opening a camera interface; access must be blocked, while the management computer must still be able to log in.
  2. Open the live view, replay a recording, and check the recording’s timestamp to detect NTP errors or lost connections.
  3. Use a phone on a mobile network to test the VPN or cloud application; if the design allows viewing only through the VPN, access must stop when the VPN is disconnected.
  4. Restart a camera and confirm that it receives the correct IP address, reconnects to the recorder, and resumes recording.
  5. Review firewall logs, the port forwarding list, and UPnP status to identify and remove any access paths not included in the design.

Businesses should retain the VLAN diagram, IP ranges, permitted access rules, and results from each test step. When replacing a camera or changing the remote viewing application, teams can reuse this list to avoid opening additional ports out of habit and then forgetting to revoke them.

Actions to take now

  1. Review passwords, firmware, UPnP, and existing port forwarding rules.
  2. Create a network diagram, identify which cameras need Internet access, and determine who is permitted to view footage remotely.
  3. Separate each device group, apply blocking rules first, and then test using the list above.

Effective network segmentation depends on clear access rules and routine checks after every change, not just on creating additional VLANs. VASCOM can help review network diagrams, firewalls, and test scenarios tailored to each business’s existing infrastructure.

Tips and how-to Talk to VASCOM
More news

Keep reading

Zalo ☎
VASCOM
Call 0822.577.579 Get a consultation