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, or relays, see their documentation:

If you plan to operate Deep Security in FIPS mode, see FIPS 140-2 support for additional requirements.

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)

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:
grep MemTotal /proc/meminfo
Minimum disk space 1.5 GB (200 GB recommended)
Operating system
  • Red Hat Enterprise Linux 7 (64-bit)
  • Red Hat Enterprise Linux 6 (64-bit)
  • Windows Server 2016 (64-bit)
  • Windows Server 2012 or 2012 R2 (64-bit)
  • Windows Server 2008 or 2008 R2 (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.x (only Core or Amazon RDS distributions)
  • Microsoft SQL RDS or Oracle RDS
  • Azure SQL Database (SaaS) multi-tenancy is not supported)

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 Express is supported in very limited deployments. See Microsoft SQL Server Express considerations for important details.
  • Trend Micro tests Deep Security with each Microsoft SQL Server service pack when it is released. Although not explicitly stated, the service packs for the Microsoft SQL versions listed above are also supported.
  • 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.

Deep Security Agent

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 11.1, see Deep Security Manager - Agent compatibility by platform.

Supported Deep Security features vary by platform.
On supported versions of Microsoft Windows, you must have at least Powershell version 4.0 to run the agent deployment script.

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. 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)