Deep Security

The following section lists all Trend Micro products/versions that are considered current and are fully supported by Trend Micro, along with milestone dates (End-of-Sale and End-of-Life) that have been formally announced.Please refer to Trend Micro’s latest End-of-Life Policy for more information on milestone definitions and standard timelines. You can also view the products/versions that have reached End-of-Life in the past 12 months here.

The following section lists all Trend Micro products and versions that have reached End-of-Life (EOL) status (formerly End-of-Support or EOS) in the last twelve (12) months and are no longer actively supported by Trend Micro. If the product/version you are looking for is not listed below, it is either still supported or is an older version that has been End-of-Life for more than 12 months.Please refer to Trend Micro’s latest End-of-Life Policy for more information on milestone definitions and standard timelines. 

Trend Micro has received reports of compatibility issue between Trend Micro Endpoint solutions and Windows 11 Microsoft Update (KB5052093). Affected endpoints would show “Bad image” popup errors:  Dism.exe - Bad ImageC:\WINDOWS\system32\tmumh\20019\AddOn\8.55.0.1333\TmUmEvt64.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000428. Dism.exe - Bad ImageC:\WINDOWS\system32\tmumh\20019\TmMon\2.9.0.1205\tmmon64.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000428.

In Windows DSA 20.0.0.8438, 20.0.1.690 and 20.0.1.700, the following error may be encountered:"Behavior Monitoring (BM) Exception Failure" When a target path is added to the Behavior Monitoring exception list, it will forcibly be converted to lower case. However, if the target path includes uppercase characters, the comparison of paths will not match. As a result, the Behavior Monitoring exception will not function properly.

Hypervisor-based protection using Anti-malware and System Security (Integrity Monitoring) are currently unavailable for Linux platforms.Hypervisor-based Network Security (Intrusion prevention, Firewall, and Web Reputation) is available to protect both Windows and Linux platforms using NSX and vCNS.Deep Security Agents (DSA) are also available to protect a wide variety of guest virtual machines. For more information, refer to the following documents:       •  Deep Security 20.0 Supported Features by Platform       •  Deep Security 12.0 Supported Features by Platform       •  Deep Security 11.0 Supported Features by Platform       •  Deep Security 10.0 Supported Features by PlatformEnsure your VMware tools meet the requirements and compatibility provided by VMWare.       •  ESXi vs VMware Tools Compatibility Table       •  VMware Tools Release NoteFor feature releases such as Deep Security versions 11.1, 11.2, 11.3, and 12.5, please refer to his article: Deep Security Feature Releases and VMware Compatibility Matrix.

This article contains the list of Deep Security supported versions related to Windows Server Core.

This article provides information about the deprecation of Amazon Linux 2 for Deep Security on AWS Marketplace, lists the end-of-life (EOL) dates, and steps to be performed by customers who use Amazon Linux and Amazon Linux 2 operating systems.

Learn all about the major systems that you can use in the redesigned Trend Micro Business Support Portal.

After activating agentless protection, a virtual machine (VM) may go from "Managed (Online)" to "Anti-Malware Engine Offline". This article consolidates the components that need to be checked as well as the other factors that may affect the functionality.Before going further, it is recommended to identify first how many VMs are affected and if they are running on the same or different ESXi host(s). This can help isolate if the issue is on endpoint, host, cluster, or vCenter level. The following must also be checked: •  VMware and Deep Security compatibility. The vCenter, ESXi, and NSX Manager version should be supported. See compatibility matrix to verify.•  Relay Group. There should be at least one (1) functional member of the relay group. It can be checked from the Deep Security Manager (DSM) console and then go to Administration > Relay Management > Relay Group. 

After turning on the DSA firewall, network traffic is blocked. As a client, connecting to a website may work properly but the outgoing connection is blocked by the DSA firewall. As a server, on the other hand, you may launch a web server but all incoming request connections are blocked, also by the DSA Firewall.