Deep Security 10.1 has reached end of support. Use the version selector (above) to see more recent versions of the Help Center.
These requirements are for Deep Security 10.1. Requirements vary by version. For previous versions of Deep Security Manager, agents, relays, or virtual appliances, see the documentation for Deep Security 9.6 SP1 or earlier or for Deep Security 10.0.
- Deep Security Manager
- Deep Security Agent
- Deep Security Virtual Appliance
- Deep Security Notifier
- Docker support
|Minimum memory (RAM)||8 GB RAM, which includes:
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:
|Minimum disk space||1.5 GB (5 GB+ recommended)|
Deep Security Manager for AWS Marketplace requires AWS Linux (64-bit).
Disk space required varies by the size of the deployment, data retention, and frequency of logging.
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.
Cookies must be enabled.
|Monitor||1024 x 768 resolution at 256 colors or higher|
|Supported Deep Security Agent, Relay, or Virtual Appliance versions||
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
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.
Total system memory
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||
Deep Security Relay must store packages for each of your agents' platforms. If you have many different platforms, more disk space is required.
This section lists the supported operating systems for Deep Security Agent 10.1. For a list of other agent and platform combinations that are supported with Deep Security Manager 10.1, see Deep Security Manager - Agent compatibility by platform.
Supported Linux kernels vary by distribution. See Deep Security 10.1 Supported Linux Kernels.
A Deep Security Relay is usually only required by Deep Security AMI from AWS Marketplace, not Deep Security as a Service.
Deep Security Agent is designed to protect servers, not laptops.
To protect AWS WorkSpaces virtual desktop infrastructure (VDI) workstations, add the “Plus” application bundle instead. It includes Trend Micro Worry-Free Business Security.
To install Deep Security Agent on CentOS, use the Red Hat installer and package.
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.
64-bit, Intel-VT or AMD-V present and enabled in BIOS
|Minimum memory (RAM)||
4 GB RAM (varies by the number of VMs being protected)
|Minimum disk space||20 GB|
For details, see the VMware compatibility matrix.
For more information about VMware product interpoerability, see VMware Interoperability Matrices.
If using a maximum transmission unit (MTU) of 9000 (also called "jumbo frames"), you must use VMware ESXi build 184.108.40.2067756 or later.
|vSwitches||vSphere Distributed Switch (vDS)|
|Guest operating system||
Supported Deep Security features vary by platform. See Supported features by platform.
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.
- 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)
With each Deep Security release, Deep Security supports the last 2 stable releases of Docker Community Edition (CE) and Docker Enterprise Edition (EE). (See Announcing Docker Enterprise Edition.) We do not officially support Docker Edge releases, but strive to test against Docker Edge releases to the best of our ability.
Support for new stable Docker releases is introduced with each release of Deep Security. We recommend that you refrain from upgrading to the latest stable release of Docker until Trend Micro documents the support statements for the latest Deep Security release.
|Deep Security release||Supported Docker Releases|
|Deep Security 10.0||Docker v1.12, v1.13|
|Deep Security 10.1||Docker 17.03-ce, v1.13|
Deep Security is committed to supporting the environments, configurations, and platforms supported by Docker: https://docs.docker.com/engine/installation/.
Before deploying Deep Security into your target environment, you should ensure that Docker supports your target environment and platform configuration.