Integrating access control with CCTV and intrusion detection combines three security systems into one coherent mechanism, in which an event from one system triggers a response in the others. Instead of three separate technology islands, the operator gets a single picture of the situation: who passed, what the camera saw and whether an alarm was triggered. In this guide we explain how such integration works at the hardware, network and software level.
Why integrate these systems
Access control alone knows that a card opened a door, but not who actually went through it. CCTV sees the image but does not automatically link it to the event. Intrusion detection senses an area breach but shows no context. Combining these layers gives image verification of events, a faster response and credible evidence. A card read is linked with a camera recording, and an intrusion alarm automatically brings up the relevant view. A side effect is also a reduction in false alarms, because the operator confirms the event with an image before dispatching an intervention.
Hardware layer: inputs, outputs and protocols
The simplest integration relies on relay inputs and outputs: the access controller outputs a signal that the recorder or alarm panel reads as an event. This is a universal solution that works between devices from different manufacturers. More advanced integration uses network protocols:
- ONVIF - a standard for communicating with IP cameras, allowing control and stream retrieval regardless of the manufacturer.
- PoE - powering cameras and devices over the network cable, which simplifies cabling and lowers installation cost.
- manufacturer integration protocols - the deepest integration, where the access control platform directly controls CCTV and intrusion systems.
Network layer: addressing, bandwidth and time
IP-based integration requires a well-thought-out network. Cameras generate traffic that must be separated from the office network, preferably on a dedicated VLAN, and for which adequate bandwidth and switches with a PoE power budget must be provided. A crucial and often overlooked point is time synchronisation: all devices should use a common time source (NTP), because only then can an access control event be precisely correlated with a video frame. A clock drift of a few seconds can nullify the entire evidential value of the material.
Software layer: a single management platform
The real value comes from shared software, in which events from three systems flow into one interface. The Protege GX platform can link access control events with cameras and intrusion modules, trigger recordings based on card reads and present the image on an alarm. You will select CCTV devices in the CCTV category, and access control and intrusion controllers and modules in the Access control and intrusion category.
Automation scenarios
Integration shows its strength in concrete rules:
- Image verification - every card read at a key passage creates a bookmark in the recording, so finding an event takes seconds.
- Alarm response - an intrusion area breach automatically brings up the camera view and notifies the operator.
- Lockdown - a single signal locks selected passages across the whole facility, for example in a threat situation.
- Area arming - the last user leaving an area arms the intrusion system, and the first entrant disarms it based on permissions.
Selecting compatible devices
The key to successful integration is compatibility already at the design stage. Check whether the cameras support ONVIF, whether the recorder has alarm inputs and outputs, and whether the intrusion panel has communication modules compatible with the access control platform. Blind selection leads to half-baked integration, where the systems formally see each other but do not carry out full automation scenarios. Design the integration as a whole, not as three purchases made separately.
Common integration mistakes
The most common mistake is treating integration as an add-on bolted on after three separate systems have been installed. It then turns out that the recorder has no free alarm inputs, the cameras do not support the required ONVIF profile, and the intrusion panel lacks a communication module compatible with the platform. The second mistake is the absence of a common time source and skipping end-to-end scenario tests. Plan the integration and its verification at the design stage, not as an improvisation at the end of the deployment.
Do you want to combine access control, CCTV and intrusion into one system? Write to us - we will select compatible devices and design automation scenarios for your facility.