What protocols does SiteConduit support for building automation remote access?

SiteConduit supports BACnet/IP (UDP 47808), Modbus/TCP (TCP 502), Niagara Fox (TCP 4911, 5011), HTTP/HTTPS (TCP 80, 443), and ICMP. The protocol allowlist is configurable per site, and a default-deny bridge filter blocks everything not explicitly permitted.

How does SiteConduit prevent unauthorized lateral movement on building networks?

Every session runs behind a protocol-level firewall with a default-deny bridge filter. Only approved BAS protocols are permitted. Technicians can reach their BACnet controllers and Niagara stations but cannot access file servers, printers, or IT infrastructure. Sessions are also bandwidth-limited to prevent data exfiltration.

Does SiteConduit support compliance and audit requirements?

SiteConduit generates detailed compliance reports with full session history including technician identity, session times, protocols used, and data transferred. Reports export to CSV and are designed to support industry compliance frameworks, insurance renewals, and vendor risk assessments.

How long does it take to deploy SiteConduit at a building site?

Minutes, not months. SiteConduit ships a pre-configured CPE device to your site. Your facilities team plugs it into the building automation network. The device auto-provisions via Zero Touch Provisioning with no on-site IT support required.

Can building owners terminate remote access sessions immediately?

Yes. SiteConduit provides a one-click kill switch that terminates any session in seconds. The encrypted tunnel is disabled, credentials are revoked, and the network bridge is destroyed. Bulk termination is available per-site or across all sites in your organization.

Niagara / Tridium — Building Automation Knowledge Base

8 articles in Niagara / Tridium

NReference guide

Tridium Upgrade: Niagara Version Upgrade and Migration Guide

Technicians need to move a Niagara station to a newer version but get blocked by a lapsed SMA, version mismatches between Workbench and the station, or hardware that cannot host the target build.

9 min read

NConfig snippet

Niagara Driver Configuration Cheat Sheet

Setting up BACnet, Modbus, and LonWorks drivers in Niagara Workbench involves non-obvious configuration steps.

7 min read

NTroubleshooting checklist

Troubleshooting a Slow Niagara JACE

JACE becomes sluggish from excessive history logging, too many Workbench sessions, or SD card degradation.

7 min read

NStep-by-step guide

How to Back Up and Restore a Niagara JACE

SD card failures and botched upgrades require restore from backup, but many sites have no documented backup procedure.

8 min read

NTips collection

Niagara Workbench Productivity Tips and Shortcuts

Engineering in Workbench is slow; technicians miss batch editing, search sidebar, and compositing features.

7 min read

NStep-by-step guide

How to Export Niagara 4 History Data to CSV

Getting trend data out of a JACE for analysis or reporting requires manual steps or third-party modules.

7 min read

NStep-by-step guide

How to Connect to a Niagara JACE Remotely

Technicians cannot reach JACE controllers at remote sites; VPN config, port forwarding, and certificate errors block access.

9 min read

NTroubleshooting guide

Fix Niagara 4 Certificate and SSL Errors

Workbench shows certificate errors after expiration, IP change, or version upgrade; platform daemon fails to start.

8 min read