Trend Micro Deep Security 11.0 Update 9 公開のお知らせ：サポート情報 : トレンドマイクロ＠累積修正っぽい

Trend Micro Deep Security 11.0 Update 9 公開のお知らせ：サポート情報 : トレンドマイクロ

Deep Security 11.0 Update 9 のモジュールを公開いたしました。
■ 公開開始日
2019 年 4 月 18 日 (木)
■ 対象モジュール
Deep Security Manager
Linux 版 Deep Security Agent
Unix 版 Deep Security Agent
Windows 版 Deep Security Agent
Windows 版 Deep Security Notifier
■ 追加機能/修正内容
追加機能や修正内容は付属の Readme をご覧ください。
※日本語のReadmeは一か月以内を目安に公開いたします。
サポート情報 : トレンドマイクロ

Deep Security Manager

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(s):
   
   Issue 1:    [DSSEG-3640/SEG-46443/SF01689893]
               A high event ingest volume sometimes caused deadlocks in
               Microsoft SQL Server when outdated events were being
               removed.
   
   Solution 1: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 2:    [DSSEG-3611]
               When upgrading Deep Security Agent 9.0 for AIX 7.2, Deep
               Security Manager did not display the latest agent
               software versions in the 'Agent Version' drop-down list
               on the 'Upgrade Agent Software' dialog box.
			   
   Solution 2: This issue is fixed in this release.			   
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 3:    [DSSEG-3608]
               Scheduled Tasks to "Check for Security Updates" now have 
			   an optional timeout field, which is used to select the 
			   window of time after the scheduled start time in which 
			   security updates may be started.
			   
   Solution 3: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 5:    [DSSEG-3543/SF00852049/SEG-35448]
               Event-based tasks with patterns that matched negative
               regular expressions yielded more accurate matches.
   
   Solution 5: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 6:    [DSSEG-3500/VRTS-3079/01692957]
               An unexpected privilege escalation sometimes happened
               when editing Deep Security Manager's contact properties.
   
   Solution 6: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Linux 版 Deep Security Agent

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(s):
   
   Issue 1:    [DSSEG-3695/1939658/SEG-49191]
               The "Send Policy" action failed because of a
               GetDockerVersion error in Deep Security Agent.
   
   Solution 1: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 2:    [DSSEG-3661/SEG-43300/SF01593513]
               Deep Security Agent failed to install on Ubuntu 18.04.
   
   Solution 2: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 3:    [DSSEG-3653/01746052/SEG-46912]
               Anti-Malware events displayed a blank file path with
               invalid Unicode encoding.
   
   Solution 3: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 4:    [DSSEG-3652/SF01919585/SEG-48728]
               Deep Security Agent sent invalid JSON objects in response
               to Deep Security Manager, which caused errors in Deep
               Security Manager's log file.
   
   Solution 4: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 5:    [DSSEG-3632/SF01328464/SEG-46345]
               Deep Security Agent running on a Linux computer did not
               generate quarantine events for files with the detection
               name PACP_XXX.
   
   Solution 5: This issue is fixed in this release
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 6:    [DSSEG-3587/SF01804378/SEG-47425]
               Deep Security Agent did not add Python extension module
               (PYD) files to the inventory of Application Control.
   
   Solution 6: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 7:    [DSSEG-3552/SF01607298/SEG-43341]
               When the Application Control driver failed to load (for
               example, if the driver was corrupted during a Deep
               Security Agent upgrade), the agent sent system events to
               Deep Security Manager repeatedly as it tried to reload
               the driver. The large number of generated events consumed
               database storage and made the System Events extremely
               slow to load.
   
   Solution 7: This issue is fixed in this release. The Application
               Control driver loading exception is now tracked and the
               Application Control server is stopped after 5 failed
               attempts to load the driver.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 8:    [DSSEG-3515/SEG-45832]
               Deep Security Agent process potentially crashed when
               the detailed logging of SSL message was enabled and
               outputed.
   
   Solution 8: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 9:    [DSSEG-3246/SF01358696/SEG-38712]
               The tbimdsa engine sometimes caused a system crash.
   
   Solution 9: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 10:   [DSSEG-3244]
               When printing logs, an invalid printf() format indicated
               that a hash calculation was skipped due to the file size
               being over the maximum hash calculation size.
   
  Solution 10: This issue is fixed in this release. The printf() format
               has been updated.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 11:   [DSSEG-2642/SEG-31883]
               An invalid dentry object sometimes caused a kernel panic.
   
  Solution 11: The issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 12:   [DSSEG-2569/SEG-27689]
               On Linux, Application Control included all files
               marked as executable in the inventory, even if it did not
               recognize the extension as an executable. This would
               result in a very large inventory database.
   
  Solution 12: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Unix 版 Deep Security Agent

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(s):
   
   Issue 1:    [DSSEG-3695/1939658/SEG-49191]
               The "Send Policy" action failed because of a
               GetDockerVersion error in Deep Security Agent.
   
   Solution 1: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 2:    [DSSEG-3652/SF01919585/SEG-48728]
               Deep Security Agent sent invalid JSON objects in response
               to Deep Security Manager, which caused errors in Deep
               Security Manager's log file.
   
   Solution 2: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 3:    [DSSEG-3587/SF01804378/SEG-47425]
               Deep Security Agent did not add Python extension module
               (PYD) files to the inventory of Application Control.
   
   Solution 3: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 4:    [DSSEG-3552/SF01607298/SEG-43341]
               When the Application Control driver failed to load (for
               example, if the driver was corrupted during a Deep
               Security Agent upgrade), the agent sent system events to
               Deep Security Manager repeatedly as it tried to reload
               the driver. The large number of generated events consumed
               database storage and made the System Events extremely
               slow to load.
   
   Solution 4: This issue is fixed in this release. The Application
               Control driver loading exception is now tracked and the
               Application Control server is stopped after 5 failed
               attempts to load the driver.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 5:    [DSSEG-3515/SEG-45832]
               Deep Security Agent process potentially crashed when
               the detailed logging of SSL message was enabled and
               outputed.
   
   Solution 5: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 6:    [DSSEG-3246/SF01358696/SEG-38712]
               The tbimdsa engine sometimes caused a system crash.
   
   Solution 6: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 7:    [DSSEG-2569/SEG-27689]
               On Linux, Application Control included all files
               marked as executable in the inventory, even if it did not
               recognize the extension as an executable. This would
               result in a very large inventory database.
   
   Solution 7: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Windows 版 Deep Security Agent/Windows 版 Deep Security Notifier

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(s):
   
   Issue 1:    [DSSEG-3695/1939658/SEG-49191]
               The "Send Policy" action failed because of a
               GetDockerVersion error in Deep Security Agent.
   
   Solution 1: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 2:    [DSSEG-3652/SF01919585/SEG-48728]
               Deep Security Agent sent invalid JSON objects in response
               to Deep Security Manager, which caused errors in Deep
               Security Manager's log file.
   
   Solution 2: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 3:    [DSSEG-3587/SF01804378/SEG-47425]
               Deep Security Agent did not add Python extension module
               (PYD) files to the inventory of Application Control.
   
   Solution 3: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 4:    [DSSEG-3552/SF01607298/SEG-43341]
               When the Application Control driver failed to load (for
               example, if the driver was corrupted during a Deep
               Security Agent upgrade), the agent sent system events to
               Deep Security Manager repeatedly as it tried to reload
               the driver. The large number of generated events consumed
               database storage and made the System Events extremely
               slow to load.
   
   Solution 4: This issue is fixed in this release. The Application
               Control driver loading exception is now tracked and the
               Application Control server is stopped after 5 failed
               attempts to load the driver.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 5:    [DSSEG-3515/SEG-45832]
               Deep Security Agent process potentially crashed when
               the detailed logging of SSL message was enabled and
               outputed.
   
   Solution 5: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 6:    [DSSEG-3514/SF01716752/SEG-45507]
               Deep Security's Notifier.exe process caused high CPU
               usage.
   
   Solution 6: The issue is fixed in this release
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 7:    [DSSEG-3381/1609675/SEG-43574]
               The "Smart Protection Server Disconnected for Smart Scan"
               alert did not automatically clear after the connection
               had been restored.
   
   Solution 7: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 8:    [DSSEG-3246/SF01358696/SEG-38712]
               The tbimdsa engine sometimes caused a system crash.
   
   Solution 8: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Issue 9:    [DSSEG-2569/SEG-27689]
               On Linux, Application Control included all files
               marked as executable in the inventory, even if it did not
               recognize the extension as an executable. This would
               result in a very large inventory database.
   
   Solution 9: This issue is fixed in this release.
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~