Cabling is the part of a surveillance project that is decided first, changed last and costs the most to get wrong. It is also the part buyers are least likely to ask about, which is why so many systems end up with cameras where the cable could reach rather than where the risk is.
Why the two meet
On a modern installation the same cable carries the video stream and the power for the camera. That single fact makes the cabling design the constraint on the surveillance design, not the other way round.
Three consequences follow, and they shape every project.
- Where a camera can go is a cabling question. Copper runs have a practical distance limit, so a camera beyond it needs either a switch closer to it or a fiber link. Both are ordinary engineering, and both need deciding at design time rather than on installation day.
- Power is capacity, not a given. Every camera draws from a switch power budget. Add heaters, wipers or pan-tilt-zoom motors and the budget goes further than expected. A switch that powers twenty small cameras will not power twenty of a different kind.
- The cameras are network devices on your network. Segmenting them onto their own network is the most effective single control you can apply to a surveillance system, and it is a decision about switch configuration and cable termination, not about cameras. NIST publishes a baseline of what such devices should be capable of, including logical access to interfaces and device identification, which is the sort of thing you can only enforce if the network was built to allow it.
What the combination changes
The design starts with a survey rather than a camera list. Where the pathways are, where power can be delivered, what the existing switching can carry. A proposal produced without that is an estimate wearing a design's clothing.
Expansion becomes predictable. Cabling planned with spare capacity and documented terminations turns "we would like four more cameras" into a short job. Cabling installed exactly to the day's requirement turns the same request into a second project, and the difference in cost is large.
Cameras go where the risk is. When cable routes are established early, camera placement follows the purpose list. When they are not, placement drifts toward wherever a cable already runs, and the system quietly stops matching its own requirements.
Faults become diagnosable. Labeled, documented, tested terminations mean a failed camera is a ten minute question. Undocumented cabling means tracing, and tracing in an occupied building is expensive.
The system can be segmented. Isolating cameras from the rest of the network, as covered in video surveillance security and risk, is straightforward if the cabling and switching were designed for it and awkward to retrofit if they were not.
Where to start
- Survey pathways before selecting cameras. Ceiling voids, risers, conduit, external routes, and which walls cannot be drilled. This dictates what is possible.
- Establish the power budget. Total draw of the intended cameras against the switch capacity, with headroom for the cameras you will add later.
- Decide the segmentation now. Which network the cameras sit on, and what may reach them. Building it in costs nothing at installation and is disruptive afterwards.
- Cable for the next set of cameras, not only this one. Spare capacity in a pathway is the cheapest thing in the whole project when it is installed and the most expensive when it is not.
- Insist on testing and documentation. Certified terminations, a labeling scheme, and a record of what connects to what. This is the document you will want on the day something fails.
- Plan the distant cameras deliberately. Anything beyond copper distance needs a local switch or fiber. Decide which at design time.
LABUSA designs and installs both the low voltage cabling and the video surveillance systems that run on it, so the cable design follows the camera purpose list rather than the other way round. Request a free site security assessment for a survey of what your building can support. The installation sequence is in how to plan a video surveillance installation, and the cost implications in what drives the cost.
Sources
- National Institute of Standards and Technology, IR 8259A, IoT Device Cybersecurity Capability Core Baseline. Establishes the device capabilities referred to here, including device identification and logical access to interfaces, which network design has to permit. nvlpubs.nist.gov. Accessed 18 August 2026.
- National Institute of Standards and Technology, SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations. Establishes the physical and environmental protection controls, including power equipment and cabling, that a surveillance installation sits within. nvlpubs.nist.gov. Accessed 18 August 2026.