Each part of a Deep Security deployment has its own system requirements.
Requirements vary by version. For older versions of
If you plan to operate Deep Security in FIPS mode, see FIPS 140-2 support for additional requirements.
For a list of agent versions that are compatible with this version of the manager, see Deep Security Agent platforms.
If you'd prefer, you can watch Deep Security 12 - DSM System Requirements and Sizing on YouTube.
|Minimum memory (RAM)||
Minimum RAM requirements depend on the number of agents that are being managed. See Deep Security Manager sizing.
On Linux, reserved system memory is separate from process memory. Therefore, although the installer's estimate might be similar, it will detect less RAM than the computer actually has. To verify the computer's actual total RAM, log in with a superuser account and enter:
|Minimum disk space||1.5 GB (200 GB recommended)|
If you are upgrading your Deep Security Manager and are using Windows Server 2008, we recommend that you add a new Deep Security Manager node on a supported operating system (see Run Deep Security Manager on multiple nodes). When that's complete, decommission the node running on Windows Server 2008.
See also Sizing.
If you'd prefer, you can watch Deep Security 12 - Agent System Requirements and Sizing on YouTube.
Requirements vary by OS version and the features that you enable. See Deep Security Agent and Relay sizing
For a list of all operating systems and agent versions that are compatible with Deep Security Manager 12.0, see Deep Security Agent platforms.
Because the appliance uses the same protection modules as agents, if you import an update to the 64-bit agent for Red Hat, it may notify you that new software is available for the appliance, like it does for Red Hat agents.
64-bit, Intel-VT or AMD-V present and enabled in UEFI.
The number of CPUs varies by the number of VMs being protected. See Deep Security Virtual Appliance sizing.
|Minimum memory (RAM)||
Varies by the number of VMs being protected. See Deep Security Virtual Appliance sizing.
|Minimum disk space||Varies by the number of VMs being protected. See Deep Security Virtual Appliance sizing.|
VMware NSX-T Data Center (NSX-T):
VMware NSX Data Center for vSphere (NSX-V):
VMware vCloud Director:
For details, see the VMware compatibility matrix.
For more information about VMware product interoperability, see VMware Interoperability Matrices.
Use vSS with NSX for vShield Endpoint, NSX Standard, and NSX Data Center Standard licenses. (These license types only support vSS.) Use vDS with all other NSX license types.
The VMs (guests) that will be protected by the virtual appliance have these requirements: