Trend Micro Incorporated October 10, 2018
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Readme for Trend Micro (TM) Deep Security Manager 11.2 Feature Release
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IMPORTANT: Deep Security 11.2 is a feature release. Feature releases
are interim releases that provide early access to new
features before the next major release becomes available. The
lifecycle and support for feature releases are different from
long-term support releases like 11.0. For details, see:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/feature-releases.html
NOTICE: This readme file was current as of the date above. However,
all customers are advised to check the Trend Micro website for
documentation updates.
GM release documentation:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/Welcome.html
Patch/SP release documentation:
https://help.deepsecurity.trendmicro.com/software.html
TIP: Register online with Trend Micro within 30 days of
installation to continue downloading new pattern files and
product updates from the Trend Micro website. Register
during installation or online at:
https://clp.trendmicro.com/FullRegistration?T=TM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deep Security Manager Platforms:
- Red Hat Enterprise Linux 7 (64-bit)
- Red Hat Enterprise Linux 6 (64-bit)
- Windows Server 2012 and 2012 R2 (64-bit)
- Windows Server 2008 and 2008 R2 (64-bit)
- Windows Server 2016 (64-bit)
Not Supported:
- Red Hat Enterprise Linux (RHEL) Xen Hypervisor
- Windows Server 2012 Core
- Windows Server 2008 Core
- Windows Server 2016 Core
- Deep Security Manager is not supported on 32-bit
versions of the Windows platform.
Date: October 10, 2018
Release: 11.2
Build Version: 11.2.225
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
Software page:
https://help.deepsecurity.trendmicro.com/software.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.2
1.1 Overview of This Release
1.2 Who Should Install This Release
1.3 Upgrade Notice
2. What's New
2.1 Enhancements
2.2 Resolved Known Issues
3. Documentation Set
4. System Requirements
5. Installation
6. Known Incompatibilities
7. Known Issues in Deep Security Manager 11.2
8. Release History
9. Files Included in This Release
10. Contact Information
11. About Trend Micro
12. License Agreement
13. Third-Party Software
===================================================================
1. About Deep Security 11.2
========================================================================
1.1 Overview of This Release
=====================================================================
Deep Security 11.2 contains feature enhancements and bug fixes.
For a complete list of the major changes in Deep Security 11.2, see
the "What's New?" page on the Deep Security Help Center:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/whats-new.html
1.2 Who Should Install This Release
=====================================================================
Deep Security 11.2 is a feature release. Feature releases are
interim releases that provide early access to new features before the
next major release becomes available. The lifecycle and support for
feature releases are different from long-term support releases
like 11.0. For details, see:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/feature-releases.html
1.3 Upgrade Notice
=====================================================================
- 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)
- The Simplified Chinese locale is no longer available in Deep
Security. Existing tenants and administrators who are using the
Simplified Chinese locale will be automatically transitioned to
English.
- If you are using PostgreSQL as your Deep Security database, prior
to upgrading to Deep Security Manager 11.2, check if the
communication between the Deep Security Manager and PostgreSQL
database is encrypted. Note that this is disabled by default and
would have been manually configured.
To check, verify whether the
Deep Security Manager\webclient\webapps\ROOT\WEB-INF\dsm.properties
file contains the line:
database.PostgreSQL.connectionParameters=ssl\=true
If it exists, disable the encryption by deleting the line and
restarting the Deep Security Manager service before upgrading. Add
the line back after the upgrade. Failure to disable the encryption
will cause the upgrade to fail.
For more information on how to set up the encryption on a
PostgreSQL database, see:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/Manage-Components/dsm-db-encrypt.html
- If application control is turned on prior to upgrading the agents,
maintenance mode must be enabled to prevent application control
from blocking the upgrade of Deep Security components or reporting
software changes depending on the configuration.
- If you are using Microsoft SQL Server 2008 SP3 (or earlier) or
Microsoft SQL Server 2008 R2 SP1 (or earlier) as your Deep Security
database, check if the communication between the Deep Security
Manager and the database is encrypted prior to upgrading the Deep
Security Manager to 11.2.
Note that this is disabled by default and would have been manually
configured. To check, verify whether the
Deep Security Manager\webclient\webapps\ROOT\WEB-INF\dsm.properties
file contains the line:
database.SqlServer.ssl=require
If it exists, disable the encryption before upgrading and then
re-enable it when the upgrade is complete. For instructions, see:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/Manage-Components/dsm-db-encrypt.html
Failure to disable the encryption will cause the upgrade to fail.
- Deep Security 11.2 includes significant improvements to the
upgrade process which contains functionality that checks your
currently installed Deep Security components and makes
personalized recommendations for your upgrade path. The upgrade
process also upgrades the database schema without requiring
manual steps.
- As usual, backup your database before upgrading and consider
performing the upgrade during off-hours. For more information see:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/Manage-Components/update-database.html
- Deep Security Manager 10.1 and later no longer supports TLS 1.0/1.1
on port 4119. Older deployed relays (any version before 9.6 SP1
Patch1, 9.6.2-6400) will fail to get software packages from the
manager for distribution. To avoid having customers encounter
non-functional relays after the manager upgrade, the upgrade
readiness check marks the older relays as not supported. Customers
should upgrade the relays first before upgrading Deep Security
Manager. (DS-13980)
- The Deep Security console (default port: 4119) now requires clients
to use TLS v1.2 in order to connect. Customers who are using
Windows Powershell for their deployment scripts will need to update
the deployment script to include the line:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12;
prior to the agent download step.
To download the agent to systems that do not support TLS 1.2 at all,
a possible workaround is to host the agent software on a web server
that supports TLS 1.0. Alternatively, you can refer to the Help Center
for instructions on how to allow TLS 1.0 on Deep Security Manager:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/tls-version.html
- Deep Security 11.1 and higher includes a new RESTful API that enables
you to automate the provisioning and maintenance of security via
Deep Security. Go to the Deep Security Automation Center
(https://automation.deepsecurity.trendmicro.com/) to download
the SDKs in the language of your choice and learn how to use
the API.
The focus of the new API, which is continuously updated with new
features and improvements, is on improving the functionality that
exists in the SOAP API. When you start new automation projects, you
should use the new API to benefit from continued support and
maintenance in the long term. The older REST and SOAP APIs that
were provided before Deep Security 11.1 have not changed. They have
been deprecated, so new features will not be added but the existing
API functionality will continue to function as usual.
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
For information about new features that have been added since Deep
Security 11.1, see:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/whats-new.html
Other additional enhancements since Deep Security 11.1:
Enhancement 1: [DSSEG-1944/SEG-19575]
A new password rule has been added for Deep Security
Manager users. Passwords cannot match the username or
username spelled backward (not case sensitive).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 2: [DSSEG-2646]
Deep Security Manager will now automatically select a
valid manager node for NSX communication.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 3: [DSSEG-2364, DSSEG-2488]
Anti-Malware Scan Engine can be displayed and has the
option to enable or disable an Anti-Malware update.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 4: [DSSEG-2273]
Deep Security Agent is now supported on Ubuntu 18.04.
This manager is compatible with the corresponding Deep
Security Agent update.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 5: [DSSEG-2667/SF00646921/SEG-26000]
Improved browser CPU usage when the Deep Security
Manager console is being accessed in Internet
Explorer.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
In addition to fixes that were included in Deep Security 11.1, this
release also resolves the following issues that were identified in
previous versions of Deep Security:
Issue 1: [DSSEG-2241/SEG-21481]
When intrusion prevention events were triggered by the
intrusion prevention module rather than by an intrusion
prevention rule, a syslog sent via Deep Security Manager
would display the severity of the event as 10, but a
syslog sent directly from the Deep Security Agent would
display the severity as 5. In addition, there was a
duplicate protocol name in the protocol field of a
syslog forwarded via Deep Security Manager.
Solution 1: With this release, the severity will be set
consistently to 5 and the protocol name will not be
duplicated.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-2194/SEG-26960]
Content in the DPI_Rule_Recommendation_Report was
truncated when its length was longer than the field.
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-1889]
When the regular expression used for an event-based
task
contained a negation (for example, do not activate a
computer name that begins with a particular string), the
match results were sometimes not as expected.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DS-16854]
During a graceful Deep Security Manager node shutdown,
if the node is for NSX communication, the next Manager
node would be assigned as NSX communication node
regardless of node status, even the node was offline.
Solution 4: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 5: [DSSEG-2521/DSSEG-2218]
This update fixes some security vulnerabilities.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 6: [DSSEG-2240/SEG-28221]
A syslog server encountered errors when a hostname
contained special characters.
Solution 6: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 7: [DSSEG-2190/SEG-26960]
Content in the DPI_Rule_Recommendation_Report was
truncated when its length was longer than the field.
Solution 7: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 8: [DSSEG-2612/SF00991531/SEG-31972]
Some computers on the computers page were not being
sorted alphabetically.
Solution 8: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 9: [DSSEG-2572/SEG-32317/SF01019268]
If the Deep Security Agents report events to the Deep
Security Manager with data that exceeds the size
limitation, the Deep Security Agents show the warning
- "Get Events Failed (Internal server error)" on the
Deep Security Manager web console. The corresponding
system events also indicate an Oracle database error -
ORA-01461.
Solution 9: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 10: [DSSEG-2508/SEG-28221]
A syslog server encountered errors when a hostname
contained special characters.
Solution 10: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 11: [DSSEG-2506]
When the regular expression used for an event-based
task contained a negation (for example, do not
activate a computer name that begins with a particular
string), the match results were sometimes not as
expected.
Solution 11: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 12: [DSSEG-2465/SEG-30293/SF00907480]
In Deep Security Manager 11.0, the SQL connection
string did not allow special characters like {. When
the password used for the Deep Security Manager
connection contained {, the Manager could not connect
to the database to proceed with an installation or
upgrade.
Solution 12: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 13: [DSSEG-2415]
When using the Tag filter in event reports and
dashboard widgets, the event count displayed twice as
many events as it should have.
Solution 13: This issue is fixed in this release. However, events
generated in Deep Security Manager 11.0 will still be
counted twice until all references to those events are
eventually pruned from the system.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 14: [DS-27174/SEG-28457]
When agent self-protection was enabled in a policy and
the policy was duplicated, the duplicate copy of the
policy did not include the correct self-protection
password.
Solution 14: A duplicate policy now includes the agent
self-protection password, if one was specified in the
original policy.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 15: [DSSEG-2707/SEG-34447]
If the Deep Security Manager was responsible for event
forwarding, severity clipping for log inspection events
did not function.
Solution 15: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 16: [DSSEG-2759/SEG-35544]
Data was missing from the "Security Module Usage
Cumulative Report" and the "Security Module Usage
Report".
Solution 16: 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:
- The Deep Security Help Center is available at:
https://help.deepsecurity.trendmicro.com/11_2/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.
- 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 Help Center:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/Get-Started/Install/system-requirements.html
5. Installation
========================================================================
Refer to the "Get Started" section of the Deep Security Help Center:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/install-deep-security.html
6. Known Incompatibilities
========================================================================
For a full list of compatible agents please see
https://help.deepsecurity.trendmicro.com/11_2/on-premise/Manage-Components/Software-Updates/compatibility.html
- When adding vCloud in this version of Deep Security, it must be
added only to the tenants. Adding vCloud to the primary
tenant is not supported.
7. Known Issues in Deep Security Manager 11.2
========================================================================
- When upgrading from Deep Security 11.0 or earlier to version 11.1
or later, Deep Security Manager does not apply auto-tagging to
events that it receives approximately 5 seconds before the service
shuts down. (DS-27880)
-
When Deep Security Agent is running on containers that use an
overlay network, the agent may report a virtual network interface
(like "vx-001000-93cfm" or "flannel.1") to Deep Security Manager.
The virtual network interface should be invisible to Deep Security
Manager. To address this issue, set the firewall rules described
in this Help Center article:
https://help.deepsecurity.trendmicro.com/container-firewall-rules.html
(DS-25863)
- In a Docker environment, when a host reboots, it gets a new NIC
name and MAC address. When that host is protected by a
Deep Security Agent, the agent receives the new interface
information and sends it to Deep Security Manager, which adds it
as a new NIC name and MAC address pair, leading to extra unused
interfaces listed in Deep Security Manager. Deep Security Manager
flags those unused interfaces as an inactive NIC and provides a
"Remove this inactive interface from Deep Security Manager"
checkbox. (DS-25335)
- In the File Lists, the Deep Security Manager does not accept the
Windows file paths that start with a wildcard on the root directory
of a file system. (DS-24983/DSSEG-2420/SF00895643/SEG-29809)
- In Deep Security Manager, the wrong DNS name is sometimes displayed
in the computer editor, under "Overview > General > VMware Virtual
Machine Summary". (DS-24983/DSSEG-2416/SEG-26103)
- When Deep Security Manager sends Anti-malware events to Trend Micro
Control Manager, the time information for the events is sometimes
incorrect. (DS-24142/DSSEG-2232/00832149/SEG-27232)
- After a rule update is applied, some CVE numbers appear multiple
times on the "Policies > Common Objects > Rules > Intrusion
Prevention Rules" page. (DS-25293/DSSEG-2507/00916321/SEG-31435)
- In Deep Security Manager, the screens that display application
control events ("Events & Reports > Events > Application Control
Events > Security Events" and "computer/policy editor > Application
Control > Application Control Events") allow to you click a link
that opens the application rule associated with the event. However,
using those locations to modify an application control rule that's
missing a value (such as the SHA value) will cause an Internal
Server Error. (DS-25146)
- If you are unable to deploy agents using deployment scripts, it
could be because you are using an older version of curl or
PowerShell that does not support TLS 1.2 communication. There are
two workarounds:
Option 1: Upgrade curl to 7.34.0 or later, or upgrade PowerShell to
4.0 or later. These support TLS 1.2.
Option 2: If you are deploying onto Windows XP, 2003, or 2008,
where PowerShell 4.0 is not supported, remove these lines:
#requires -version 4.0
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12;
Or, if you are deploying onto Red Hat Enterprise Linux 6,
which uses curl 7.19 by default, remove this tag:
--tls1.2
For details, see:
https://help.deepsecurity.trendmicro.com/11_2/on-premise/tls-version.html
(DS-24372)
- With this release of Deep Security Manager, new installations have
the TLS protocol version for all communication channels set to
TLS 1.2 by default. If your environment includes Deep Security Agent
9.6 or earlier, the agent activation will fail with this default
configuration. To support Deep Security Agent 9.6 or earlier, switch
the TLS protocol version back to 1.0 using this command:
dsm_c -action settlsprotocol -MinimumTLSProtocol TLSv1
(DS-23761)
- If you are using a VMware NSX for vShield Endpoint or a Standard
license of NSX, the "NSX Security Group Change" event-based task in
Deep Security will not be triggered until Deep Security is manually
synchronized with the vCenter/NSX Manager. For example, when a
computer is moved from an unprotected security group to a protected
security group, the protection will not be triggered automatically
until the next manual NSX synchronization. (DS-8864)
- When performing a silent install of Deep Security Manager on
Red Hat Enterprise Linux, the install may fail if you have installed
Java via Yum, due to a missing font. To work around this issue,
add a /etc/fonts/local.conf file with this content:
serif
Utopia
sans-serif
Utopia
monospace
Utopia
dialog
Utopia
dialoginput
Utopia
"
(DS-15872)
- 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)
- There is an issue when a virtual machine (VM) is protected
agentlessly by a Deep Security Virtual Appliance and the VM is
moved (using vMotion) from ESX A to ESX B, where both ESX A and
ESX B have an appliance installed. In that scenario, the source
appliance stores some temporary data to a relay and the target
appliance downloads the package from the relay. However, if the
relay is disabled, deleted, or deactivated, the target appliance
is not able to download the package and it could fail to restore
some data (such as the integrity monitoring baseline) on the
target appliance. (DS-18684)
- In a multi-tenant environment, the primary tenant (t0) can share
its default relay group with other tenants (tn), and the tenants
(tn) can choose to use the t0's default relay group or its own
relays.
If a tn enables relays in its own default relay group but
then changes their settings to use the t0's default relay group,
the tn user will not be able to see their own relays on the Relay
Management page in Deep Security Manager.
To see those relays again, the tn can use this procedure:
1. Stop using the t0's default relay group.
2. The tn's own relays will appear again on the Relay Management
page. Move those relays to another group (something other than
the default relay group).
3. Start using the t0's default relay group again. The tn will be
able to see their relays in the group used in step 2.
(DS-18687)
- Disabling the relay feature on a Windows 10 agent can sometimes
take more than ten minutes to complete. (DS-18685)
- The new Relay Management page does not allow users to add or
modify relay group descriptions. (DS-15947)
- 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)
- If you are using application control with a global ruleset and
want to delete multiple hash values from the ruleset, you must
delete them one by one.
(DS-17474)
- After upgrading to Deep Security Agent 11.1 or higher, the
Security Update Status for the agent may change from "Up-to-Date"
to "Out-of-Date" due to a synchronization issue with the Trend
Micro Active Update Server. To fix this, trigger a security update
for the agent. (DS-16996)
- Due to a known issue with the VMWare EPSec API, an advanced threat
detection (machine learning) query will be initiated again when
deleting files and moving them to the recycle bin. This make the
deleting process slower. This only happens for soft-deletes (moving
the files to the recycle bin). If a user chooses to delete the
files from hard disk directly (hard-delete), the issue will not
happen. (DS-14032)
- When using a Deep Security Virtual Appliance deployed in an NSX
environment, after turning on a protection module and applying a
rule to a protected VM, then when switching between protection
module tabs in Deep Security Manager, the status may display "Not
Activated" for a brief time before correctly displaying the correct
state (for example, "On, 1 rule"). (DS-12380)
- You must import software patch packages (in the form of .dsp files)
before deploying the Deep Security Virtual Appliance or upgrading
it to a newer version. If you see "Event 710 (.dsp xxx patch
package is not found)" in the Deep Security Manager system events,
it indicates that the patch package for the appliance has not been
imported yet. To resolve this event, go to the Deep Security
software download page
(https://help.deepsecurity.trendmicro.com/software.html) and import
the patch package. (DS-16981)
- 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 (AMSP) 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)
- 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)
- 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)
- AWS instance types have different throughputs and computing
resources. Shared ruleset creation time can vary widely depending
on the instance type and may take an hour or longer on m3.medium
and smaller instances. (DS-13747)
- In environments with Integrity Monitoring enabled and a large
number of computers, the database may experience high CPU. This
applies to Microsoft SQL Server databases. To resolve the issue
maintenance on the 'entitys' table should be done using the
'EXEC sp_updatestats' command. (DS-10471)
- Upgrading to Deep Security 11.1 or higher with an Oracle 12c
Database is not supported in a multi-tenant deployment. (DS-8139)
- Using Windows 10 Edge as your browser for DSM may show certificate
errors. Microsoft Edge is a web browser included in Windows
10/2016 operation systems. Unlike IE, the Edge browser does not
have a configuration option for Trusted Sites which allows the
user to add websites (e.g. the DSM URL). However, administrators
can still add the DSM URL to the list of trusted sites from the
Control Panel (Control Panel > Network and Internet >
Internet Options > select Security). (DS-4618)
- Online Help Search does not support special characters such
as "!", "#" and "%". (DS-6453)
- A "Refresh" notification appears on the UI after undoing an action
in Application Control. (DS-10151)
- Using a Safari browser, the filter search option in Application
Control under the ACTIONS tab only works one time, then you need to
flip to another tab and back to do another search. On Chrome,
Firefox and IE11 it works every time. (DS-7844)
- In Application Control, the drift number and button for "ALLOW ALL"
or "BLOCK ALL" on the Action tab won't reflect the last executed
state after user switches to any other page. The information
displayed on the Action tab page will depend on how many
unrecognized software items are being allowed or blocked by the
current action, and if the number of items is very large then the
page will take longer to be updated. (DS-10294)
- In the Application Control > Actions tab page, it takes longer than
expected to display the first drift card, and if there is a huge
amount of drift, the performance is affected. (DS-9808)
- When using Application Control, if the existing rule set is large,
it can take several minutes to enforce the action on the Agent
protecting the computer. (DS-9464)
- 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)
- When using Trend Micro Control Manager (TMCM) with a locally
installed Smart Protection Server (SPS) for the Connected
Threat Defense feature, Deep Security (DS) will not only
take the action according to Deep Security Web Reputation
features (Security Level /score) but also take action
according to Control Manager/Smart Protection Server (Log
or Block for a URL). However, DS blocking page and events
still show the risk information instead of specific
action/reason or category information for this.
For example:
1. Some pages rated/shown with Suspicious Risk Level are
blocked when user setting of Web Reputation Security Level
is Medium, to block Dangerous and Highly Suspicious pages
2. Some Web Reputation events are log events instead of block
events and the user can't tell which is log event in DSM Web
Reputation event pages. To clearly know this information,
the user needs to login to TMCM to view the web reputation
events with action/reason information. (DS-3947)
- When using TMCM 6.0 SP3, a user-defined Suspicious Object doesn't
have a filterCRC value and therefore Deep Security cannot
detect/block this type of file. (DS-768)
- When using Connected Threat Defense, sometimes, the "Submission
Status" field of Identified files may become "Report
Unavailable" because DS can't get the analysis result
from Deep Discovery Analyzer for the submission over one day.
DS will no longer wait for the result of this submission and the
user will have to choose the identified file (event) and button
to submit the file to Deep Discovery Analyzer manually. Then,
DSM will submit the file, reset the submission date, and
wait/retrieve for DDAn analysis result again. (DS-98)
- When using a Policy with SAP turned on, if the SAP license has
expired, although it may appear on the DSM UI as though the SAP
Policy is still On, the policy sent to Agents will have SAP off.
SAP will not run on an Agent with an expired license. (DS-4534)
- With the SAP module enabled and Netweaver running on the same
host, when a realtime scan detects a malicious file it will be
reported twice. To prevent this, users should add the Netweaver
GUI process path e.g. "C:\Program Files
(x86)\SAP\FrontEnd\SAPgui\saplogon.exe" to their AM realtime scan
exclusion list. (DS-6615)
- When a user disables the scanner functionality and
then enables the Relay after assigning a Scanner "On" policy to
this Relay-enabled Agent, then deactivating and reactivating the
Agent, on the Computer details page there will be a delay in
display showing scanner icon and information first, then change
to relay icon and information. (DS-4988)
- When using Deep Security Scanner (SAP for Windows) to successfully
scan and block MIME types for graphics files such as jpg, bmp and
gif on the SAP WinGUI, administrators should enable the
configuration parameter SCANBESTEFFORT. (DS-2499)
- When using Deep Security Scanner (SAP for Windows), when a file
extension does not match the MIME Type of file itself, the scan
for virus will take some time, and the Rule Violation error will
not appear shortly. (DS-2484)
- When using Deep Security Scanner (SAP for Windows) and the block
MIME Type is set to application/zip on the SAP WinGUI, the scan
will proceed but will not block the .zip file immediately and
will take some time to return the result if the .zip file is
large. (DS-2470)
- When using Deep Security Scanner (SAP for Windows), if the file
to be scanned exceeds the DSM scan size limitation then instead
of an "Extracted file size exceeded the limit" error, a
"Skip file error" result will be returned. (DS-2002)
- When using Deep Security Scanner (SAP for Windows), there is a
difference in compressed files scan behavior between .zip and
.sar file types. If the file to be scanned is a .sar file and the
scanned file, when extracted, is larger than the Scan Limit
configured on the DSM, then the scan will be skipped. For .zip
files, the scan will be completed as long as the scanned file,
when extracted is smaller than the Extract size configured through
the SAP profile (DS-1126)
- When using Anti-Malware with containers there is currently no
ability to specify paths within containers when defining policy for
inclusion / exclusion lists. (DS-11086/DS-16030)
- Users should take care when manually adding a zip file to
Administration > Software > Local. If the original filename is not
maintained (as on the Download Center) it will not deploy correctly
to Agents. For example downloading a second copy of an Agent file
can result in a file named something like this:
Agent-amzn1-11.1.2-7690.i386 (1).zip. (DS-11078)
- 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)
- 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)
- In an Agentless environment with a GuestVM Windows Server 2008
R2 64-bit protected by a DSVA, the SAP Configuration page will
display "Platform not supported." (DS-4987)
- If DSVA is configured in Agent-Initiated mode, user cannot
successfully activate the guest agents via DSM's web UI. A
"Protocol error" is shown in the web UI. The best practice for
deploying DSVA is bi-directional mode. (DS-9924)
- Some platforms (e.g. Linux) do not distinguish network interfaces
at the packet level, when they are connected to the same network.
When enabling "Policy -> Interface Types -> Rules can apply to
specific interfaces" on these platforms, firewall policies that
attempt to distinguish between network interfaces connected to the
same network will result in only one of the policies being applied.
[29543]
- The Trusted Platform Module (TPM) monitoring does not work on
vSphere 6 environment. When enabled, the event "The vCenter sent
empty or unreliable TPM information that has been ignored. This is
only an issue if the problem persists" will appear. In rare
circumstances, the value may also be unreliable on vSphere 5.5
environment. VMware is already investigating this issue.
[29268/27166]
- When doing vMotion of many simultaneous VMs, some of the VMs may
appear as Anti-Malware Engine Offline after it moves to the new
host. This occurred because the DSM checked the status of the VMs
during heartbeat before the vMotion is finished. Doing another
check status or waiting for the next heartbeat will fix the status.
[28825]
- Deep Security Azure Connector does not identify virtual machines
created by Azure Resource Manager a.k.a ARM VM (v2). DSA installed
in ARM VM will not be included in Azure connector but in normal
computer list. This limitation will have no impact on security
features provided by Deep Security. [29630]
- If vMotion occurs while Anti-Malware scan is happening, there is a
possibility that the scan will not continue after moving from one
Agentless protected host to another. If you see an event saying
"Manual Malware Scan Failure" or if you see a "Manual Malware Scan
Started" without a corresponding "Manual Malware Scan Completed",
then this means that the scan has stopped and did not finish.
[28059]
- During the upgrade process after removing the Filter Driver, Deep
Security Manager will display "Intrusion Prevention Engine Offline
and Firewall Engine Offline" regardless of policy until the Deep
Security Virtual Appliance is upgraded.[28992]
- If the Deep Security Relay is down during deployment of Deep
Security Virtual Appliance, it will fail to upgrade
and will cause the vShield Endpoint to not register. Even after the
Deep Security Virtual Appliance upgrade becomes successful, the
vShield Endpoint will remain in a Not Registered state.
Reactivating the Deep Security Virtual Appliance will resolve this
issue. [28712]
- 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 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]
- 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 Security 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]
- The Deep Security Manager will display the platform of CentOS
machines as Red Hat. This is because the agent package used in
CentOS and Red Hat are the same and labeled as Red Hat 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, Deep Security Manager 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 in Azure cloud will not be
managed under Azure cloud account in the Deep Security Manager.
The agent will appear under normal computers list. [26499]
- 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]
- 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 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 Server 2008 and Windows 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 vf.
This will cause any newly Deep Security Virtual Appliance-
protected virtual machines to not have Anti-Malware enabled.
The workaround is to uninstall and reinstall the driver
through the VSM.
[Deep Security 8.0-01036]
- 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
Help Center 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.
8. Release History
========================================================================
Deep Security Manager 11.2.225, October 10, 2018
Deep Security Manager 11.2.225, October 10, 2018
9. Files Included in This Release
========================================================================
This release is a complete installation. Use one of the
following files:
Manager-Linux-11.2.225.x64.sh (64-bit)
Manager-Windows-11.2.225.x64.exe (64-bit)
10. Contact Information
========================================================================
A license to 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, you must renew Maintenance 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.
11. 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.
12. License Agreement
========================================================================
View information about your license agreement with Trend Micro at:
https://www.trendmicro.com/en_us/about/legal.html
Third-party licensing agreements can be viewed by selecting the
"About" option in the application user interface.
13. 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.