Trend Micro Deep Security 11.0 Update 5 公開のお知らせ：サポート情報 : トレンドマイクロ
Deep Security 11.0 Update 5 のモジュールを公開いたします。
■ 公開開始日2018 年 12 月 25 日 (火)
■ 対象モジュール
Deep Security Manager
■ 追加機能/修正内容追加機能や修正内容は付属の Readme をご覧ください。
※日本語のReadmeは一か月以内を目安に公開いたします。■ 入手方法
Deep Securityヘルプセンターからダウンロードできます。
サポート情報 : トレンドマイクロ
「Deep Securityヘルプセンター」
また、以下の製品 Q&A も合わせてご参照ください。
Deep Security Manager
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancements are included in this release:
Enhancement 1: [DSSEG-3217]
The HostUsageReport now includes a TenantID column.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 2: [DSSEG-2993/SEG-28030/SF00852527]
In a multi-tenant Deep Security Manager environment,
alert emails now include the Tenant Name and Tenant
ID.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 3: [DSSEG-2990]
When generating a diagnostics package in Deep Security
Manager running on Windows, if you select the "System
Information" option, the diagnostics package will now
include the manager's msinfo file.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 4: [DSSEG-2901]
In this release, a time zone improvement has been
added to the Deep Security Manager logging.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 5: [DSSEG-2792/SEG-35196]
A new 'Include time zone in events' check box has been
added to the SIEM and syslog configuration in Deep
Security Manager under Administration > System
Settings > Event Forwarding > Edit > General tab.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 6: [DSSEG-2784]
The versions of Apache Tomcat used in Deep Security
Manager have been upgraded to 8.5.34.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issues:
Issue 1: [DSSEG-3145/SEG-34447]
The Log Inspection severity clipping feature did not
work as expected when forwarding events.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-3143/SEG-41156/01484581]
Deep Security Manager sometimes failed to apply a rule
update right after deleting some computers.
Solution 2: The issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-3140/1468357/SEG-40727]
Deep Security Manager sometimes used high levels of
CPU when when a very large number of superseded
baseline entities were being deleted.
Solution 3: This release optimized the performance of superseded
baseline entities.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DSSEG-2983]
Deep Security Manager was not able to synchronize with
Azure accounts using the Azure connector in an air-
gapped environment. This was because the Azure
connector used the ADAL4j library to retrieve the
access token. This implementation has a limitation in
handling a proxy with username/password
authentication, which caused timeout exceptions in
air-gaped environments.
Solution 4: Deep Security Manager now uses the Azure REST API to
retrieve the access token. This new implementation
works with an authenticated proxy in air-gaped
environments.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 5: [DSSEG-2899]
The Inactive Agent Cleanup feature sometimes did not
work because the upgrade process inserted null values
when migrating data from the hosts table to the
hostvolatiles table.
Solution 5: The issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
