Trend Micro Deep Security 9.6 Service Pack 1 Patch 1 Update 18 公開のお知らせ：サポート情報 : トレンドマイクロ
（情報元のブックマーク数 
Trend Micro Deep Security 9.6 Service Pack 1 Patch 1 Update 18 リリース
Deep Security 9.6 Service Pack 1 Patch 1 Update 18 のモジュールを公開いたしました。
■ 公開開始日2018 年 8 月 24 日 (金)
■ 対象モジュール
Deep Security Manager
Linux 版 Deep Security Agent
Windows 版 Deep Security Agent
Windows 版 Deep Security Notifier
■ 追加機能/修正内容追加機能や修正内容は付属の Readme をご覧ください。
※日本語のReadmeは一か月以内を目安に公開いたします。■ 入手方法
Deep Securityヘルプセンターからダウンロードできます。
サポート情報 : トレンドマイクロ
「最新版ダウンロードページ」
また、以下の製品 Q&A も合わせてご参照ください。
Update プログラムとは
Deep Security Manager 9.6.4184 for Linux-x64
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancement is included in this release:
Enhancement 1: [DSSEG-2234/00838640/00838640/SEG-27876]
Added support for TLS 1.2. Deep Security Manager can
now communicate with agents that only support TLS 1.2.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issues:
Issue 1: [DSSEG-2560]
If you misuse firewall rules to block Address
Resolution Protocol (ARP) traffic, you see 'Agent
offline' issues in Deep Security Manager. This problem
occurs because other necessary traffic (DNS or DHCP)
is blocked even though ARP traffic is passed through
the network engine. This fix allows you to bypass this
necessary traffic through a Deep Security
Manager control.
Solution 1: This issue is resolved by adding hidden 'Force Allow'
firewall rules for ARP. Additionally, you can control
whether to 'force allow' DNS, DHCP, and ICMP packet
fragments using the new 'Force Allow DHCP
DNS' and 'Force Allow ICMP type3 code4' settings. To
find these settings, go to the manager's Policy editor
or the Computer editor and click Settings > Advanced.
See the Deep Security Help Center for details. You
might consider disabling DNS, DHCP, and ICMP if
security concerns outweigh 'Agent offline' messages.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-2232/00832149/SEG-27232]
When Deep Security Manager sent Anti-malware events to
Trend Micro Control Manager, the time information for
the events was incorrect.
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-2190/SEG-26960]
Content in the DPI_Rule_Recommendation_Report was
truncated when its length was longer than the field.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DSSEG-2013/SEG-23253]
The "Learn More" link on the Development Scripts
screen did not work.
Solution 4: The links works now.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deep Security Agent 9.6.2-8587 for amzn1
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-2587]
When the firewall feature was enabled, Deep Security
Agent was not registered to the Windows Security Center
on Windows 10 version 1803 (April 2018 Update). This
caused the status of firewall to be incorrect in the
Windows Security Center and Windows Defender Security
Center.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-2519]
In previous releases, the Deep Security Agent for
Linux dropped ARP packets. This sometimes led to
configuration issues.
Solution 2: On Linux, the Deep Security Agent logs ARP packets
instead of dropping them.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-2306/SEG-26904]
When a security event syslog was forwarded directly
from the Deep Security Agent to a syslog server, it
contained an incorrect IPv6 address in the dvchost
field.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deep Security Notifier 9.6.2-8587 for Windows-i386
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-2587]
When the firewall feature was enabled, Deep Security
Agent was not registered to the Windows Security
Center on Windows 10 version 1803 (April 2018 Update).
This caused the status of firewall to be incorrect in
the Windows Security Center and Windows Defender
Security Center.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-2306/SEG-26904]
When a security event syslog was forwarded directly
from the Deep Security Agent to a syslog server, it
contained an incorrect IPv6 address in the dvchost
field.
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deep Security Agent 9.6.2-8587 for Windows-x86_64
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-2587]
When the firewall feature was enabled, Deep Security
Agent was not registered to the Windows Security
Center on Windows 10 version 1803 (April 2018 Update).
This caused the status of firewall to be incorrect in
the Windows Security Center and Windows Defender
Security Center.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-2306/SEG-26904]
When a security event syslog was forwarded directly
from the Deep Security Agent to a syslog server, it
contained an incorrect IPv6 address in the dvchost
field.
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
