System requirements

Each part of a Deep Security deployment has its own system requirements.

Requirements vary by version. For older versions of Deep Security Manager, agents, relays, or virtual appliances, see their documentation:

Deep Security Manager

For a list of agents versions that are compatible with this version of Deep Security Manager, see Deep Security Manager - Agent compatibility by platform.

System component Requirements
Minimum memory (RAM) 8 GB RAM, which includes:
  • 4 GB for heap memory
  • 1.5 GB for the Java virtual machine
  • 2 GB for the operating system

Minimum RAM requirements depend on the number of agents that are being managed. (See 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:
grep MemTotal /proc/meminfo
Minimum disk space 1.5 GB (5 GB+ recommended)
Operating system
  • Red Hat Enterprise Linux 7 (64-bit)
  • Red Hat Enterprise Linux 6 (64-bit)
  • Red Hat Enterprise Linux 5 (64-bit)
  • Windows Server 2016 (64-bit)
  • Windows Server 2012 or 2012 R2 (64-bit)
  • Windows Server 2008 or 2008 R2 (64-bit)

Deep Security Manager for AWS Marketplace requires AWS Linux (64-bit).
Database
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2008
  • Microsoft SQL Server 2008 R2
  • Oracle Database 12c
  • Oracle Database 11g
  • PostgreSQL 9.6. Distributions that have been tested for use with Deep Security are:
  • Microsoft SQL RDS or Oracle RDS
  • Azure SQL Database (SaaS) (only with Deep Security Manager VM for Azure Marketplace)

Disk space required varies by the size of the deployment, data retention, and frequency of logging. See Sizing.

Minimum free disk space = (2 x database size) + transaction log

For example, if your database plus transaction log is 40 GB, you must have 80 GB (40 x 2) of free disk space for database schema upgrades. To free disk space, delete any unnecessary event log data and transaction logs.

  • Co-locate the database and all Deep Security Manager nodes in the same physical data center, with a 1 Gb link or better to ensure 2 ms latency or less between them.

  • Microsoft SQL Server 2008 and Microsoft SQL Server 2008 R2 are deprecated and will not be supported by future releases. Plan to migrate to a newer version of Microsoft SQL Server if you're using them.

  • Microsoft SQL Server Express is supported in very limited deployments. See Microsoft SQL Server Express considerations for important details.
  • Oracle Database Express (XE) is not supported.
  • Oracle container database (CDB) configuration is not supported with Deep Security Manager multi-tenancy.
  • Apache Derby, which provided an embedded database for proof-of-concept and testing in previous versions of Deep Security, is not supported anymore.
Web browser

Cookies must be enabled.

  • Firefox 52.0.1+
  • Microsoft Internet Explorer 11+ or Edge
  • Google Chrome 57+
  • Apple Safari 9+ (for Mac)
Monitor 1024 x 768 resolution at 256 colors or higher
Supported Deep Security Agent, Relay, or Virtual Appliance versions
  • Deep Security Agent, Relay, or Virtual Appliance 10.2
  • Deep Security Agent, Relay, or Virtual Appliance 10.1
  • Deep Security Agent, Relay, or Virtual Appliance 10.0
  • Deep Security Agent, Relay, or Virtual Appliance 9.6
Relays must be 64-bit. 32-bit relays are not supported.

For some platforms, the supported versions of Deep Security Agent listed above do not exist. Deep Security Manager 10.2 supports older agents on these specific platforms:

  • Deep Security Agent 9.0 on AIX 5.3, 6.1, 7.1, or 7.2
  • Deep Security Agent 9.0 on HP-UX 11.31
  • Deep Security Agent 9.0 on Solaris 10 Updates 4 - 10
  • Deep Security Agent 10.0 on Solaris 10 Update 11 (1/13) and Solaris 11

When using an older agent, you must go to Administration > System Settings > Update and select Allow supported 8.0 and 9.0 Agents to be updated. Otherwise Deep Security will conserve disk space by not downloading older update formats.

Deep Security Agent 10.2

System component Requirements

Minimum memory (RAM)

Total system memory

Windows

  • all protection enabled: 2 GB RAM (4 GB recommended)
  • Deep Security Relay feature only: 2 GB RAM (4 GB recommended)

Linux

  • all protection enabled: 1 GB RAM (5 GB recommended)
  • Deep Security Relay feature only: 1 GB RAM (4 GB recommended)
Requirements vary by OS version. Some versions may require less RAM. Less RAM is required also if you don't enable all Deep Security features.
Minimum disk space
  • all protection enabled: 1 GB
  • without anti-malware: 500 MB
  • Deep Security Relay feature only: 30 GB
Deep Security Relay must store packages for each of your agents' platforms. If you have many different platforms, more disk space is required.
Operating system

For compatible Docker and OS platforms, see Deep Security Manager - Agent compatibility by platform.

Supported Deep Security features vary by platform.

Deep Security Virtual Appliance

Because Deep Security Virtual Appliance uses the same protection modules as Deep Security Agents, if you import an update to the 64-bit Deep Security Agent for Red Hat, it may notify you that new software is available for the Virtual Appliance, like it does for Red Hat agents.

VMware does not support running nested ESXi servers in production environments. For more information, see the VMware Knowledge Base article.
System component Requirements
CPU

64-bit, Intel-VT or AMD-V present and enabled in BIOS

2 vCPU
Minimum memory (RAM)

4 GB RAM (varies by the number of VMs being protected)
Minimum disk space 20 GB
VMware
  • VMware vCenter 6.5 with ESXi 5.5, 6.0, or 6.5
  • VMware vCenter 6.0 with ESXi 5.5 or 6.0
  • VMware vCenter 5.5 with ESXi 5.5
  • VMware Tools on each ESXi host (including Guest Introspection)
  • VMware NSX Manager 6.2.4 or later
    VMware vSphere 6.5a is the minimum supported version with NSX for vSphere 6.3.0.

For details, see the VMware compatibility matrix.

For more information about VMware product interoperability, see VMware Interoperability Matrices.

If using a maximum transmission unit (MTU) of 9000 (also called "jumbo frames"), you must use VMware ESXi build 5.5.0.1797756 or later.
vSwitches vSphere Distributed Switch (vDS)
Guest operating system
Supported Deep Security features vary by platform. See Supported features by platform.

Windows

  • Windows Server 2016 (64-bit)
  • Windows Server 2012 R2 (64-bit) (on vSphere 5.5 - ESXi build 1892794 or higher)
  • Windows Server 2012 (64-bit) (on vSphere 5.5 only)
  • Windows Server 2008 R2 (64-bit)
  • Windows Server 2008 (32-bit and 64-bit)
  • Windows 10 (32-bit and 64-bit)
  • Windows 10 RS2 (32-bit and 64-bit)
  • Windows 8.1 (32-bit and 64-bit) (on vSphere 5.5 - ESXi build 1892794 or higher)
  • Windows 8 (32-bit and 64-bit) (on vSphere 5.5 only)
  • Windows 7 (32-bit and 64-bit)

Linux

  • Red Hat Enterprise Linux 7 (64-bit)
  • Red Hat Enterprise Linux 6 (32-bit and 64-bit)
  • CentOS 7 (64-bit)
  • CentOS 6 (32-bit and 64-bit)
  • Oracle Linux 7 (64-bit)
  • Oracle Linux 6 (32-bit and 64-bit) - Red Hat kernel
  • Oracle Linux 6 (64-bit) - Unbreakable Kernel
  • SUSE 12 (64-bit)
  • SUSE 11 SP1, SP2, SP3, SP4 (32-bit and 64-bit)
  • Ubuntu 16.04 LTS (64-bit)
  • Ubuntu 14.04 LTS (64-bit)
  • Debian 8 (64-bit)

Deep Security Notifier

If installed, Deep Security Notifier appears in the Windows system tray. If anti-malware is licensed and enabled, it indicates the statuses of Deep Security Agent, or the status of a VM protected by a Deep Security Virtual Appliance. Supported platforms include:

  • Windows Server 2016 (64-bit)
  • Windows Server 2012 or 2012 R2 (64-bit)
  • Windows Server 2008 R2 (64-bit)
  • Windows Server 2008 (32-bit and 64-bit)
  • Windows 10 (32-bit and 64-bit)
  • Windows 8.1 (32-bit and 64-bit)
  • Windows 8 (32-bit and 64-bit)
  • Windows 7 (32-bit and 64-bit)
  • Windows XP (32-bit and 64-bit)