Network and deployment architecture

A CID connects three operating areas: your corporate network, an isolated instrument network, and CID Hub. Separate interfaces and trust boundaries prevent the instrument network from becoming a route to the corporate network or internet.

Corporate network path

The Corporate NIC connects the CID Linux host to CDS clients, the OpenLab Server, DNS, NTP, and outbound internet services. The CID uses this interface to establish its outbound TLS connection to CID Hub and to download approved software.

The embedded Windows VM does not have its own address on the corporate network. A reverse proxy on the Linux host exposes only the approved paths needed for OpenLab CDS and administrative access.

Instrument network path

The Instrument NIC connects the Windows VM to the laboratory instrument. It supports Automatic addressing through DHCP or Manual static addressing. The instrument network must not provide a default gateway in either configuration. This prevents the instrument network from routing traffic through the CID to another network.

CID Hub path

The CID initiates all communication with CID Hub. HTTPS supports APIs and downloads, and MQTT over TLS carries management commands and reported state. Remote support sessions use an outbound secure-tunneling connection that the CID joins only when a session is requested and approved.

CID Hub is hosted by Agilent in AWS. Your organization does not install or maintain the Hub software. The Hub manages operational configuration and metadata; OpenLab CDS analytical data remains in your laboratory environment.

For exact endpoints and ports, see System requirements. For interface fields, see Network interfaces.