~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Readme for Trend Micro (TM) Deep Security Manager 9.5 Service Pack 1 Platforms: Windows Server 2012 (64-bit), Windows Server 2012 R2 (64-bit), Windows Server 2008 (64-bit), Windows Server 2008 R2 (64-bit), Windows Server 2003 SP2(64-bit), Windows Server 2003 R2 (64-bit), Redhat Enterprise Linux 5 (64-bit) Redhat Enterprise Linux 6 (64-bit) Not Supported: Red Hat Enterprise Linux (RHEL) Xen Hypervisor Windows Server 2012 Core Windows Server 2008 Core As of Deep Security 9.0, Deep Security Manager is no longer supported on 32-bit versions of the Windows platform. Date: Jan. 30, 2015 Release: 9.5 SP1 Build Version: 9.5.5600 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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: http://us.trendmicro.com/us/solutions/enterprise/security-solutions/ virtualization/deep-security/ Download the latest version of this readme from the "Software" page at the Trend Micro Download Center website: http://downloadcenter.trendmicro.com/ 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 9.5 Service Pack 1 1.1 Overview of This Release 1.2 Who Should Install This Release 1.3 Upgrade Notice 2. What's New 2.1 New in Deep Security 9.5 Service Pack 1 2.2 Resolved Known Issues 3. Documentation Set 4. System Requirements 5. Known Incompatibilities 6. Known Issues in Deep Security Manager 9.5 SP1 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 9.5 Service Pack 1 ======================================================================== 1.1 Overview of This Release ===================================================================== Deep Security 9.5 SP1 contains a number of bug fixes as well as new feature enhancements. For a complete list of the major changes in Deep Security 9.5 SP1 from previously released versions of Deep Security, please see the "What's New in Deep Security 9.5 SP1" section of the online help or the Administrator's Guide, 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 8.0, 9.0 or 9.5. All new Deep Security users should install Deep Security 9.5 SP1. 1.3 Upgrade Notice ===================================================================== To upgrade to Deep Security Manager 9.5 SP1, you must be running the latest patch or service pack versions of Deep Security Manager 8.0, 9.0 or 9.5. If you choose to upgrade your Deep Security Manager to version 9.5 SP1 while running older versions of Deep Security Agents under protection, you will be warned during the upgrade installation that this version will no longer be able to communicate with those Agents. Deep Security Manager 9.5 SP1 ONLY supports the latest versions of 8.0 and 9.x of Deep Security Agent, and Deep Security Virtual Appliance. Please refer to the "Known Incompatibilities" section of this readme file for details. Deep Security 9.5 SP1 does not support ESXi version 4.1. To deploy Deep Security 9.5 SP1, your VMware infrastructure (vCenter, vShield Manager, vShield Endpoint, and vShield Endpoint drivers) must be upgraded to version 5.x. Also be sure to read the VMware documentation for upgrading your VMware environment including the KB article on VMware's web site: http://kb.vmware.com/kb/2032756 http://kb.vmware.com/kb/2052329 Upgrade the Deep Security Filter Driver to SP1 version build 9.5.3-2750 prior to upgrading the Deep Security Virtual Appliance to 9.5 SP1 on non-NSX environment. Engine offline errors will occur after upgrading Deep Security Virtual Appliance without upgrading the Filter Driver. 2. What's New ======================================================================== 2.1 New in Deep Security 9.5 Service Pack 1 ===================================================================== Extended support for Microsoft Azure - Deep Security can now connect to Microsoft Azure accounts using shared certificates. For more information, see the Deep Security 9.5 SP1 Installation Guide (Cloud). Extended support for VMware NSX Security Policies - Event-Based Tasks are now available which allow users to monitor the VMware NSX Security Policy assigned to a VM and perform Deep Security Tasks (such as the activation or deactivation of Deep Security protection) based on changes to the NSX Security Policy. For more information, see "Deploying Agentless Protection in an NSX Environment" in the Deep Security 9.5 SP1 Installation Guide (NSX). Extended support for NSX tagging - Deep Security can now apply NSX tags based on Intrusion Prevention Events (as well as Anti-Malware Events). For more information, see "Deploying Agentless Protection in an NSX Environment" in the Deep Security 9.5 SP1 Installation Guide (NSX). Extended Proxy Support for Relays - Relay Groups can now be configured to use unique proxy servers to retrieve Security Updates from Trend Micro. The option is available in the Relay Group's properties window. Support for log only HTTP Protocol Decoder errors - Certain errors determined by the HTTP Protocol decoder can now be manually set to be log only. The errors are: Double Decoding Exploit Illegal Character in URI Invalid Hex Encoding Invalid Use of Character Invalid UTF8 Encoding IPS Events are now viewable in Trend Micro Control Manager - Deep Security Intrusion Prevention Events can now be monitored in Trend Micro Control Manager. Proxy settings for communication with Cloud Instances - Deep Security Manager can now be configured to use a separate proxy server to communicate with protected Cloud Account instances. The proxy settings are available in the Deep Security Manager on the Administration > System Settings > Proxies tab. Recommendation Scan Performance Improvements - Improvements to the recommendation scan analysis algorithms have resulted in a fivefold improvement in the average amount of time required to carry out a Recommendation Scan on a computer. Display X-Forwarded-For header in Intrusion Prevention Events - Deep Security can now display X-Forwarded-For headers in Intrusion Prevention events when available in the packet data. This information can be useful when the Deep Security Agent is behind a load balancer or proxy. When X-Forwarded-For header data is available, it is displayed in the Event's Properties window. 2.2 Resolved Known Issues ===================================================================== This release resolves the following issues: Issue 1: [25132/25109/TT308912] Recommendation Scan with either Agent-initiated mode or Manager-initiated mode on Windows Azure endpoint fails, since Windows Azure disconnects connection between DSM and DSA when the connection is in idle over 4 minutes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: Enable Keep-Alive socket option to prevent being disconnected by Windows Azure when connection is in idle. With this fix, the connection between DSM and DSA is able to get TCP/IP Keep-Alive packet by Windows with the following settings: Key: HKLM\SYSTEM\CurrentControlSet\Services\Tcp \Parameters Name: KeepAliveTime Type: REG_DWORD Default Value: 0x6DDD00 (7,200,000 milliseconds = 2 hours) Key: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip \Parameters Name: KeepAliveInterval Type: REG_DWORD Default Value: 0x3E8 (1,000 milliseconds = 1 second) Issue 2: [25167/24845/TT307842] An issue with the SSLv3 protocol triggers a certain vulnerability in Deep Security Manager 9.0 Service Pack 1. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 2: This critical patch enables Deep Security Manager 9.5 web servers to accept only TLSv1.0 connections and prevents these from accepting SSLv3 connections to prevent the vulnerability. Issue 3: [25168/25110/TT307416] Some Log Inspection events have mistranslation in Japanese version. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 3: fix the translation. Issue 4: [25340/25333/TT309982] DSM fails to prepare ESXi 5.0/5.1 because of SSLv2 Hello protocol attribute. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 4: This hot fix resolves above issue. Filter Driver now can be deployed successfully on ESXi 5.0/5.1. Issue 5: [25341/24139/TT302914] For an valid URL request to Deep Security Manager, the response includes DSM web server type and version information. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 5: Changing the server.xml parameter to remove server type and version information. Issue 6: [20448/19960/TT279384] Some widgets on Dashboard always show items in English even if user's display language is Japanese. Due to this behavior, the user can't see any events in "Events & Reports" by clicking the items on the widgets. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 6: Widgets and Reports show items based on user's language setting. Issue 7: [22745/21578/TT290832/TT247366] When DSM is installed on RHEL 5 and RHEL 6 with a JP locale, the diagnostic package collected may not be able to show Japanese characters in the pdf file. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 7: This release fixes bug in diagnostic package pdf file. Issue 8: [25062/25807/TT307226] When you add more than one NIC to an existing guest virtual machine (VM), vCenter will update the IP address list in a last-in first-out (LIFO) pattern. When Deep Security Manager queries vCenter, vCenter will provide the most recently-added IP address for each guest VM. If the IP address and the corresponding NIC card is not accessible from Deep Security Manager or vCenter at that time, the corresponding guest VM status will be "offline". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 8: This release allows users to specify a preferred IP address for each guest VM through the "settings.configuration.preferredGuestVMIpAddress" parameter. Deep Security Manager will always use this preferred IP address to connect to a guest VM with multiple IP addresses and NICs. This helps ensure that Deep Security Manager can always connect to Deep Security Agent even when the NIC changes as long as the specified IP address is correct. 3. Documentation Set ======================================================================== In addition to this readme.txt, the documentation set for this product includes the following: o Deep Security 9.5 SP1 Installation Guides (IG) -- Provides product overview, deployment plan, installation steps and basic information intended to help you smoothly deploy Deep Security. The following Installation Guides are available in Trend Micro Download Center: Deep_Security_95_SP1_Install_Guide_basic_EN.pdf Deep_Security_95_SP1_Install_Guide_cloud_EN.pdf Deep_Security_95_SP1_Install_Guide_nsx_EN.pdf Deep_Security_95_SP1_Install_Guide_vmsafe_EN.pdf o Deep Security 9.5 SP1 Administrator's Guide (AG) -- Provides 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. (All the content of the Administrator's Guide can be found in the Deep Security Manager's online help.) o Readme.txt files -- version enhancements, known issues, and release history. There is one readme for each installable Deep Security component: Manager, Agent, Virtual Appliance, and ESX Filter Driver. Electronic versions of the manuals are available from the Trend Micro Download Center at: http://downloadcenter.trendmicro.com/ o Online help -- Context-sensitive help screens that provide guidance for performing a task. (The online contains all the information contained in the Administrator's Guide.) o TrendEdge is a program for Trend Micro employees, partners, and other interested parties that provides information on unsupported, innovative techniques, tools, and best practices for Trend Micro products. The TrendEdge database contains numerous documents covering a wide range of topics. http://trendedge.trendmicro.com o Knowledge Base -- a searchable database of known issues, including specific problem-solving and troubleshooting topics. http://esupport.trendmicro.com 4. System Requirements ======================================================================== For a complete list of the System requirements, please refer to the Deep Security 9.5 SP1 Installation Guide. 5. Known Incompatibilities ======================================================================== - Deep Security Manager 9.5 SP1 does not support version 7.5 and earlier versions of Deep Security Virtual Appliance and Deep Security Agent. 6. Known Issues in Deep Security Manager 9.5 SP1 ======================================================================== - The CPU Usage (Agent only) setting under Manual and Scheduled Scan Configuration in the Deep Security Manager console is not working on SUSE 10 SP3 and SP4. [20717] - Coordinated approach in NSX is not supported in this build. Appliance (agentless) protection appears active and online even when Deep Security Agent is installed and online. [22136] - Agentless protection is not supported in ESX 5.1 with NSX. ESX 5.5, VCenter 5.5 and NSX Manager 6.0.5 are the minimum requirements for agentless protection. [22062] - Excluding a folder in Anti-Malware agentless protection would also exclude folders that starts with the same folder name. For example, excluding c:\temp also excludes c:\temp1 and c:\temp2 from Anti-Malware scanning. [22037] - Anti-Malware, Web Reputation, Integrity Monitoring, and Log Inspection should not be enabled on the policy that is assigned to the Deep Securit Virtual Appliance itself. These features are not supported when applied to the Deep Security Virtual Appliance and may produce error events. [21250] - It can take up to 30 minutes before the appliance is ready for deployment through NSX Manager after importing the Deep Security Virtual Appliance package to the DSM. Deploying the appliance before the package is in place at \temp would result in failure. [23150] - When preparing ESXi 5.5 for Deep Security Virtual Appliance (DSVA) 9.5 deployment, you get the following error during Filter Driver installation: "The installation transaction failed". Refer to http://esupport.trendmicro.com/solution/en-US/1102068.aspx for complete details on the recommended action. [22285] - The Deep Security Manager will display the platform of CentOS machines as RedHat. This is because the agent package used in CentOS and RedHat are the same and labeled as RedHat agent package.] [21674/25156] - Location awareness will not work on pure IPv6 environment. [12776] - Infected file will still appear in Quarantined Files list even if the Anti-Malware Event says Quarantine Failed. [21620] - In the computer updates page, DSM will show Smart Scan Agent Pattern, Spyware Active Monitoring Pattern and Virus pattern in Deep Security Agent for Linux regardless of the scan mode. [21829] - Software update using IPv6 is currently not supported by Trend Micro download center. [25937] - Deep Security Agent running on SUSE on Azure cloud will not be managed under Azure cloud account in the Deep Security Manager. The agent will appear under normal computers list. [26499] - When real-time Integrity Monitoring feature of Deep Security Agent is being used on Windows, the event "Get Events Failed" and "Agent/Appliance Error" may appear with the following description: "SQLITE_BUSY[5]: database is locked." When this event occurs, restart the Deep Security Agent service. [26615] - 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] - The Out of Sync relays hyperlink displays the correct count but clicking the link will display both out of date computers and relays. [23418/21042] - In NSX 6.1.2 and earlier, if more than one NSX Security Groups are defined and applied to the NSX Security Policy that contains Deep Security Services, any un-applying of the policy will not be reflected in Deep Security Manager with respect to NSX Security Group membership. [25304] - In NSX 6.1.1 and earlier, if your remove the Deep Security Services from an NSX Security Policy, it will not be reflected in Deep Security Manager with respect to NSX Security Group membership. [25303] - Deep Security Manager does not support installation paths that contain special characters (non-alphabet and non-numeric characters). The same restriction also applies to the database name and/or database account used by Deep Security Manager. [16708] - When a user runs Agent-initiated recommendation scan using the "dsa_control -m RecommendationScan:true" command, no system event related to recommendation scan is recorded. - In rare situations, Deep Security Manager may not correctly identify the status of the EPsec Driver installed on an ESXi. When you activate an Appliance, if Deep Security Manager does not identify the correct status of vShield Endpoint, it will not register with the vShield Manager. If Deep Security Manager gives you this warning, perform a full "Synchronize" with your vCenter and it will update the current installation status of all drivers on all ESXi(s) in the environment. [17636] - In Multi-Tenant installations, the Primary tenant Deep Security Manager may cause "Reconnaissance Detected: Network or Port Scan" alerts on Tenants' Deep Security Managers. To avoid these alerts, Tenants can manually add the Primary Tenant's Deep Security Manager IP address to the "Ignore Reconnaissance" IP list. (Policies > Common Objects > Lists > IP Lists). [17175] - In rare cases, adding a vCloud or AWS Cloud Account in Deep Security Manager can result in the creation of two identical Cloud Accounts. If this occurs, either one of the two accounts can be safely removed. [17280/17051] - 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] - If the Manager node(s) and the Database are installed on machines with synchronized clocks but configured for different time-zones, an error indicating that the clocks are not synchronized will be triggered incorrectly. [17100] - On Windows 2008 and Server 2012 systems, after installing the Deep Security Manager with a co-located Relay, the Deep Security Notifier icon does not automatically appear in the Windows notification area. However, the Deep Security Notifier will still function. Users need to re-launch the Deep Security Notifier from the "Start" menu or restart the system. [17533] - When using Deep Security in iCRC mode, a DNS server must be available. If a DNS server is unavailable the Anti-malware feature of the Deep Security Virtual Appliance may not function correctly. [Deep Security 8.0-01169] - Deep Security Manager does not support License updates or connecting to the Trend Micro Certified Safe Software Service using a SOCKS5 proxy. To use these two features, use an HTTP proxy. [Deep Security 8.0-1024] - In certain cases, when attempting to use the dsm_s stop command on Linux to stop the Deep Security Manager service, you may get the following message: "Timeout. Daemon did not shutdown yet." Dsm_s is based on install4j whose timeout value is 15 seconds, which cannot be changed. The Deep Security Manager may require longer than this to shut down. To ensure the service has been shut down run the "ps -ef | grep DSMService" command before using the dsm_s stop command. [Deep Security 8.0-00095] - Air-gapped Relays will still try to contact an Update Server to check for Updates. To avoid update failure alerts, set the Relay to use itself as an update source: 1. In the Relay's "Details" window, go to "System > System Settings > Updates". 2. In the "Relays" area, select "Other Update Source:" and add "https://localhost:4122". 3. Click "Save". [Deep Security 8.0-01124] - If an ESXi with an installed vShield Endpoint driver is removed from its vCenter, Deep Security Manager cannot detect the installed driver if the ESXi is later re-added to the vCenter. This will cause any newly Deep Security Virtual Appliance- protected virtual machines to not have antimalware enabled. The workaround is to uninstall and reinstall the driver through the VSM. [Deep Security 8.0-01036] - The default value for whois in Deep Security does not resolve properly. To use the whois feature, you must modify the WHOIS URL to use a different server. [Deep Security 8.0-01248] - Intrusion Prevention is not supported over SSL connections when using IPv6. - The Anti-malware scan inclusion/exclusion directory settings are sensitive to forward slash "/" and backslash "\". For use with Windows operating systems the inclusion/exclusion paths must use the backslash "\". [7.5 SP1-00231] - When creating custom Integrity Monitoring Rules using the "RegistryKeySet" tag, the attribute values must be in uppercase letters. For example, . Using lowercase may result in an "Integrity Monitoring Rule Compile Issue" error. [7.5 SP1-00171] - Malware scans of network shared folders are only supported using real-time scan. Manual scans or scheduled scans will not work. [7.5-00012] - If a CD or a mounted ISO file contains malware and the anti-malware configuration is set to "Delete" upon detection, Deep Security Manager will still report that the malware was "deleted" even if it was unable to do so. [7.5-00010] - Deep Security Manager cannot display an incorrect filename event in the Anti-Malware Event if the malware was found in the "Recycle Bin". [7.5-00023] - During an upgrade, the Deep Security Manager service may not be able to install properly on some platforms if the "Services" screen is open. To work around this, make sure the "Services" screen is closed prior to installation or upgrade of Deep Security Manager. - If you receive a "java.lang.OutOfMemoryError" error during the installation of Deep Security Manager, please refer to the "Installation Guide" for instructions on how to configure the maximum memory usage for the installer. - During an upgrade, if you receive a message stating that the Deep Security Manager cannot start the service, restarting Deep Security Manager usually fixes the problem. In rare cases, you may have to run the installer again in Upgrade/Repair mode after restarting. - If Windows Firewall is enabled on Deep Security Manager, it may interfere with port scans causing false port scan results. Windows Firewall may proxy ports 21, 389, 1002, and 1720 resulting in these ports always appearing open regardless of any filter placed on the computer. - By default Exchange 2000 and later servers will dynamically assign a non-privileged port (1024-65535) for communications between the client and the server for the System Attendant, Information Store, and Name Service Provider Interface (NSPI) services. If you will be using the Microsoft Exchange Server profile with an Exchange 2000 or later server then you should configure these services to use static ports as described in the article "Exchange 2000 and Exchange 2003 static port mappings" (http://support.microsoft.com/?kbid=270836). Once static ports have been configured you should extend the appropriate Exchange Server port list to include the ports that have been assigned to these services. You may also want to set the "No RFR Service" registry setting to "1" to prevent the Exchange server from referring clients to the domain controller for address book information. See the article "How Outlook 2000 Accesses Active Directory" (http://support.microsoft.com/?kbid=302914) for more information. Alternatively, it is possible to configure Exchange RPC to run over HTTPS if you are using Outlook 2003 on Windows XP Service Pack 1 or later with Exchange Server 2003. In this case only port 443 needs to be added to the Exchange port list. - The "Recommendation" Alert may remain raised on some computers even after all recommended Intrusion Prevention, Integrity and Log Inspection Rules appear to have been applied. This can occur because even though an "Application Type" may be recommended for a computer, the "Application Type" will not be displayed in the "Show Recommended" view if no Intrusion Prevention Rules associated with Application Type are currently recommended. To resolve the situation, use the "Show All" view of the Intrusion Prevention Rules screen and assign all recommended "Application Types" (even if no associated Rules are currently recommended). Alternatively, you can just dismiss the alert after verifying that you have assigned all recommended rules to the computer. [8345] - When an Appliance-protected VM is migrated from one Appliance-protected ESXi to another, and if that virtual machine currently has warnings or errors associated with it (for example "Reconnaissance Detected"), those errors may incorrectly get cleared during the migration. [10602] - Log Inspection Events have a size limitation of 6000 characters. 7. Release History ======================================================================== 9.5.5600 Jan. 30, 2015 8. Files Included in This Release ======================================================================== This release is a complete installation. Use one of the following files: Manager-Windows-9.5.5600.x64.exe (64-bit) Manager-Linux-9.5.5600.x64.sh (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. You can contact Trend Micro via fax, phone, and email, or visit us at: http://www.trendmicro.com Evaluation copies of Trend Micro products can be downloaded from our Web site. Global Mailing Address/Telephone Numbers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For global contact information in the Asia/Pacific region, Australia and New Zealand, Europe, Latin America, and Canada, refer to: http://www.trendmicro.com/us/about-us/index.html The Trend Micro "About Trend Micro" screen displays. Click the appropriate link in the "Contact Us" section of the screen. Note: This information is subject to change without notice. 10. About Trend Micro ======================================================================== Trend Micro, Inc. provides virus protection, anti-spam, and content-filtering security products and services. Copyright 2015, Trend Micro Incorporated. All rights reserved. Trend Micro, the t-ball logo, Deep Security and "deep security solutions" 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 ======================================================================== Information about your license agreement with Trend Micro can be viewed at: http://us.trendmicro.com/us/about/company/user_license_agreements/ 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) 2015 Trend Micro Inc. All rights reserved. Published in Canada.