System Requirements

Lists the hardware requirements for the ESA

The following table lists the supported components and their compatibility settings.

ComponentCompatibility
Application ProtocolsHTTP 1.0, HTTP 1.1, SSL/TLS
WebServicesSOAP 1.1 and WSDL 1.1
Web BrowsersMinimum supported Web Browser versions are as follows:
- Google Chrome version 129.0.6668.58/59 (64-bit)
- Mozilla Firefox version 130.0.1 (64-bit) or higher
- Microsoft Edge version 128.0.2739.90 (64-bit)

The following table lists the minimum hardware configurations.

Hardware ComponentsConfiguration
CPUMulticore Processor, with minimum 8 CPUs
RAM32 GB
Hard Disk320 GB
CPU Architecturex86
vCPUx86-64-v2

Note: Ensure that the vCPU supports x86-64-v2 configuration. Additionally, in the /proc/cpuinfo directory, the following flags must appear.
pni (SSE3), ssse3, sse4_1, sse4_2, popcnt, cx16, lahf_lm.

The hypervisor can hide these flags even when the physical CPU supports them. For instance, with an EVC or CPU baseline older than Nehalem these flags might not be visible. The virtualization admin must set a baseline that exposes them. This change only takes effect after a full power-off and power-on of each VM. A guest reboot is does not reflect the baseline changes.

Certificate Requirements

Certificates are used for secure communication between the ESA and protectors. The certificate-based communication and authentication involves a client certificate, server certificate, and a certifying authority that authenticates the client and server certificates.

The various components within the Protegrity Data Security Platform that communicate with and authenticate each other through digital certificates are:

  • ESA Web UI and ESA
  • Insight
  • ESA and Protectors
  • Protegrity Appliances and external REST clients

Protegrity client and server certificates are self-signed by Protegrity. However, these can be replaced by certificates signed by a trusted and commercial CA. These certificates are used for communication between various components in ESA.

Licensing Requirements

Ensure that a valid license is available before upgrading. After migration, if the license status is invalid, then contact Protegrity Support.

Last modified : October 19, 2026