This document describes how Segura® Platform and the EPM agents enforce version compatibility with each other, and what to expect if either side is running a version from before this enforcement existed.
Current policy (version 4.2.14 and later)
Starting with version 4.2.14, both the EPM agents and Segura® Platform enforce a minimum-version check.
| Item | Description |
|---|---|
| When it runs | Before installing or updating an agent. |
| What it checks | The agent asks Segura® Platform for its current minimum required agent version, then compares it against the version being installed. |
| Enforcement direction | An agent version below the minimum required is blocked. An agent version newer than the minimum required is never blocked. |
| Requirement | Both the agent and Segura® Platform must be on version 4.2.14 or later for the check to apply. |
The required minimum version is not a fixed number. Segura® Platform publishes its current minimum whenever it is queried, so the requirement can change after Segura® Platform is updated. Check the installer's result at install time rather than relying on a previously seen value. Here is the compatibility table:
| EPM Agent version | Segura® application minimum version |
|---|---|
v4.2.14.x |
v4.2.14.x |
Before version 4.2.14
Versions before 4.2.14 have no compatibility check. An agent of any version can attempt to register with a Segura® Platform of any version. An incompatible combination is not blocked upfront; it can fail unpredictably during registration instead.
If you are running an EPM deployment from before version 4.2.14, update both the agent and Segura® Platform to version 4.2.14 or later to get automatic compatibility checking.
Supported agents
The version-compatibility check applies to all EPM agent types:
- EPM Windows.