SenseOn Deployment Architectures
Cloud Deployment with Endpoint Collectors
The SenseOn Endpoint Network Sensor (EPNS) is a feature that uses only endpoint agents to get network telemetry. This telemetry is equivalent to the telemetry from an appliance on a mirror or TAP. EPNS is particularly useful for organisations with a large number of satellite offices or a large remote workforce. For these organisations, physical appliances can be too expensive or too complicated to deploy. With EPNS, you install software, not hardware, to expand a deployment. Thus, you do not have to do on-site visits or change requests, and space and power budgets do not limit the deployment.
EPNS also gives visibility of network traffic from public cloud environments. You do not need dedicated virtual servers, and you do not have to change the configuration of cloud networks.

Cloud Deployment with Endpoint Collectors and Network Probe
Probe Appliances
You can deploy SenseOn probe appliances at your sites. A probe appliance captures network traffic and sends it to the virtual analysis appliance. Probe appliances can be physical or virtual. A physical probe appliance is configured to receive network traffic from at least one mirror or TAP. Usually, this traffic comes from the core switch at the location of the probe appliance.
The virtual probe appliance can run on VMware ESXi 6.5 and 6.7. It is configured to capture network traffic from the VMware vSwitch, or from a physical TAP or mirror. Your network can have a large number of separate locations that already have virtual infrastructure. If so, virtual probes can be more cost-effective and quicker to deploy than physical probes. Physical and virtual probe appliances both send their data to the virtual analysis appliance through an outbound connection on TCP port 1194.

On-Site Deployments
On-Site is By Exception: Use our managed cloud deployments. We strongly recommend them for all customers. Cloud deployments have significant advantages over on-premise solutions, for example scalability, higher availability and better recovery capabilities.
We provide on-site deployments, but usually only in exceptional circumstances. Our focus is to give the best possible service with the reliability and flexibility of cloud infrastructure. For most scenarios, cloud infrastructure is generally more efficient and more effective.
On-premise deployments have these components:
Analysis Appliance
The physical analysis appliance is the core of a single-site physical deployment. The appliance is installed on-premise at an office or data centre. It collates and analyses the data that the platform collects, and it hosts the SenseOn User Interface. It is configured to receive network traffic from at least one mirror or TAP, usually from the core switch at the installation location. The appliance arrives at the deployment site already built and configured for the needs of your organisation. Usually, the installation of the appliance takes less than one hour.
Analysis Appliances Can Monitor Traffic: You can configure an on-premise analysis appliance with separate capture interfaces to monitor traffic.
Probe Appliances
You can also deploy SenseOn probe appliances at more locations to capture network traffic. Probe appliances can be physical or virtual. Like the main analysis appliance, they are configured to receive network traffic from at least one mirror or TAP.
Endpoint Agents
You deploy SenseOn endpoint agents on endpoint devices, for example laptops, desktops and servers. The endpoint agents are available for Windows, Mac and Linux operating systems.
From v7.0, the agent has two components, and one command installs the two components. The bootstrapper installs the sensor and keeps it updated. The sensor collects telemetry. Refer to Universal Sensor v7.
The agents send their data to the SenseOn analysis appliance over the local network on port 443. Endpoint agents can be at a remote site, away from the SenseOn analysis appliance. If so, they must connect through a site-to-site link, for example a VPN or MPLS.
Agents on v7.0 and later also get their sensor update packages from the analysis appliance, not from the SenseOn S3 buckets. Thus, these updates use the same path as telemetry. On each agent version, crash diagnostic uploads and Active Response file transfers go directly to S3. Thus, endpoints must still have that outbound path. For the applicable domains, refer to Connectivity Requirements.
Endpoint 360
Some endpoints are remote or do not have a site-to-site connection. Endpoint 360 lets the endpoint agents on these endpoints communicate with an on-premise appliance across different networks. When Endpoint 360 is enabled, the endpoint first tries a local or site-to-site connection. If that connection does not work, the endpoint sends its telemetry to the analysis appliance through a cloud-hosted bastion server.
Callback Connection
In a standard deployment, the analysis appliance makes an SSH connection to the SenseOn infrastructure. This connection lets SenseOn monitor the operation of the hardware and makes regular updates to the SenseOn platform easier. The telemetry data stays on the analysis appliance.
Architecture Diagram
The diagram that follows shows a multi-site deployment architecture. A SenseOn Solutions Engineer must design each on-site deployment.
