Trend Micro Deep Security 9.6 Service Pack 1 Patch 1 Update 16 公開のお知らせ：サポート情報 : トレンドマイクロ
（情報元のブックマーク数 
Trend Micro Deep Security 9.6 Service Pack 1 Patch 1 Update 16リリース。
Deep Security 9.6 Service Pack 1 Patch 1 Update 16 のモジュールを公開いたしました。
■ 公開開始日
2018 年 3 月 27 日 (火)■ 対象モジュール
Deep Security Manager
Deep Security Virtual Appliance
Linux 版 Deep Security Agent
Windows 版 Deep Security Agent
Windows 版 Deep Security Notifier
■ 追加機能/修正内容
追加機能や修正内容は付属の Readme をご覧ください。
※日本語のReadmeは1か月以内を目安に公開いたします。■ 入手方法
サポート情報 : トレンドマイクロ
本製品の各コンポーネントは最新版ダウンロードページの「統合サーバセキュリティ対策」カテゴリからダウンロードできます。
「最新版ダウンロードページ」
また、以下の製品 Q&A も合わせてご参照ください。
Update プログラムとは
■製品サポート情報
ご不明な点がございましたら、弊社サポートセンターまでお問合せください。
お問合せ方法については、こちらをご確認ください。
Deep Security Manager 9.6 SP1 Patch1 Update16
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
There are no enhancements in this release.
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issues:
Issue 1: [DSSEG-1841/SEG-20215]
The folder name in the Windows Agent deployment script
for Asiainfo Security was not correct.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-1820/SEG-20095]
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 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-1766/SEG-1268]
When using an Oracle database as the Deep Security
database in an agentless deployment (no combined mode
on agents), the agent records would have an "anti-
malware scheduled scan state" of 1 when a scheduled
anti-malware scan began. This happened only when there
were more than 501 agents. The expected behavior is
that only virtual agent records would be updated with
the anti-malware scan status.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ESXi4.1をサポートしないらしい（まぁ、流石にないだろうけど）
- Deep Security 9.6 Service Pack 1 Patch 1 Update 16 does not
support ESXi version 4.1. To deploy Deep Security 9.6 Service Pack 1
Patch 1 Update 16, 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
Deep Security Virtual Appliance 9.6 SP1 Patch1 Update16
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancement is included in this release:
Enhancement 1: [DSSEG-2092/SEG-6472/SEG-6201]
When the kernel module (gsch) in Deep Security Agent
Anti-malware feature in Linux was loaded and hooked a
system call, unloading the gsch module or disabling
the Anti-malware feature would cause a system crash
if other vendor's kernel module was hooking the system
call later than the gsch driver.
Solution 1: The issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issues:
Issue 1: [DSSEG-2064/SEG-21385/00673856]
When Deep Security Agent failed to download new kernel
modules of both Anti-Malware and Firewall, it expected
to try downloading those modules again. However, if
only the Anti-Malware kernel module was successfully
downloaded, Deep Security Agent sometimes did not
retry downloading Firewall kernel module. As a
result, the new kernel module was not loaded and it
sometimes triggered a Firewall Engine offline issue
on Amazon Linux.
Solution 1: The issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-1993]
Deep Security Agent incompatibilities with c5 and m5
instance types in AWS Elastic Compute Cloud (EC2)
running Linux operating systems caused an issue where
computers that failed to be correctly identified were
activated outside of an AWS cloud connector, were not
assigned EC2 metadata, and may not have been assigned
the expected security policy. In these cases,
assigning a security policy or relay groups based on
EC2 metadata – using Event Based Tasks (EBTs) for
example - was incorrect. In addition, consumption-
based billing for large instances was incorrect.
Existing EC2 instance types that have Deep Security
Agents already installed or newly deployed are
unaffected. For details, please refer to:
https://success.trendmicro.com/solution/1119433
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-1830/SEG-20057/DSSEG-1988]
When an Agent self-updated or installed a new Kernel
Support Package, some of the installed files would
have incorrect permissions.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Linux 版 Deep Security Agent / Relay 9.6 SP1 Patch1 Update16
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancement is included in this release:
Enhancement 1: [DSSEG-2092/SEG-6472/SEG-6201]
When the kernel module (gsch) in Deep Security Agent
Anti-malware feature in Linux was loaded and hooked a
system call, unloading the gsch module or disabling
the Anti-malware feature would cause a system crash
if other vendor's kernel module was hooking the system
call later than the gsch driver.
Solution 1: The issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issues:
Issue 1: [DSSEG-2064/SEG-21385/00673856]
When Deep Security Agent failed to download new kernel
modules of both Anti-Malware and Firewall, it expected
to try downloading those modules again. However, if
only the Anti-Malware kernel module was successfully
downloaded, Deep Security Agent sometimes did not
retry downloading Firewall kernel module. As a
result, the new kernel module was not loaded and it
sometimes triggered a Firewall Engine offline issue
on Amazon Linux.
Solution 1: The issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-1993]
Deep Security Agent incompatibilities with c5 and m5
instance types in AWS Elastic Compute Cloud (EC2)
running Linux operating systems caused an issue where
computers that failed to be correctly identified were
activated outside of an AWS cloud connector, were not
assigned EC2 metadata, and may not have been assigned
the expected security policy. In these cases,
assigning a security policy or relay groups based on
EC2 metadata – using Event Based Tasks (EBTs) for
example - was incorrect. In addition, consumption-
based billing for large instances was incorrect.
Existing EC2 instance types that have Deep Security
Agents already installed or newly deployed are
unaffected. For details, please refer to:
https://success.trendmicro.com/solution/1119433
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-1830/SEG-20057/DSSEG-1988]
When an Agent self-updated or installed a new Kernel
Support Package, some of the installed files would
have incorrect permissions.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Windows 版 Deep Security Agent / Relay / Notifier 9.6 SP1 Patch1 Update16
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
There are no enhancements in this release.
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issues:
Issue 1: [DSSEG-2086/SEG-21208]
Deep Security Agent restarted abnormally along with an
"Unable to send data to Notifier app. " error message
in ds_agent.log.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-1993]
Deep Security Agent incompatibilities with c5 and m5
instance types in AWS Elastic Compute Cloud (EC2)
running Linux operating systems caused an issue where
computers that failed to be correctly identified were
activated outside of an AWS cloud connector, were not
assigned EC2 metadata, and may not have been assigned
the expected security policy. In these cases,
assigning a security policy or relay groups based on
EC2 metadata – using Event Based Tasks (EBTs) for
example - was incorrect. In addition, consumption-
based billing for large instances was incorrect.
Existing EC2 instance types that have Deep Security
Agents already installed or newly deployed are
unaffected. For details, please refer to:
https://success.trendmicro.com/solution/1119433
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
