Nettverks- og brannmurkrav

For de fleste bygg trenger Arcturus ingenting fra nettverket deres — ingen VPN, ingen innkommende tilkoblinger og ingen brannmuråpninger. Plattformen kommuniserer med SD-anlegget gjennom SD-leverandørens sky, den samme skyen SD-anlegget allerede bruker, og med innendørssensorer gjennom sensorleverandørens sky. Begge koblingene er utgående fra disse skyene, ikke fra bygget.

Skybaserte SD-anlegg (vanligst)

IWMAC, Airthings, Disruptive Technologies og lignende skybaserte leverandører fungerer slik: enheten på bygget sender avlesninger til leverandørens sky over den eksisterende internettforbindelsen, og Arcturus leser fra den skyen. Brannmuren deres ser bare utgående HTTPS fra enheten til leverandøren — ingenting nytt, ingenting fra oss.

When your equipment connects to us (Niagara MQTT)

For Niagara sites the direction is the other way round from the cloud-BMS case, but still nothing inbound: we host the MQTT connection point, and the Niagara station in your building connects OUT to it over TLS on port 8883. Your firewall sees one more outbound connection from the station and nothing new coming in — no port to open, no hostname to expose. The one thing installed on your side is our certificate file (mqtt-ca.crt) in the station's trust store, so the station can verify it is talking to us; your supplier does that. The owner guide "Niagara: connect your building to us" and the technical page for your supplier describe the setup.

When we connect to your system (IWMAC and other APIs)

For IWMAC and the sensor providers we connect to the vendor's cloud API, never to your building. Nothing on your network is involved beyond the outbound path the device already uses to its vendor.

Hva du gir IT-teamet ditt

• For skybaserte SD-anlegg (IWMAC, sensorleverandører): ingenting. Den eksisterende utgående HTTPS-forbindelsen enheten bruker mot leverandøren, er den eneste forbindelsen som er involvert.
• For Niagara MQTT: the station makes one outbound TLS connection to our broker on port 8883. Nothing inbound; no firewall opening. If outbound traffic is filtered, that one destination and port need to be allowed.
• For all sites: no static IP from us, no agent to deploy on the building network.