（情報元のブックマーク数
Trend Micro Deep Security 9.6 Service Pack 1 Patch 1 Update 7 リリースが4月20日予定とのこと。
Trend Micro Deep Security 9.6 Service Pack 1 Patch 1 Update 7 を下記日程にて公開いたしました。
■ 公開開始日
2017 年 04 月 20 日 (木)
■ 対象モジュール
Deep Security Manager
Deep Security Virtual Appliance
Linux 版 Deep Security Agent
Windows 版 Deep Security Agent
Windows 版 Deep Security Notifier
■ 追加機能/修正内容
オフラインエージェントへの予約検索実行に関するオプションが追加されました。
※上記機能はReadmeの「Enhancement 4」の内容に該当します。
その他の追加機能や修正内容は付属のReadmeをご覧ください。
※日本語のReadmeは一か月以内に公開いたします。
繧オ繝昴?シ繝域ュ蝣ア : 繝医Ξ繝ウ繝峨?槭う繧ッ繝ュ
Manager
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancements are included in this release:
Enhancement 1: [DSSEG-718/SEG-692]
Standard time in Turkey has changed from GMT+2 to
GMT+3.
Solution 1: In this release, the bundled JRE has been updated to
version 1.8.0_121, which resolves this issue.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 2: [DSSEG-484]
Collecting a Deep Security Manager diagnostic package
using the dsm_c command with verbose enabled
sometimes failed to include the debug.xml if there
were more than 5000 hosts.
Solution 2: This release has resolved this issue; however, for
larger numbers of hosts (>10 000), the JVM memory for
dsm_c.exe may need to be increased. This is done by
creating a file named dsm_c.vmoptions and including,
for example, "-Xmx2g" to increase memory to 2GB.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 3: [DSSEG-435]
When VMware Distributed Power Management puts an ESXi
host in standby/power off mode, Deep Security Manager
needs to handle the notification from vCenter to shut
down the Deep Security Virtual Appliance. Previously,
the Deep Security Virtual Appliance would prevent the
ESXi from entering standby/power off mode.
Solution 3: With this release, Deep Security Manager now will
turn off the Deep Security Virtual Appliance when an
ESXi host is going into standby mode, which allows
the ESXi host to enter standby mode.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 4: [DSSEG-361]
This release adds the ability to specify a timeout
value for scheduled malware scans. You can see the
new option by going to Administration > Scheduled
Tasks and adding or editing a "Scan Computers for
Malware" scheduled task. The timeout option is
available for daily, weekly, monthly, and once-only
scans. It is not available for hourly scans. When a
scheduled malware scan is running and the timeout
limit has been reached, any tasks that are currently
running or pending will be cancelled.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issue(s):
Issue 1: [DSSEG-892]
Deep Security Manager used a Long type when composing
an SQL query on an integer-type data field, which
resulted in a class case exception.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-884/SEG-2247]
When Deep Security updated its components, some
computers appeared out of date on the Security
Updates page. The out-of-date warning message could
persist for more than an hour.
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-865]
An error would occur when a user allowed a
quarantined spyware via Events & Reports > Events >
Anti-Malware Events > Quarantined Files.
Solution 3: This issue is resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DSSEG-842/SEG-3748/SF00372864]
In a deployment that includes the Deep Security
Virtual Appliance, if there are two data centers with
the same name located in the same vCenter (but in
different folders), the appliance information page
could display incorrect folder information.
Solution 4: This issue is resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 5: [DSSEG-831/SEG-392]
When Deep Security Manager performed a Synchronize
VMware vCenter job and the job could not be
completed, it occupied Deep Security Manager
resources and other jobs could not be processed.
Solution 5: This hot fix adds a timeout value to the Synchronize
VMware vCenter job. If the job cannot be finished
within two minutes, Deep Security Manager will
terminate the job so that other jobs will not be
affected.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 6: [DSSEG-774]
When a user manually added a computer to the Deep
Security Manager console and also imported the
vCenter containing the computer, Deep Security
Manager would raise a duplicate UUID alert.
Solution 6: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 7: [DSSEG-749]
When Deep Security Manager was using Microsoft SQL
Server 2008 R2 or earlier, the Deep Security Manager
console was unable to show an instance list under a
vCloud connector that contained more than 500
activated instances.
Solution 7: This issue is resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 8: [DSSEG-669/SEG-452]
When the Deep Security Manager performed a computer
discovery operation, it sometimes detected virtual
machines that did not exist. This was caused by a bug
in the JRE that is fixed in JRE 1.8u102 build 35.
Solution 8: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 9: [DSSEG-624/SEG-1068]
"Unable to communicate" alerts were still raised,
even after the "Raise Offline Errors For Inactive
Virtual Machines" setting was disabled. In addition,
"Unable to communicate" alerts were not raised when a
virtual machine was suspended.
Solution 9: These issues are fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 10: [DSSEG-785/SEG-551/SEG-551]
In the "Anti-Malware Protection Status" widget (on
the Deep Security Manager Dashboard), clicking the
"Unprotected" number would display incorrect results.
Solution 10: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~