Trend Micro Deep Security 9.5 Service Pack 1 Patch 3 Update 4 リリース。
Trend Micro Deep Security 9.5 Service Pack 1 Patch 3 Update 4 を下記日程にて公開いたします。
■ 公開開始日
2017 年 04 月 10 日 (月)
■ 対象モジュール
Deep Security Manager
Deep Security Virtual Appliance
Linux 版 Deep Security Agent
Windows 版 Deep Security Agent
Windows 版 Deep Security Notifier
■ 追加機能/修正内容
追加機能や修正内容は付属のReadmeをご覧ください。
※日本語のReadmeは一か月以内に公開いたします。
繧オ繝昴?シ繝域ュ蝣ア : 繝医Ξ繝ウ繝峨?槭う繧ッ繝ュ
2. What's New ======================================================================== 2.1 Resolved Known Issues ===================================================================== This release resolves the following issues: Issue 1: [DSSEG-907/SEG-3551] The Deep Security Agent created temporary files in the temp directory but these files were not removed after use, which resulted in disk space filling up. Solution 1: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 2: [DSSEG-776/SEG-2048/TT-338431] The NIC teaming features used in Windows 2012 R2 led to duplicate or triplicate packets. If the NIC teaming sets NIC to promiscuous mode and the related port in the switch is set to trunk mode, the NICs will receive duplicate packets. A stop error on a blue screen happened due to a race condition in the Deep Security filter driver when these duplicate or triplicate packets were handled in separate threads and one of the threads was touching functions that had not been initialized by other threads. Solution 2: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 3: [DSSEG-710] When the Deep Security Agent generated Web Threat Protection (WTP) syslog messages, it did not follow the syslog format. When the syslog is set to "direct forward" from the agent, the log message should be Common Event Format (CEF). Solution 3: This issue is fixed in this release. The WRS Syslog format is now CEF. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Issue 4: [DSSEG-460] When the Intrusion Prevention rule "1000128 - HTTP Protocol Decoding" is enabled and "Specify raw characters that are not allowed in the URI:" is used, when the Deep Security Agent detects an illegal character, the Deep Security Manager will show the illegal character in an Intrusion Prevention event. However, the Deep Security Agent sometimes did not report the correct location of the illegal character, so it was not displayed correctly in the Deep Security Manager. Solution 4: This issue is fixed in this release. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~