This document describes the requirements for installing and operating EPM Windows.
Requirements
To ensure proper operation:
- Add EPM Windows to your antivirus exclusions.
- Include EPM Windows as an exception in system hardening processes.
If you do not add EPM Windows to your hardening exceptions, it will not run normally.
Hardware specifications
| Sessions | CPU Cores | RAM (GB) | Storage (GB) |
|---|---|---|---|
| Up to 50 | 4 | 4 | - |
| 50 - 100 | 8 | 8 | 8 |
| 500 | 16* | 16 | 16 |
* Requires the pm.max_children parameter set to 10. For sessions exceeding 500, consult the Segura™ Platform support for tailored recommendations.
Network requirements
EPM Windows needs outbound access to the following DigiCert URLs. Allow them on your firewall and proxy with these settings:
| Setting | Requirement |
|---|---|
| Port | 80 (HTTP) |
| Proxy authentication | None. Configure the proxy to allow these URLs without user authentication. |
| SSL inspection | None. Exclude these URLs from SSL inspection and decryption. |
DigiCert URLs to allow:
http://crl3.digicert.comhttp://crl4.digicert.comhttp://ocsp.digicert.comhttp://cacerts.digicert.com
Segura™ application certificate requirements
EPM Windows 4.2.17 validates the Segura™ application certificate with the standard Windows rules. There is no option to ignore certificate errors. If the certificate fails any of the following requirements, the installer blocks the installation. The Name and Tenant name requirements below do not apply to a certificate issued by a private certificate authority (CA), such as an internal CA or the vault's own CA.
| Requirement | What to ensure |
|---|---|
| Name | The address in URL is in the certificate's DNS Subject Alternative Name (SAN) or Common Name (CN). For an IP address, the certificate must list it as an IP SAN. We recommend the host name. |
| Tenant name | On a multi-tenant Segura™ Platform, the certificate covers the tenant's name. Access to a specific tenant depends on the host name used in the connection (for example, <tenant>.domain.com); connecting by IP address always reaches the main tenant, and a hosts file alias does not replace that name. |
| Trusted chain | The issuing root certificate authority (CA) is in the Trusted Root Certification Authorities store of the local computer. Segura™ Platform sends the intermediate certificates. For a self-signed certificate, import the certificate itself on every workstation. |
| Validity | The certificate is valid today, and the workstation's date, time, and time zone are correct. |
| Port | HTTPS on port 443. EPM always uses 443, whatever port you type in URL. |
| Protocol | TLS 1.2 or TLS 1.3. |
If the installation is blocked, see:
- EPM Windows installer does not trust the Segura™ application certificate
- EPM Windows installer reports that the address is not in the Segura™ application certificate
- EPM Windows installer reports that the Segura™ application certificate is outside its validity period
- EPM Windows installer cannot negotiate a secure connection with Segura™ Platform
Dependencies
| Component | Requirement |
|---|---|
| .NET | Microsoft .NET 9 Desktop Runtime ≥ 9 and Microsoft .NET Framework 4.8 or higher. |
| Libraries | Microsoft Visual C++ Redistributable (2015-2022) x64 |
| Segura™ Platform | Version 4.2.17 or later. On earlier versions, the installer blocks the agent installation and update. Update Segura™ Platform before you update the agent. See EPM version compatibility for details. |
Supported platforms
EPM Windows supports the following Windows Server environments and x64 workstations:
| OS | Version | Architecture |
|---|---|---|
| Windows Server | 2022 (64-bit) | x64 |
| Windows Server | 2019 (64-bit) | x64 |
| Windows Server | Version 1803 and later (64-bit) | x64 |
| Windows Server | 2016 (64-bit) | x64 |
| Windows Server | 2012 R2 (64-bit) | x64 |
| Windows Server | 2012 (64-bit) | x64 |
| Windows | 8.1 (64-bit) | x64 |
| Windows | 10 version 1607 and later (64-bit) | x64 |
| Windows | 11 (64-bit) | x64 |
Unsupported OS versions
For unsupported OS versions:
- Visit the Segura™ suggestions portal.
- Submit an official support request.