Firewall and egress requirements

The collector is outbound-only. What to allow, on which ports, and why no inbound rules are ever needed.

Updated Aug 24, 2026Product 2026.95 minMSP operator, Internal IT, Platform admin

Overview

The AssurIQ collector is an outbound-only agent. It initiates every connection to the AssurIQ control plane over HTTPS/mTLS on port 443; the control plane never opens a connection back to the collector. No inbound firewall rules, port forwards or NAT exceptions are required or supported.

Because the collector is outbound-only, it can be placed behind NAT, on a private RFC1918 range, or on a network with no public IP without any special configuration.

Required endpoints

PurposeDirectionPortNotes
Enrollment and heartbeatOutbound only443/TCPmTLS to the control plane
Evidence and scan result uploadOutbound only443/TCPSame control-plane endpoint
Installer and binary downloadOutbound only443/TCPOne-time, during install or upgrade
Auto-upgrade channelOutbound only443/TCPPeriodic check-in

Allow-list the control plane URL you were given during onboarding at the firewall or web filter level, by hostname where the filtering device supports SNI-based rules, so a future IP change does not break connectivity.

TLS inspection and content filtering

Do not TLS-inspect collector traffic
The collector authenticates the control plane and vice versa using mutual TLS. A TLS-intercepting proxy that re-signs the connection with a local certificate authority will break the mTLS handshake and the collector will fail to enroll or heartbeat.

If your organization enforces TLS inspection broadly, add an explicit bypass for the AssurIQ control plane hostname.

DNS and clock requirements

  • The host must be able to resolve the control plane hostname via DNS.
  • The host clock must be accurate; the platform tolerates up to 5 seconds of skew before heartbeat and mTLS validation are affected.
  • NTP synchronization is strongly recommended on every collector host.

Proxy environments

If outbound traffic must transit an explicit or PAC-defined proxy, configure the collector's proxy settings during or after install rather than relying on system-wide defaults, since the collector runs as a service account that may not read a logged-in user's proxy configuration.

Troubleshooting

A collector that cannot reach the control plane will show Offline once its heartbeat grace period elapses, or Enrollment Pending if it never completed its first exchange.

  • AIQ-COL-001Collector offline
    The collector has not sent a heartbeat within the expected interval. Discovery, scans and evidence collection for its sites are paused.
  • AIQ-ENR-004Control plane unreachable during enrollment
    The host could not complete the outbound HTTPS/mTLS handshake to the control plane.
Was this helpful?