Best practices for connecting intrusion panels to the network - Genetec™ Intrusion Protocol 5.0.0

Genetec™ Intrusion Protocol Extension Guide 5.0.0

Applies to
Genetec™ Intrusion Protocol 5.0.0
Last updated
Content type
Guides > Plugin and extension guides
Genetec™ Intrusion Protocol

To ensure performance and security, it is considered a best practice to host your intrusion panels on an isolated network.

Performance considerations

Intrusion detection panels are not designed to withstand heavy traffic from the network, especially when broadcast messages occur frequently. Because the panel needs to process incoming packets to check whether it is the recipient, this might lead to increased demand on processing resources. Under heavy network load conditions, you might notice that the panel drops offline and reconnects repeatedly.

To avoid this, we recommend that you connect the panel to the Genetec™ Intrusion Bridge through an isolated network to isolate the panel from traffic for which it is not the recipient. Multiple panels can be connected to the same isolated network, as long as the network is not a hub for traffic unrelated to panels.

Security purposes

If your panel manufacturer does not use encryption in their communication protocol, your panels must be hosted on an isolated private network to prevent attackers from intercepting data related to the panel.

Building an isolated network

You can build an isolated network by adding a dedicated hardware network node (switch or router), or by creating a dedicated Virtual Local Area Network (VLAN) on a network node that provides network node configuration capabilities.