Security model
This page describes the Connected Instrument Device (CID) trust boundaries, attack surface, device identity, and user identity. It provides the answers an IT reviewer needs to evaluate a CID against a domain-controlled lab PC. Procedures live in the How-to guides. Authoritative network details live in System requirements. This page explains the relevant mechanisms and the current security posture of the Connected Instrument Device.
CID Hub architecture
The CID Hub is the Software-as-a-Service (SaaS) control plane that activates CIDs, distributes software and configuration, mediates Agilent-support tunnels, and stores the Activity Log of administrative actions. Agilent hosts and operates the Hub as a fully managed service, and access is included with your CID purchase, so there is no Hub software for you to install, host, patch, or maintain. The Hub is not offered as installable software for on-premise or private-cloud deployment. This page describes the Hub's AWS service inventory, multi-tenant isolation model, and region / residency posture.
Data flow and privacy
This page describes the data flows in a CID solution. It covers what moves between the CID, your local OpenLab systems, the CID Hub, and external services; what stays on your local network; how data is protected in transit; and where and for how long the Hub stores it. It is written for IT and security teams reviewing a CID deployment.
Remote access
This page explains how remote access to a CID works and how it is controlled. It is for IT and security reviewers assessing session boundaries, approvals, and traceability, and for the CID Hub administrators and Agilent support users who operate within them.
Traceability and compliance
This page describes how the CID Hub records administrative and operational events, how long those records are retained, what tamper-protection exists, and how software changes are logged across their lifecycle. The page also discusses how the CID relates to laboratory-records compliance frameworks.