<> Trend Micro Incorporated September 18, 2018 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Readme for Trend Micro (TM) Deep Security Agent 11.0 Update 2 for Windows, and Deep Security Notifier 11.0 Update 2 for Windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Deep Security Agent Platforms: - Windows Server 2016 or 2016 RS3 (64-bit) - Windows Server 2012 or 2012 R2 (64-bit) Full Server or Server Core - Windows Server 2008 R2 (64-bit) - Windows Server 2008 (32-bit and 64-bit) (*) - Windows 10, 10 TH2, 10 RS2, 10 RS3, or 10 RS4 (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) (*) - Hyper-V on Windows 2016, 2012 R2, 2012, 2008 R2, 7, and 8.1 (**)(***) (*) Deep Security Relay is supported only on 64-bit versions. (**) There is no agentless solution for Windows Hyper-V. The Agent installed on the Hyper-V hypervisor will only protect the hypervisor itself. In order to protect guest images running on Hyper-V an Agent must be installed on each Hyper-V guest. See Knowledge Base article http://esupport.trendmicro.com/solution/en-us/1103857.aspx for more information. (***) Deep Security Relay is not supported on these platforms. Not supported: - Windows Server 2003 SP2 or R2 SP2 - Windows Server 2003 SP1 - Windows Server 2008 Core - Windows Server 2016 Core - Microsoft Virtual Server 2005 R2 SP1 - Hyper-V on Windows 8 - Windows XP (32-bit and 64-bit) Date: September 18, 2018 Release: 11.0 Update 2 Build Version: 11.0.0-390 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This product is subject to the terms detailed in the license agreement and copied to the install directory. For more information about the Trend Micro suite of Deep Security products, visit our website at: https://www.trendmicro.com/en_us/business/products/hybrid-cloud.html Download the latest version of this readme from the Deep Security Help Center, Software page: https://help.deepsecurity.trendmicro.com/software-feature-releases.html Trend Micro is always seeking to improve its documentation. If you have questions, comments, or suggestions about this or any Trend Micro documents, please contact us at docs@trendmicro.com. Your feedback is always welcome. Contents =================================================================== 1. About Deep Security 11.0 1.1 Overview of This Release 1.2 Who Should Install This Release 2. What's New 2.1 Enhancements 2.2 Resolved Known Issues 3. Documentation Set 4. System Requirements 5. Known Incompatibilities 6. Known Issues in Deep Security Agent 11.0 7. Release History 8. Files Included in This Release 9. Contact Information 10. About Trend Micro 11. License Agreement 12. Third Party Software =================================================================== 1. About Deep Security 11.0 Update 2 ======================================================================== 1.1 Overview of This Release ===================================================================== Deep Security Agent 11.0 Update 2 contains feature enhancements as well as bug fixes. For a list of the major changes in Deep Security 11.0 Update 2, please see the "What's New" section of the Installation Guides, which are available for download from the Trend Micro Download Center. 1.2 Who Should Install This Release ===================================================================== You should install this release if you are currently running Deep Security 9.6 Service Pack 1 Patch 1, Deep Security 10.0 Update 8, Deep Security 10.1, Deep Security 10.2, or Deep Security 10.3. All new Deep Security users should install Deep Security 11.0. 2. What's New ======================================================================== 2.1 Enhancements ===================================================================== The following enhancements are included in this release: Enhancement 1: [DSSEG-2488] Anti-Malware Scan Engine can be displayed and has the option to enable or disable an Anti-Malware update. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enhancement 2: [DSSEG-2703] A report is created when Windows Anti-Malware encounters an install/upgrade failure or error because of an interop or timing issue. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2.2 Resolved Known Issues ===================================================================== This release resolves the following issues: Issue 1: [DSSEG-2735/SEG-34502] When a TCP connection was established with the same tuples as a previously tracked one, the network engine could set the connection track to an incorrect status. This sometimes happened on a busy server where rapid connections reused a recycled connection. The network engine treated it as an "Out of connection" error and dropped the packet. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-2408/SEG-29915/00863552] Deep Security Agent would sometimes crash when collecting truncated logs from the kernel module. Solution 2: The issue is resolved in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 3: [DSSEG-2566] When firewall or intrusion prevention rules were assigned to specific network interfaces, it sometimes did not trigger network configuration recompilation, and the Deep Security Agent Network Engine wouldn't load the expected configuration. Solution 3: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 4: [DSSEG-2466/SEG-30270/SF00900562] When a host machine's locale was not set to UTF-8, the Deep Security Agent installation would not complete and the agent could not be activated. Solution 4: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 5: [DSSEG-2417/00817382/SEG-26134] When certain Intrusion Prevention rules for Oracle Database Server were enforced, the network filter driver crashed the computer. Solution 5: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3. Documentation Set ======================================================================== In addition to this readme.txt, the documentation set for this product includes the following: - Information formerly contained in the Deep Security Installation Guides and Deep Security Administrator's Guide is now available on the Deep Security Help Center https://help.deepsecurity.trendmicro.com/11_0/on-premise/Welcome.html and includes: -- product overview, deployment plan, installation steps and basic information intended to help you smoothly deploy Deep Security. -- post-installation instructions on how to configure the settings to help you get Deep Security "up and running". Also includes instructions on performing other administrative tasks for the day-to-day maintenance of Deep Security. - You can easily search the Help Center content or get context-sensitive help from your Deep Security Manager. 4. System Requirements ======================================================================== For a complete list of the System requirements, please refer to the Deep Security Help Center: https://help.deepsecurity.trendmicro.com/11_0/on-premise/Get-Started/Install/system-requirements.html 5. Known Incompatibilities ======================================================================== 1. Resonate Load Balancer (5.0.1) Deep Security Agents Affected: All Issue: Environments in which the Resonate load balancing software is installed may experience a loss of Resonate functionality when the Deep Security Agent is installed. Resolution: Restart the Resonate Central Dispatch Controller services. 2. Trend Micro Client Server Messaging Security for SMB Deep Security Agents Affected: All Issue: Connectivity issues have been noted when running versions of Trend Micro Client Server Messaging Security for SMB that are older than Version 3.5 Build 1113. Resolution: Upgrade Trend Micro Client Server Messaging Security for SMB to Version 3.5 Build 1138 or higher. 3. Realtek RTL8169/8110 Family Gigabit Ethernet NIC Deep Security Agents Affected: All Issue: Issues have been noted when using Version 5.663.1212.2006 of the Realtek Gigabit Ethernet NIC Resolution: To resolve these issues, upgrade the driver to the latest version. 4. Intel(R) PRO/100+ Dual Port Server Adapter Deep Security Agents Affected: All Issue: Issues have been noted when using Intel NIC cards with driver versions lower than 8.0.17.0 Resolution: To resolve the issue, upgrade the driver to version v8.0.19 or higher. 5. Wireshark Deep Security Agents Affected: All when installed in Windows 7, 2008 and 2008 R2. Issue: When Wireshark is monitoring packets they are incorrectly presenting outgoing packets through NdisFilterRecv packet which is the path for incoming packets. Resolution: Use Microsoft Network Monitor instead when doing packet capture. 6. Known Issues in Deep Security Agent 11.0 ======================================================================== - The Deep Security Agent query script, dsa_query.cmd or dsa_query.sh, sometimes fails. (DSSEG-2173/SEG-23387) - After a relay is upgraded successfully and all software packages are imported into Deep Security Manager, users should wait at least ten minutes before upgrading agents. Otherwise, a "Software Update: Agent Software Upgrade Failed" error may occur. (DS-23195) - On a Windows 10 computer with Microsoft Application Virtualization (App-V) enabled, if you enable Deep Security Anti-Malware protection, the Deep Security Agent may display the message "A computer reboot is required to complete an Anti-Malware cleanup or restoration task". The App-v client service must be restarted to enable Anti-Malware scanning on the virtual drive. (DS-22761) - If you activate a Deep Security Agent on an AWS WorkSpace and apply a policy that uses the default Firewall rules, the workspace will become "unhealthy". You must alter the policy to allow access to the ports required by WorkSpaces. (DS-17460) - Disabling the relay feature on a Windows 10 agent can sometimes take more than ten minutes to complete. (DS-18685) - When an agent with relay functionality is in the "Enabling" or "Disabling" state, the operation cannot be canceled. If the operation hangs in either of these states, the agent with the relay functionality needs to be deactivated and then reactivated. (DS-16407) - A new Anti-Malware module was introduced in Deep Security 10.2 for Windows. If Anti-Malware scans are enabled on a Windows platform, a system reboot is required after upgrading the Deep Security Agent from a pre-10.2 version. Before the system reboot, you may see intermittent Error alert(s) transactions that you can ignore. For more information, see: http://esupport.trendmicro.com/solution/en-US/1118752.aspx. (DS-14544) - Advanced threat detection (machine learning) does not detect threats on USB storage devices on Windows 7. (DS-17536) - Application Control is not supported with 32-bit versions of Deep Security Agent. However, Deep Security 10.1 and 10.2 would download the Application Control component to 32-bit agents even though it did not work. The presence of this component can cause an upgrade failure when upgrading the Deep Security Agent to version 11.0. To fix this issue: 1. In Deep Security Manager, disable Application Control for the agents that need to be upgraded to 11.0. 2. As a user with the appropriate administrative access, remove the Application Control security module component files from the agent installation folder (on Windows, the installation folder is typically c:\Program Files\Trend Micro\Deep Security Agent). You will need to remove: /dep/ac.deplua /lib/ac.dll /ext/ac.dse /ext/ac.dse.version 3. Restart the agent software by performing a restart of the agent node. 4. Upgrade the agent package to Deep Security Agent 11.0. (DS-22499/DS-15695) - Application Control build inventory, which happens after enabling Application Control, will take longer to finish on Windows Server 2008 R2 compared to other supported platforms. (DS-13120) - If you have created an Application Control block rule for a batch file or PowerShell script, you will not be able to copy, move, or rename the file using its associated interpreter (powershell.exe for PowerShell scripts or cmd.exe for batch files). (DS-13253) - Application Control is not compatible with Windows Defender. Running both can result in severe performance impacts. However, if both Application Control and Anti-Malware are enabled, then Deep Security will automatically disable Windows Defender for normal operation. (DS-12890) - Application Control build inventory, which happens after enabling Application Control, will be slower when TiWorker.exe is running. TiWorker.exe is the Windows Modules Installer Worker, which is used when performing Windows updates. (DS-14313) - When Application Control is configured to "Block unrecognized software until it is explicitly allowed", you will not be able to upgrade or uninstall the Deep Security Agent on that computer. To unblock the procedure, enable maintenance mode. (DS-14369) - In rare circumstances, Anti-Malware could go offline after the Deep Security Agent finishes upgrading. When you check the Windows Application events log, it will show that Microsoft-Windows-RestartManager has stopped the Anti-Malware Solution Platform (Anti-MalwareSP) and Trend Micro Solution Platform service, and the service will need to be restarted. See:  https://success.trendmicro.com/solution/1117465 for more details. (DS-11331) - When the Anti-Malware protection module is installed by enabling Anti-Malware protection on a Deep Security Agent for the first time on Windows 2016, the Windows Defender service will be stopped, a reboot message will popup on Windows 2016 and a reboot-required event will be displayed on the Deep Security Manager. After this first time, changing the computer's policy to disable and re-enable Anti-Malware will not show the reboot-required messages. It is strongly recommended to reboot Windows Server 2016 if the Windows Defender service is stopped by the Deep Security Agent Anti-Malware policy. (DS-10389) - Customers should only run one Trend Micro Anti-Malware module on a protected computer. When Deep Security Agent is to be deployed, administrators should ensure that other Trend Micro products such as OfficeScan are uninstalled. If the Deep Security Agent Anti-Malware module goes offline because another product is installed you will need to remove OfficeScan and reinstall the agent. One exception to this Trend Micro Endpoint Sensor (TMES), which is compatible with the Deep Security Agent Anti-Malware feature enabled on Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012R2 only. (DS-2846) - Windows XP Embedded is not a supported Deep Security Agent platform in this version. Customers running Windows XP Embedded should continue to use the latest 9.6 SP1 Agent version. (DS-10558) - For Windows Server 2008 operating in an environment without internet connection, when upgrading Deep Security Agent 9.x Agents with Anti-Malware policy assigned to Deep Security Agent 10.0 or above then the Agent may successfully upgrade but the Anti-MalwareSP (Anti-Malware protection) version still remains at v2.6.x. The computer status on Deep Security Manager and Deep Security Agent Notifier will show Anti-Malware offline, and the following error message is generated: Anti-Malware Windows Platform Update Failed. This is because the Trusted Root Certificate cannot be verified without an internet connection. Troubleshooting: 1. Do not attempt to uninstall the Deep Security Agent. (If you tried this and the Anti-Malware module could not be removed, then you should re-install the original version of the Agent before proceeding. Hint: To find the version number of yourprevious Deep Security Agent, log in to the Deep Security Manager and search the Computer's Events for "Update: Summary Information") 2. Reactivate the Deep Security Agent from Deep Security Manager, and the Deep Security Agent should return to Managed (Online) 3. Obtains and import the certificate "VeriSign Class 3 PublicPrimary Certification Authority - G5" (DS-9981) - While upgrading Deep Security Agent 10.0 or higher from a previous version, the Anti-Malware module may fail to upgrade because the certificate of dsuam.exe (which is processing Anti-MalwareSP upgrade) cannot be verified. The following event would be received: Event ID 935 Software Update: Anti-Malware Windows Platform Update Failed. This issue impacts systems on Windows Server 2008, and in an environment disconnected from the internet. Other OSs (such as Windows 7 and Server 2008 R2 and above) do not have this issue. The problem is that legacy and disconnected systems cannot download the new root VeriSign certificate from the internet. The certificate is required to perform the agent upgrade with Anti-Malware. This is a security enhancement to ensure only certified applications can process Anti-Malware upgrades.) Systems Administrators in a disconnected environment are recommended to ensure the availability of "VeriSign Class 3 Public Primary Certification Authority - G5" in "Trusted Root Certification Authorities". Workaround (if Deep Security Agent is not upgraded): 1. Download verisign_g5.cer and save it to machine to upgrade or download G5 root certificate from https://www.symantec. com/theme/roots 2. Log in and run command as system administrator, and run: certutil -addstore "Root" verisign_g5.cer 3. For systems as XP and 2003, please use MMC.exe console, add "Certificates" snap-in, and import certificate to "Trusted Root Certification Authorities". Troubleshooting (if Deep Security Agent is already upgraded to 11.0 but Anti-Malware failed to upgrade): 1. Re-install the old version of Deep Security Agent. To find the version of previous Deep Security Agent, please search "Update: Summary Information" from "Events" of the machine from Deep Security Manager. 2. Reactivate Deep Security Agent from Deep Security Manager. Deep Security Agent should return to Managed (Online). 3. Import "VeriSign Class 3 Public Primary Certification Authority - G5" (DS-9020) - Anti-Malware endpoint correlation on Windows does not generate hash values. When Anti-Malware File Hash Calculation is enabled, the following cases may still not generate related hash values: 1. Multiple Spyware detections 2. Trojan detections with multiple files cleaned 3. Endpoint Correlation detection 4. Windows XP SP2 doesn't natively support SHA256 and no SHA256 value will be generated 5. Anti-exploit may calculate the hash values of victim file instead of malware file Note: the Anti-exploit detection often is a victim file instead of a malware file; the hash values of the victim must be carefully used. (DS-9573) - Anti-Malware Memory Scan is not supported on Windows XP and 2003 x64 platforms. (DS-8630) - With a Deep Security Agent running on Windows 7, when the Network Directory Scan function is enabled in the Real-Time Scan configuration, when scanning a network folder, if a virus is detected, the Deep Security Agent may show some "clean failed" (delete failed) events. This is caused by OS behavior when accessing network files on Windows 7 platforms only. (DS-4783) - Under certain circumstances, the Deep Security Agent may fail to upgrade while Windows Process Explorer tool is running on the Deep Security Agent machine. This issue is isolated to the following conditions only: 1. An Administrator is not logged in to the Deep Security Agent computer 2. UAC (User Access Control) is enabled on the Deep Security Agent computer 3. Process Explorer tool is running (and is not being run by the Administrator account) (DS-5788) - When upgrading from Deep Security Agent 9.6 SP1 Patch 1 U5 with Anti-Malware enabled to Deep Security Agent 10.2 on Windows 8, Windows 8.1, Windows 10, Windows 10 TH2, Windows 10 RS1, Windows 2012, Windows 2012 R2, or Windows 2016, a reboot will be required to complete the upgrade. When upgrading from other earlier versions of Deep Security Agent on Windows platforms, a reboot may also be required. A "Computer Reboot Required" event will be displayed on the Deep Security Manager and popup notification on the host will be displayed if a reboot is necessary. (DS-3590) - In the Windows Control Panel "Notification Area Icons" settings, Deep Security Notifier will remain listed even after uninstalling Deep Security. This is a known issue in Windows that also affects other products. (DS-1300) - Full Windows administrative privileges are required to install the Agent to a non-default installation path. (DS-1191) - In some circumstances, the Windows Deep Security Agent uninstallation process may hang if there are quarantined files on the system. Workaround Steps: 1. Cancel this uninstallation 2. Delete quarantined files manually. Quarantine files are stored at C:\ProgramData\Trend Micro\Anti-MalwareSP\quarantine or C:\Documents and Settings\All Users\Application Data \Anti-MalwareSP\quarantine. 3. Uninstall the Deep Security Agent (DS-874) - The Deep Security Notifier icon may sometimes disappear on Windows 10. (DS-1301) - When a virtual machine is added through vCloud connector, after vMotion from a protected ESXi host to an unprotected ESXi host, the virtual machine will not go from combined mode to Agent-only protection. (DS-558) - When a virtual machine is added through vCloud connector, after vMotion from unprotected ESXi host to a protected ESXi host, the virtual machine will not go from Agent-only protection to combined mode. (DS-557) - Full Windows administrative privileges are required to install the Agent to a non-default installation path. (DS-1191) - On Windows Agents, if the Anti-Malware (Anti-MalwareSP) service is still starting up when the Deep Security Manager sends a new policy switching Smart Scan on/off, it will return the warning message: "Security Update: Pattern Update on Agents/Appliances Failed". NOTE: This warning is not an Anti-MalwareSP offline/failure. The Anti-Malware protection is still active with the warning. Administrators need to manually clear the warning since the Deep Security Manager will not clear it automatically. (DS-4101) - The Deep Security Notifier system tray icon may not appear after installation if multiple users are logged in to Windows. Logging off and logging back in or manually executing the notifier.exe will make the system tray icon appear. [DS-602] - Deep Security Agent does not support Code Integrity checking on Windows 10 hosts (32- or 64-bit platforms). Enabling Code Integrity checking on Windows 10 hosts with the Deep Security Agent installed may cause a Blue Screen error. [883/254] - When a virtual machine is added through vCloud connector, after vMotion from a protected ESXi host to an unprotected ESXi host, the virtual machine will not go from combined mode to Agent-only protection. [558] - When a virtual machine is added through vCloud connector, after vMotion from an unprotected ESXi host to a protected ESXi host, the virtual machine will not go from Agent-only protection to combined mode. [557] - In rare circumstances, when enabling Anti-Malware feature on Deep Security Agent running on Windows XP, the Anti-MalwareSP service installation may fail with the error message "Anti-MalwareSP error code (0x20ff0000)". As a workaround, reinstall the Deep Security Agent. [29436] - On Windows 32-bit platforms, there is a configuration limit of 20MB because of the smaller kernel memory available on these platforms. The event "Agent configuration package too large" may appear if there are too many rules enabled on the Deep Security policy being assigned. This may be fixed by trimming down the Intrusion Prevention rules strictly to Recommended for Assignment only. [27162] - If the Integrity monitoring feature in Combined Mode is disabled, the Deep Security Notifier status will display it as Not Capable instead of Not Configured. [29403] - Deep Security Azure Connector does not identify virtual machines created by Azure Resource Manager a.k.a ARM VM (v2). Deep Security Agent installed in ARM VM will not be included in Azure connector but in the normal computer list. This limitation will have no impact on security features provided by Deep Security. [29630] - Deep Security Agent could not convert shift-jis encoded characters to UTF-8. Therefore, any folders named with shift-jis encoding will be skipped during Integrity Monitoring scanning. [28879] - If agentless Anti-Malware real-time protection is turned off, the notifier will not get any status updates from the appliance. It will then turn off Antivirus protection in the Windows Action Center. [29230/29574] - When you deactivate the Deep Security Virtual Appliance or agentless protection, the notifier will not be able to get any status from the Deep Security Virtual Appliance. The notifier knows that Anti-Malware is not working so it will turn it off in the Windows Action Center. It does not know the status of the Firewall so it will leave the Firewall status in the Windows Action center in its last known state. [29230/29574] - The Deep Security Notifier installed in the virtual machines should be upgraded to correctly display the status of protection especially in Combined Mode. [28557] - Deep Security does not support switching the Windows 2012 server mode between Server Core and Full (GUI) modes after the Deep Security Agent is installed. [28481] - If you are using Server Core mode in a Hyper-V environment, you will need to use Hyper-V Manager to remotely manage the Server Core computer from another computer. When the Server Core computer has the Deep Security Agent installed and Firewall enabled, the Firewall will block the remote management connection. To manage the Server Core computer remotely, turn off the Firewall module. [28481] - Hyper-V provides a migration function used to move a guest VM from one Hyper-V server to another. The Deep Security Firewall module will block the connection between Hyper-V servers, so you will need to turn off the Firewall module to use the migration function. [28481] - Deep Security Agent does not support scanning a mounted network folder (SMB) on the following Windows platforms: Windows 2012 Server R2 (64-bit) Windows 2012 Server (64-bit) Windows 8.1 (32/64-bit) Windows 8 (32/64-bit) [22016] - Deep Security Notifier when using agentless protection in NSX environment will not work if only Web Reputation is turned on. Agentless Anti-Malware must be enabled for Deep Security Notifier to work. [22210] - The relay feature uses TCP port 4122. When enabling the relay feature, make sure TCP port 4122 is allowed in any Firewall being used. [22749] - The Deep Security Agent Anti-Malware files and folder might not get removed on upgraded agents when uninstall is performed. This only happens when Anti-Malware feature is enabled then disabled before upgrading and the Anti-Malware feature was never enabled before uninstalling. When this happens, follow manual uninstall procedures in http://esupport.trendmicro.com/solution/en-US/1096150.aspx to completely uninstall. [21716] - Some Anti-Malware events are not generated when the built-in Windows decompress tool. This issue does not happen when using 3rd party decompress tool. [23055] - Windows Add/Remove Programs or Programs and Features doesn't show the exact version of the Deep Security Agent. Deep Security Agent version consists of major.minor.sp-build but Windows only show them as major.minor.build. [21990] - CPU usage control in Scan for Integrity may not work after a reboot. Rebuilding the Integrity Baseline or reactivation will fix this. [20725/20563] - During Anti-Malware realtime scan, the Deep Security Agent may sometimes produce multiple Delete Failed events even when the deletion was successful. This rarely occurs but it happens when the file is being locked by other processes temporarily. [23520] - When upgrading Deep Security Agent on Windows 2012, an error message saying "Service ‘Trend Micro Deep Security Agent’(ds_agent) could not be installed. Verify that you have sufficient privileges to install system services." may appear. This may be fixed by running Windows Update troubleshooter in http://support.microsoft.com/kb/910336. [23728] - Deep Security Notifier will show the status of Intrusion Prevention as Not Configured if it has no rules assigned, even if it's On. [22938] - Some security components of Deep Security Agent with Relay feature enabled may get removed unexpectedly after an update. As a workaround, retry the security update. [24004] - Upgrading to Deep Security Agent 9.5 or later by running a deployment script on an AWS instance that already has Deep Security Agent 9.0 will not work. Deep Security Agent upgrade must be done from the Deep Security Manager. [25598] - After Deep Security Agent upgrade, the event "Abnormal Restart Detected" may appear. The upgrade is not affected by this event and may be safely ignored. Do Clear Warnings and Errors and perform a Check Status to reflect the actual status of the agent. [26619] - In some cases, a laptop computer has the "Microsoft Virtual Wi-Fi Miniport Adapter" option enabled. Such devices, used for creating Wi-Fi hotspots (ad hoc networks) through the wireless adapter, would enable both the real device for the true wireless connection and the "Microsoft Virtual Wi-Fi Miniport Adapter" for the ad hoc connections, with the same MAC address. This triggers Deep Security Agent on such laptop computers to request for an interface update on every heartbeat. [17502] - In a cloud provider environment if the "Enable regular synchronization with Cloud Provider" option is disabled, changing the Deep Security Agent hostname will disrupt the communication between Deep Security Manager and Deep Security Agent. Trend Micro strongly recommends keeping the "Enable regular synchronization with Cloud Provider" option ON. [15608] - On Windows Server 2008 and Windows Server 2012, after installing Deep Security Manager with a co-located Relay, the Deep Security Notifier icon does not automatically show up in the Windows notification area. However, Deep Security Notifier will still work. Users need to re-launch Deep Security Notifier from the "Start" menu or restart the system. [17533] - The following system event log appears when you install Deep Security Agent on the Windows Server 2008 or Windows 7: "The Trend Micro Deep Security Agent service is marked as an interactive service. However, the system is configured not allow interactive services. This service may not function properly." This is a normal warning. On these platforms, Windows does not allow services to interact with the user's desktop, so the operating system displays the warning when Deep Security Agent tries to use interactive services. This desktop interaction feature is used by the Deep Security Agent to provide the restart notice on earlier versions of Windows. The warning message can be safely ignored. [Deep Security 8.0 Tier 2-00253] - You may sometimes encounter problems while upgrading the Deep Security Agent. The problem is related to the timing of the VC RTL assemblies being published to WinSxS, but it only seems to cause trouble if the version of the RTL is not changing. The root cause is some corrupted Windows components. To work around this, you can either run the Windows System File Checker (sfc.exe) to repair the operating system, or install the Microsoft Visual C++ Redistributable Package from the following URL before starting the upgrade procedure again. http://www.microsoft.com/download/en/details.aspx?id=26347 After installing the package from Microsoft, you should restart the computer or else the upgrade may still fail. To recover from this, you can install the package, re-run the installer and restart the computer. [Deep Security 8.0-01044] - Intrusion Prevention (DPI) is not supported over SSL connections when using IPv6. - When running an Anti-Malware Manual Scan with Smart Scan enabled, if the Deep Security Agent cannot contact the Smart Scan server, the resulting error event will indicate a "Real-Time" scan type instead of "Manual". [Deep Security 8.0 Tier 2-00024] - If network connectivity is lost for an extended period of time during a Deep Security Agent upgrade, you may need to restart the host machine. - It is possible that NDIS drivers will stop responding during Deep Security Agent installation or uninstallation if they do not properly free packets when requested to unbind. Deep Security Agent with NDIS 5.1 or NDIS 6.0 driver can free all packets correctly before upgrading or uninstalling. However, when installing or uninstalling NDIS drivers, Microsoft requires that all NDIS drivers be unbound and then rebound. This means that if other third-party NDIS drivers do not properly free packets, it is still possible for the Deep Security Agent install, upgrade, or uninstall process to stop responding. This is beyond Trend Micro's control and will only happen rarely. If this does occur then you can restart the computer and try to install, uninstall, or upgrade Deep Security Agent again. - Log Inspection Event logs are limited to 6000 characters. - When the network engine is working in TAP mode and the in-guest Agent is offline, the Deep Security Virtual Appliance status will display "Stand By". But, Deep Security Virtual Appliance is actually online and IP/FW events logs are still generated as rules are triggered. [10948] 8. Release History ======================================================================== See the following website for more information about updates to this product: http://www.trendmicro.com/download - Deep Security Agent 11.0, Build 11.0.0-211, 11.0.0-223, May 22, 2018 - Deep Security Agent 11.0, Build 11.0.0-326, August 2, 2018 - Deep Security Agent 11.0 Update 2, Build 11.0.0-390, September 18, 2018 7.1 Deep Security Agent 11.0.0-211, 11.0.0-223 ===================================================================== 7.1.1 Enhancements ===================================================================== This release includes the new features described in https://help.deepsecurity.trendmicro.com/11_0/on-premise/whats-new.html Additional enhancements since Deep Security 10.0: Enhancement 1: [DSSEG-1872] Microsoft requested that anti-virus vendors set a registry key that will allow a critical system patch for Microsoft Windows. Deep Security Agent sets the required registry key upon installation. For details, see https://success.trendmicro.com/solution/1119183 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enhancement 2: [DSSEG-934] This release enhances agent self-protection to prevent specific keys from being injected. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enhancement 3: [DSSEG-960] This release of Deep Security Agent adds support for Windows 10 RS2. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enhancement 4: [DSSEG-1264/511146/SEG-11066] Deep Security Agent 10.0 Update 4 or later no longer needs the Microsoft Visual C++ 2005 Redistributable Package. It will not be installed unless you are upgrading from a Deep Security 9.x Agent. If you are upgrading from an earlier Deep Security 10.x Agent, you may be required to reboot. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enhancement 5: [DSSEG-1404/TT 353335] A new policy setting (Computer/Policy editor > Settings > General > Suppress all pop-up notifications on host) enables you to hide all pop-up windows on hosts. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 7.1.2 Resolved Known Issues ===================================================================== This release resolves the following issues that were identified in previous versions of Deep Security: Issue 1: [DSSEG-1551] A change made on October 14 to version 2.7 of smBIOS for AWS EC2 instances introduced an incompatibility issue with Deep Security Agents on Linux and Windows. We have seen this issue affecting new instances created in the US-Virginia, Japan, and Singapore regions since October 14, but additional regions will be affected. This issue affects agent activation on any instance with the 2.7 bios and is likely to result in agents entering an unprotected state. Currently running activated agents are not affected. For details, please refer to: (EN) https://success.trendmicro.com/solution/1118601, (JP) http://esupport.trendmicro.com/solution/ja-JP/1118597.aspx Solution 1: The incompatibility is fixed with this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-943/SEG-4381] After the Deep Security Agent had been running on a web server for a long time, it would interrupt HTTPS traffic. Solution 2: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 3: [DSSEG-937/377091] When Firewall was enabled, the agent logged many 'invalid tcp timestamp' events in some circumstances. Solution 3: The default behavior has been changed to not log those events. It can be still enabled in the Anti- Evasion settings. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 4: [DSSEG-910/SEG-2762] The Deep Security Agent would crash when the integrity monitoring module scanned a file path containing a "%" character. Solution 4: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 5: [DSSEG-891] The Deep Security Agent created temporary files in the temp directory but these files were not removed after use, which resulted in inodes filling up. Solution 5: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 6: [DSSEG-855] A custom Log Inspection rule would not work and produced the error: "OSSEC id does not map to Deep Security Manager id". Solution 6: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 7: [DSSEG-844] Application Control failed to download a ruleset when the Deep Security Agent thread was stuck downloading a ruleset from an older configuration. Solution 7: With this release, Application Control will download the ruleset. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 8: [DSSEG-839] On a 'Large Send Offload' (LSO) network, a number of Firewall events with a reason of "Invalid IP Datagram Length" sometimes occurred. This happened because the Firewall driver incorrectly calculated the IP datagram length in an LSO environment. Solution 8: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 9: [DSSEG-1138/SEG-5409/00388364] Due to a race condition, a kernel panic would occur when Deep Security Agent_filter was handling duplicate UDP packets. Solution 9: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 10: [DSSEG-1109] Deep Security file reputation querying to Smart Protection Server was not counted correctly in the Summary of Smart Protection Server. For example, the "Active Users for File Reputation" widget displayed an incorrect number of users. Solution 10: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 11: [DSSEG-1090] In some circumstances, the kernel module for a Linux version of the Deep Security Agent could be replaced by an earlier version of the kernel support package. Solution 11: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 12: [DSSEG-1081] When connections were reset, they were not removed in the kernel module until the connection timed out. This resulted in the maximum number of TCP connections being reached. Solution 12: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 13: [DSSEG-1041/SEG-370] The Deep Security Firewall/Intrusion Prevention driver sometimes did not bind to a specific Network Interface Controller (NIC). When the Deep Security Agent took it as StandbyAdapter, it would cause a Deep Security Agent exception during initialization and fail to generate the Firewall/intrusion prevention driver configuration file. Solution 13: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 14: [DSSEG-1040/SBM 352560] When the Intrusion Prevention rule "1000128 - HTTP Protocol Decoding" is enabled and "Specify raw characters that are not allowed in the URI:" is used, when the Deep Security Agent detects an illegal character, the Deep Security Manager will show the illegal character in an Intrusion Prevention event. However, the Deep Security Agent sometimes did not report the correct location of the illegal character, so it was not displayed correctly in the Deep Security Manager. Solution 14: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 15: [DSSEG-1012] If the Deep Security Agent failed to download the Kernel Support Package, the agent would not retry the download. Solution 15: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 16: [DSSEG-975] The Threat Tracing pattern number in Deep Security Agent on Windows was incorrectly set to a large number and could not be updated because the latest ActiveUpdate pattern number was smaller. Solution 16: This release resets the pattern number to 0 during Agent upgrade. The pattern number will then be set to the latest number when the next security update is performed (either manually or using a scheduled task). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 17: [DSSEG-947] When the Anti-Malware engine encountered a problem during update, it displayed an error code in the endpoint event. Solution 17: An error message is now displayed instead of a code. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 18: [DSSEG-1089/SEG-875] In some environments, the Anti-Malware Solution Platform (Anti-MalwareSP) could cause high disk input/output when the common scan cache was on. Solution 18: By default, the Anti-MalwareSP common scan cache is on. To disable it, open a Windows command prompt on the Deep Security Manager computer, go to the Deep Security Manager root folder, and run this command: Deep Security Manager_c -action changesetting -name settings.configuration.disableAmspCommonScanCache -value true ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 19: [DSSEG-1279/00474128/SEG-9606] A heap corruption in li.dll caused Deep Security Agent to crash. Solution 19: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 20: [DSSEG-1242/internal case] A race condition caused an error displayed on a blue screen when the Intrusion Prevention module handled duplicate UDP packets. Solution 20: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 21: [DSSEG-1198/351879] The Deep Security Agent did not securely generate the SSL Master Secret when the "Client key exchange" and "Certificate verify" handshake records were both in one packet. Solution 21: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 22: [DSSEG-1367/SF00472245/SEG-10539] When log inspection was enabled, the Deep Security Agent sometimes used more than 50% (and up to 98%) of the CPU for long periods of time. Solution 22: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 23: [DSSEG-1364/493112] In previous releases, the "Smart Protection Server Disconnected for Web Reputation" alert could only be cleared manually by a user. Solution 23: In this release, Deep Security Manager will clear the alert automatically when it receives a "Smart Protection Server Connected for Web Reputation" event. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 24: [DSSEG-1361/SEG-12002] A copy or rename operation to a large file (over 3MB) from client computer was sometimes delayed if the file was put on a shared folder on a remote server and SMB v3.0 was used. This issue occurred when the Deep Security Agent was installed on the remote file server and Anti-Malware real-time scanning was enabled. Solution 24: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 25: [DSSEG-1239] Deep Security Notifier did not display any information because the ds_agent service's relevant thread exited abnormally. Solution 25: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 26: [DSSEG-1203/SEG-8048/SF00453864] Smart scan pattern updates sometimes failed. Solution 26: This issue is fixed in this release. The iAU module has been upgraded to 1062. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 27: [DSSEG-1497] A brief network disconnection occurred during the installation of the Trend Micro Lightweight Filter Driver. This network disconnection would result in the following issues: 1) DNS record disappears in the dual-AD server environment 2) Windows Fail-Over Cluster out-of-sync 3) Windows Network Load Balancing servers out-of-sync. Solution 27: On Windows 2012 R2 or later, network will remain connected even when doing a filter hook/unhook and during installation. During upgrade, a reboot is needed for the Filter Driver's FilterRunType transition. For Windows Network Load Balancing, a few Firewall rules are needed in addition to this fix. For details, please see: [https://success.trendmicro.com/solution/1118512] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 28: [DSSEG-1370] The Deep Security Agent sometimes failed to complete an SSL handshake when the agent was using a proxy to connect to Deep Security Manager. Solution 28: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 29: [DSSEG-1271/SEG-10957] A stop error was reported on Windows Servers in an IPv6 environment with vLAN tagging. Solution 29: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 30: [DSSEG-1247] A race condition when the ds_agent kernel module was handling TCP connections caused an error displayed on a blue screen. Solution 30: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 31: [DSSEG-1508/SEG-8557/464768] A driver used by Anti-MalwareSP caused increased kernel memory usage due to a token leak. Solution 31: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 32: [DS-14009] When Application Control was enabled, customers sometimes saw software changes when executable files were changed or added by Microsoft. Solution 32: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 33: [DS-14221] If you enabled Anti-Malware and Application Control in a policy and applied it to a pre-10.1 Deep Security Agent on Windows, then upgraded the agent to 10.1, it sometimes displayed the status “Software Update: Anti-Malware Windows Platform Update Failed”. This error was due to a timing issue and could be ignored because the Anti-Malware component upgrade was successful. Solution 33: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 34: [DS-15543] Deep Security Manager sometimes raised an event with an incorrect description, which indicated the settings had been reset back to "inherited" when the value of the setting was changed to an empty string (""). Solution 34: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 35: [DS-16913] When the Deep Security Agent lightweight filter driver (tbimdsa.sys) was installed in a Windows environment where NIC teaming was configured as LACP mode, the "Microsoft Network Adapter Multiplexor Driver" device could enter a "Network cable unplugged" state. Solution 35: The issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 36: [DSSEG-1148/SEG-1206, DS-18289] The default ICRC log level for a Deep Security Agent on Linux is "debug", which causes the ds_am-icrc.log file to grow quickly. Solution 36: Change the default ICRC log level to "warn". For a fresh agent installation, the default ICRC log level will be set to "warn" by default. To update an existing agent on Linux: 1. Upgrade the Deep Security Manager to the build that contains the fix. 2. On the Deep Security Manager computer, open a windows command prompt, go to the Deep Security Manager root folder, and run this command: Deep Security Manager_c -action changesetting -name settings.configuration.resetICRCLogConfig -value true 3. Upgrade the Deep Security Agent to the build that contains the fix. 4. After the agents are upgraded and the default ICRC log level has been corrected, we recommend that you turn off the key. To do this, go to the Deep Security Manager computer, open a windows command prompt, go to the Deep Security Manager root folder and run this command: Deep Security Manager_c -action changesetting -name settings.configuration.resetICRCLogConfig -value false ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 37: [DSSEG-1744, DS-16246] Sometimes, after a Deep Security Agent upgrade, anti- malware protection would be absent or out of date. Solution 37: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 38: [DSSEG-1714, DS-18289] An EICAR sample was not detected and blocked in a NIC teaming environment. Solution 38: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 39: [DSSEG-1692, DS-17349] When event logs were aggregated, the Mac address for an aggregated Firewall or Intrusion Prevention event could be incorrect. Solution 39: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 40: [DSSEG-1493] When the Deep Security Agent lightweight filter driver (tbimdsa.sys) was installed in a Windows environment where NIC teaming was configured as LACP mode, the "Microsoft Network Adapter Multiplexor Driver" device would enter a "Network cable unplugged" state. Solution 40: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 41: [DS-18215] When a Deep Security Agent had the relay feature enabled and then the agent was demoted to remove the relay while packages were being downloaded to the relay, those packages sometimes were not removed from the agent. Solution 41: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 42: [DS-17807] Advanced threat detection (machine learning) did not work when a Deep Security Agent was using a proxy with IPv6 IP format. Solution 42: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 43: [DS-13419] When using Application Control for Windows computers, if you selected "Block unrecognized software until it is explicitly allowed", you needed to enable maintenance mode before updating the computer's operating system. This included when performing an "update and restart" action on a computer running Windows. Failure to do this could break the computer because Application Control would block execution of updated files in the OS until you created the allow rules. Depending on which OS file was updated, you could need to use an OS recovery mode or external tool to recover from this misconfiguration. Solution 43: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 44: [DSSEG-1885/SEG-11876 When SSL inspection was enabled on an SSL server, clients sometimes failed to establish an SSL session and a "Record Layer Message (not ready)" intrusion prevention event would occur. Solution 44: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 45: [DSSEG-2076/SEG-23938/SEG-23938 SSL/TLS compression was not disabled while initiating SSL context for DSA listening port (4118). Solution 45: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 7.2 Deep Security Agent 11.0.0-326 ======================================================================== 7.2.1 Enhancements ===================================================================== There are no enhancements in this release. 7.2.2 Resolved Known Issues ===================================================================== This release resolves the following issue(s): Issue 1: [DSSEG-2511] When a Deep Security Relay had Anti-Malware and agent self-protection enabled, the agent self-protection would prevent the relay-enabled agent from restarting when needed. This prevented the TLS 1.2 command from taking effect. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-2513] When the anti-malware or firewall features were enabled, Deep Security Agent was not registered to the Windows Security Center on Windows 10 version 1803 (April 2018 Update). This caused the status of anti-malware and firewall to be incorrect in the Windows Security Center and Windows Defender Security Center. Solution 2: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 3: [DSSEG-2456] During a component update, the Anti-malware service sometimes got stuck while purging the cache, so the Deep Security Agent status shown in Deep Security Manager would remain as "Security Update in Progress" for a long time. Solution 3: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 8. Files Included in This Release ======================================================================== This release is a complete installation. Use one of the following files: Agent-Windows-11.0.0-390.x86_64.zip (64-bit) Agent-Windows-11.0.0-390.i386.zip (32-bit) Notifier-Windows-11.0.0-390.i386.msi (32-bit - can be installed on 64-bit) 9. Contact Information ======================================================================== A license to the Trend Micro software usually includes the right to product updates, pattern file updates, and basic technical support for one (1) year from the date of purchase only. After the first year, Maintenance must be renewed on an annual basis at Trend Micro's then-current Maintenance fees. Contact Trend Micro via phone or email, or visit our website to download evaluation copies of Trend Micro products. https://www.trendmicro.com/en_us/contact.html NOTE: This information is subject to change without notice. 10. About Trend Micro ======================================================================== Smart, simple, security that fits As a global leader in IT security, Trend Micro develops innovative security solutions that make the world safe for businesses and consumers to exchange digital information. Trend Micro, Deep Security, "deep security solutions", and the t-ball logo are trademarks of Trend Micro Incorporated and are registered in some jurisdictions. All other marks are the trademarks or registered trademarks of their respective companies. 11. License Agreement ======================================================================== View information about your license agreement with Trend Micro at: https://www.trendmicro.com/en_us/about/legal.html 12. Third Party Software ======================================================================== Deep Security employs the use of 3rd party binary distributions. The binary distributions are subject to the licenses available in the following directory: [Install Directory]\licenses Where 3rd party licenses require open access to their source code, Trend Micro will provide the necessary materials upon written request. ======================================================================== (C) 2018 Trend Micro Inc. All rights reserved. Published in Canada.