Universal Sensor v7
Universal Sensor v7.0 is the current generation of the SenseOn endpoint agent. It replaces the single sensor package of v6.x and earlier with two components. The bootstrapper installs and maintains the sensor. The sensor itself collects telemetry and enforces endpoint protection.
SenseOn still supports agents on v6.x and earlier. This page calls them legacy agents. This page explains the difference between the two generations, what runs on a v7 host, and how to move a legacy host to v7.
The Two Components
| Component | What it does |
|---|---|
| bootstrapper | The install command installs it. It enrols the host with your tenant, and it downloads and installs the sensor. It keeps the sensor and itself up to date. It also refreshes the agent configuration from the SenseOn platform. |
| sensor | The agent itself. It collects telemetry, applies local detection rules and Endpoint Protection rules, and does Active Response actions. It does not update itself. |
The two components have separate version lines. Sensor versions are 7.0.x. The bootstrapper has its own version, which does not follow the sensor version. The agent version that Assets > Devices shows is the sensor version.
One install command. You install the bootstrapper, and the bootstrapper installs the sensor for you. There is no separate download for the sensor. Refer to Installing the Universal Sensor.
What Runs on a v7 Host
A v7 Windows host runs five SenseOn services: three from the bootstrapper and two from the sensor.
| Platform | From the bootstrapper | From the sensor |
|---|---|---|
| Windows | senseon-bootstrapper, senseon-broker, senseon-logger |
senseon-seed, senseon-epp |
| macOS | io.senseon.bootstrapper, io.senseon.broker, io.senseon.logger |
io.senseon.endpoint-sensor |
| Linux | senseon-bootstrapper, senseon-broker, senseon-logger |
senseon-seed |
On Windows, sensor versions before 7.0.40 run senseon-quarantine in place of senseon-epp.
Each component has its own directories. This is important when you set antivirus exclusions. The bootstrapper uses paths under senseon-bootstrapper, and the sensor uses paths under senseon-see. Antivirus and EDR Exclusions lists the two sets of paths.
For information about how these components collect, process and upload data, refer to How the Universal Sensor Works.
What Changed From Legacy
| Legacy (v6.x and earlier) | v7.0 and later | |
|---|---|---|
| Package installed | The sensor | The bootstrapper, which then installs the sensor |
| Enrolment | An install key file placed on the host | A token issued by the SenseOn platform and used once at install time |
| Windows services | senseon-seed, senseon-quarantine |
Five services, as listed in What Runs on a v7 Host |
| Sensor updates | The agent downloads update packages from the SenseOn S3 bucket | The bootstrapper downloads them from the SenseOn platform. The platform gets them for the endpoint. |
| Version control | Not available | Pinned, held or automatic per Device Segment |
Host requirements did not change between the generations. The supported operating systems and architectures are the same for the two generations. The CPU and memory figures are also the same. Endpoint Requirements gives these requirements.
There is one difference in connectivity, which comes from the change to sensor updates. If all of an estate is on v7.0 or later, the estate does not need access to the seev4 S3 bucket for updates. This is because update packages come from the platform. But on each agent version, crash diagnostic uploads and Active Response file transfers still go to S3. Thus, the wider S3 rule is still necessary. Connectivity Requirements covers the two rules.
Moving a Legacy Host to v7
To move to v7, you do a new installation, not an in-place upgrade. Use the current install command to install the bootstrapper on the host. The bootstrapper then gets and installs the v7 sensor. Refer to Installing the Universal Sensor.
Legacy agents no longer update themselves. By default, automatic updates are off for v6.x and earlier. Thus, a legacy host stays on its version until you move it to v7. While the host stays on that version, there is no effect on protection and telemetry.
Keep hosts on bootstrapper 1.0.20 or later. On Windows, an upgrade of a host from bootstrapper 1.0.12 can stop the sensor. The upgrade can also queue the removal of the sensor for the next administrator logon, and not keep the sensor in place. From 1.0.20, the bootstrapper repairs this problem during the upgrade. It clears the queued removal and starts the services of the sensor again. A new installation of 1.0.20 or later over an affected host does the same.
If a host has a connection to the SenseOn platform that works, the host updates its own bootstrapper. Thus, this problem is mainly important where a package is cached and deployed again, for example in an MDM package or a golden image. Refresh each stored copy of the bootstrapper package so that it is 1.0.20 or later.
Removing SenseOn From a v7 Host
You must remove the two components. While the bootstrapper is installed and runs, it installs the sensor again if the sensor is missing. Usually, this occurs in approximately ten minutes. Thus, if you remove only the sensor, the removal does not last. Also, you cannot enrol the device again until the bootstrapper is removed. Follow Uninstalling SenseOn, because the steps and their sequence are different for each platform.
Related Reading
- Endpoint Requirements: supported operating systems, connectivity, exclusions, proxy configuration
- Installing the Universal Sensor: the install command for each platform
- How the Universal Sensor Works: collection, data flow, security model and the update model
- Uninstalling SenseOn: how to remove the two components
- Troubleshooting: step-by-step checks when an endpoint does not install, run or report
- Device Segments: where you configure version control for each segment