Trend Micro Deep Security 9.6 Service Pack 1 Patch 1 Update 19 公開のお知らせ:サポート情報 : トレンドマイクロ
Trend Micro Deep Security 9.6 Service Pack 1 Patch 1 Update 19 リリース
Deep Security 9.6 Service Pack 1 Patch 1 Update 19 のモジュールを公開いたしました。
■ 公開開始日2018 年 10 月 9 日 (火)
■ 対象モジュール
Deep Security Manager
Linux 版 Deep Security Agent
Windows 版 Deep Security Agent
Windows 版 Deep Security Notifier
■ 追加機能/修正内容追加機能や修正内容は付属の Readme をご覧ください。
※日本語のReadmeは一か月以内を目安に公開いたします。■ 入手方法
Deep Securityヘルプセンターからダウンロードできます。
サポート情報 : トレンドマイクロ
「Deep Securityヘルプセンター」
また、以下の製品 Q&A も合わせてご参照ください。
Update プログラムとは
Deep Security Manager 9.6 Service Pack 1 Patch 1 Update 19
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-2738/SEG-34426/SEG-11143] The numbers displayed in the Reconnaissance section of an Attack Report were incorrect. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-2461/VRTS-2089/JPSE-394] This update fixes some security vulnerabilities. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 3: [DSSEG-2362/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 3: A duplicate policy now includes the agent self- protection password, if one was specified in the original policy. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 4: [DSSEG-2232/SEG-27232/00832149] When Deep Security Manager sent Anti-Malware events to Trend Micro Control Manager, the time information for the events was incorrect. Solution 4: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 5: [DSSEG-2013/SEG-23253] The "Learn More" link on the Development Scripts screen did not work. Solution 5: The links works now. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 6: [DSSEG-1469/SEG-13304] During a graceful Deep Security Manager node shutdown, if the node is for NSX communication, the next manager node will be assigned as an NSX communication node regardless of node status, even the node is offline. Solution 6: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deep Security Agent 9.6 Service Pack 1 Patch 1 Update 19 for Linux
2. What's New ======================================================================== 2.1 Enhancements ===================================================================== There are no enhancements in this release. 2.2 Resolved Known Issues ===================================================================== This release resolves the following issue: Issue 1: [DSSEG-2737/SEG-34502] When a TCP connection was established with the same tuples as a previously tracked one, the network engine could set the connection track to an incorrect status. This sometimes happened on a busy server where rapid connections reused a recycled connection. The network engine treated it as an "Out of connection" error and dropped the packet. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deep Security Agent 9.6 Service Pack 1 Patch 1 Update 19 for Windows, and Deep Security Notifier 9.6 Service Pack 1 Patch 1 Update 19 for Windows
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-2737/SEG-34502] When a TCP connection was established with the same tuples as a previously tracked one, the network engine could set the connection track to an incorrect status. This sometimes happened on a busy server where rapid connections reused a recycled connection. The network engine treated it as an "Out of connection" error and dropped the packet. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-2395/SEG-27008/825021] AMSP could cause system hang when verifying signature of a file. Solution 2: The issue has been fixed. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~