Network Probe Installation
SenseOn collects most of its network telemetry from its endpoint sensor. Most SenseOn customers do not use a network probe. Usually, a network probe only gives coverage for Operational Technology (OT) or legacy systems in a Data Centre.
If a probe is necessary, this guide gives the requirements to install a SenseOn physical network probe in your network infrastructure. Some endpoint devices cannot host the SenseOn Universal Sensor. These probes capture the network metadata of connections to and from those devices. To do this, a probe does Deep Packet Inspection of the traffic that a TAP or mirror sends to its capture interface.
For endpoint devices that host the Universal Sensor, Deep Packet Inspection on the endpoint itself captures the network metadata. This also lets SenseOn attribute the activity to the user identity and the process that manage the interactions. Hardware probes that you deploy do not duplicate the activity that the endpoint captures in this way.
Technical Architecture
SenseOn network probes communicate with the central analytic appliance through a secure connection on port 1194. The figure that follows shows this.

Firewall Requirements
The primary IP of a network probe must be able to connect outbound to the SenseOn master appliance on port 1194/tcp. SenseOn recommends that you make the same IP accessible on port 22/tcp (ssh) from a privileged access workstation or a management jumpbox. That is, make the IP accessible to your systems administrators if it is necessary to troubleshoot. Do not make it accessible to the full network. SSH access is not mandatory. SenseOn recommends SSH access for when you must troubleshoot and access to the virtual console is not possible or not wanted.
Physical Probes
SenseOn Required Information for a Physical Probe
Before delivery, SenseOn configures each probe to run in your environment. Each probe has three network interfaces: one management interface and two capture interfaces. Connect one or two of the capture interfaces to a network TAP or mirror port. The probe can then do deep packet inspection of the applicable network traffic. Connect the management port to a management network. The management port must be able to communicate with the SenseOn cloud analysis appliance endpoint on port 1194.
SenseOn must have the information that follows to configure and ship the probe. Collect the information and give it to your SenseOn representative:
- Management Interface (active interface, used to send telemetry to SenseOn platform)
- Static IP Address.
- Subnet Mask.
- Gateway IP Address.
- Public IP address of the probe (for SenseOn to allow list).
- Management interfaces are RJ45 Copper by default.
- Capture Interface (passive interfaces for network monitoring through SPAN/TAP)
- Remote switch vendor model (for example, Cisco, Juniper, or HP).
- Average sustained bandwidth of the link that the probe monitors (this is not the line speed).
- If the capture interface is copper:
- Interface type (RJ45/DAC).
- If the capture interface is fibre optic:
- Wavelength (860nm/1310nm).
- Speed (1G/10G/?).
- Fibre Type (OM1/OM2/OM3/OM4/OM5).
- Duplex (Full/Half).
- Shipping Details
- Contact Name.
- Contact Number.
- Contact Email.
- Address.
Probe Installation
After delivery, you must unpack the appliance, install it in a rack, and connect the cables. SenseOn configures the ports on the appliance to agree with the network requirements that you gave.

Diagram Rear Elevation
The diagram shows these connections:
- A. Power Supply. You must connect the two power supplies.
- B. Management interface. This interface already has the IP configuration that you gave.
- C. Capture interfaces. Connect these interfaces to the span/tap ports on the network switch.
A port that the diagram marks with a circle with a line through it is not in use and is not configured.
-
Unpack the Appliance. Unpack the appliance. Keep all shipping materials because it is possible that they will be necessary later. Your SenseOn Probe Appliance comes with a rack-mount rail kit. The kit is for installation in a 19” rack (standards ANSI/EIA 310-D-92, IEC 297 or DIN 41494).
-
Power Connectivity. Your SenseOn Probe has a redundant power supply. The power supply has two hot-swappable PSU components. For a hot swap to be possible, each of the two power supplies must get power from its own cord. Connect the two PSUs to a power supply.
-
Connect Network Cables. The SenseOn Probe appliance must have one connected interface for administration and one or more interfaces to capture traffic.
- Connect your management cable to port B.
- Connect the capture cable from your switches to ports C.
-
If you have only 1 capture interface, connect it to port C1.
-
Power On the Appliance. To set the appliance to on, push the power button at the right-hand side of the front of the appliance. This button is adjacent to the power symbol ⏻. When power is connected to the appliance, the button shows a green light.

- Confirm Connectivity. After you connect the appliance and set it to on, contact your Customer Success Manager or the SenseOn SOC. Use email or the Support Hub. SenseOn can then make sure that the connectivity is correct. NB: The management interface is password protected.
Virtual Probes
You can request a virtual probe from SenseOn through your Customer Success Manager. Alternatively, contact our 24/7 support team.
SenseOn builds the probe with the network connection settings that you specify. SenseOn supplies the probe as an Open Virtual Appliance (OVA) file.
When you request a virtual probe, SenseOn must have these details for the build:
- Internal IP address for the Management Interface. The IP address that the device will use on your network. This must be an internal address on your network. SenseOn recommends SSH access to this address. The appliance must be able to communicate outbound from this address to the SenseOn SaaS appliance. Refer to the Firewall Requirements section.
- Subnet Mask for the Management Interface.
- Default Gateway for the Management Interface.
- External IP Address. (likely a public IPv4 address on the edge firewall of your network).
- Location. The location for the deployment of the probe (for example, “Data Centre 01 in Sandford”, or “The Swan Hotel”).
- Platform. The virtualisation platform and version for the deployment of the probe.
- Bandwidth. Average sustained bandwidth of the link that the probe monitors (this is not the line speed).