Trend Micro Deep Security 10.0 Update 17 公開のお知らせ：サポート情報 : トレンドマイクロ
Deep Security 10.0 Update 17 のモジュールを公開いたしました。
■ 公開開始日2019 年 2 月 4 日 (月)
■ 対象モジュール
Deep Security Manager
Linux 版 Deep Security Agent
Unix 版 Deep Security Agent
Windows 版 Deep Security Agent
Windows 版 Deep Security Notifier
■ 追加機能/修正内容追加機能や修正内容は付属の Readme をご覧ください。
※日本語のReadmeは一か月以内を目安に公開いたします。■ 入手方法
Deep Securityヘルプセンターからダウンロードできます。
サポート情報 : トレンドマイクロ
「Deep Securityヘルプセンター」
また、以下の製品 Q&A も合わせてご参照ください。
Update プログラムとは
Deep Security Manager
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancements are included in this release:
Enhancement 1: [DSSEG-3189]
Oracle JRE 8u181 has been replaced with Azul Zulu
OpenJDK 8u192.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 2: [DSSEG-3161]
When a protected ESXi is upgraded to a newer version
or a new ESXi version is deployed, Deep Security
Manager automatically detects the ESXi version and
adds it to the Trend Micro Deep Security service in NSX
Manager, which helps to ensure the successful
deployment of the related version of dsva.ovf.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issues:
Issue 1: [DSSEG-3331/01458561/SEG-41188]
When several ESXi hosts were managed by different
vCenters, Deep Security Manager sometimes displayed
incorrect Deep Security Virtual Appliance information.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-3179]
Sometimes, when a large number of vMotion jobs did not
finish normally (such as when the Deep Security
Manager service was shut down) new vMotion jobs could
not be processed. Other Deep Security Manager jobs
were affected as well.
Solution 2: The issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-2363/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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 issues:
Issue 1: [DSSEG-3386/SEG-40130]
Deep Security Scanner encountered problems when an SAP
client program created a large number of scan tasks.
Solution 1: Scanner has been improved and can now handle a larger
number of scan tasks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-3336]
The Network Filter Driver lacked error handling for
some cases when memory allocation failed. This
sometimes resulted in a system crash, especially when
the system memory was exhausted.
Solution 2: This issue has been resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-3309]
Deep Security Agent real-time Anti-Malware scans and
Application Control didn't work correctly with a Linux
4.18 kernel.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DSSEG-3262]
Deep Security Agent real-time Anti-Malware scans
didn't work correctly with a Linux 4.12 kernel.
Solution 4: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 5: [DSSEG-3216]
When both Anti-Malware real-time scans and SAP scanner
were enabled on a Windows computer that had SAP
NetWeaver 7.5+ installed, a virus could be detected
and quarantined, but the error code returned to SAP
NetWeaver was not correct.
Solution 5: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 6: [DSSEG-3109]
A native firewall could not be turned on/off
automatically after the Deep Security Firewall module
was enabled or its configuration was changed.
Solution 6: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 7: [DSSEG-3103]
In certain configurations, the Deep Security Agent
kernel driver loaded an incorrect configuration,
causing an OS crash.
Solution 7: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 8: [DSSEG-3081/SF01339187/SEG-38497/SEG-33163]
An SAP system with Java running in a Linux environment
failed to start when Deep Security Scanner returned an
error code without an error message.
Solution 8: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 9: [DSSEG-3039/SEG-39670]
An Integrity Monitoring rule could be triggered
unintentionally when the prefix of its base directory
path matched that of another rule. For example, if you
had rules that monitored "c:\lab\" and "c:\lab1\", and
added a file "c:\lab1\sample.txt", both rules would be
triggered.
Solution 9: 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 issues:
Issue 1: [DSSEG-3336]
The Network Filter Driver lacked error handling for
some cases when memory allocation failed. This
sometimes resulted in a system crash, especially when
the system memory was exhausted.
Solution 1: This issue has been resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-3178/SEG-32973/01021938]
Deep Security Agent on Solaris had a memory leak when
writing the debug log.
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-3109]
A native firewall could not be turned on/off
automatically after the Deep Security Firewall module
was enabled or its configuration was changed.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DSSEG-3039/SEG-39670]
An Integrity Monitoring rule could be triggered
unintentionally when the prefix of its base directory
path matched that of another rule. For example, if you
had rules that monitored "c:\lab\" and "c:\lab1\", and
added a file "c:\lab1\sample.txt", both rules would be
triggered.
Solution 4: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 5: [DSSEG-2898/01190643/SEG-35814]
Solaris InfiniBand interfaces are not supported in any
version of Deep Security Agent. If such interfaces are
present, Deep Security Manager displays a 'Get
Interface Failed' status for the relevant computer(s),
and also generates many unwanted firewall events from
these interfaces.
Solution 5: Deep Security Agent ignores all the traffic on
InifiniBand interfaces, and also these interfaces do
not appear in Deep Security Manager > agent's Computer
details > Interfaces page.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Windows 版 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 issues:
Issue 1: [DSSEG-3336]
The Network Filter Driver lacked error handling for
some cases when memory allocation failed. This
sometimes resulted in a system crash, especially when
the system memory was exhausted.
Solution 1: This issue has been resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-3333]
Due to a side effect from a previous fix, the Network
Filter Driver would pass packets through a broadband
wireless interface.
Solution 2: This issue has been resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-3245/SEG-38712/SF01358696]
The tbimdsa engine sometimes caused a system crash.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DSSEG-3216]
When both Anti-Malware real-time scans and SAP scanner
were enabled on a Windows computer that had SAP
NetWeaver 7.5+ installed, a virus could be detected
and quarantined, but the error code returned to SAP
NetWeaver was not correct.
Solution 4: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 5: [DSSEG-3109]
A native firewall could not be turned on/off
automatically after the Deep Security Firewall module
was enabled or its configuration was changed.
Solution 5: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 6: [DSSEG-3039/SEG-39670]
An Integrity Monitoring rule could be triggered
unintentionally when the prefix of its base directory
path matched that of another rule. For example, if you
had rules that monitored "c:\lab\" and "c:\lab1\", and
added a file "c:\lab1\sample.txt", both rules would be
triggered.
Solution 6: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 7: [DSSEG-2608/SEG-32198]
When upgrading Deep Security Agent, the operating
system would sometimes reboot automatically.
Solution 7: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 issues:
Issue 1: [DSSEG-3336]
The Network Filter Driver lacked error handling for
some cases when memory allocation failed. This
sometimes resulted in a system crash, especially when
the system memory was exhausted.
Solution 1: This issue has been resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-3333]
Due to a side effect from a previous fix, the Network
Filter Driver would pass packets through a broadband
wireless interface.
Solution 2: This issue has been resolved in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-3245/SEG-38712/SF01358696]
The tbimdsa engine sometimes caused a system crash.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DSSEG-3216]
When both Anti-Malware real-time scans and SAP scanner
were enabled on a Windows computer that had SAP
NetWeaver 7.5+ installed, a virus could be detected
and quarantined, but the error code returned to SAP
NetWeaver was not correct.
Solution 4: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 5: [DSSEG-3109]
A native firewall could not be turned on/off
automatically after the Deep Security Firewall module
was enabled or its configuration was changed.
Solution 5: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 6: [DSSEG-3039/SEG-39670]
An Integrity Monitoring rule could be triggered
unintentionally when the prefix of its base directory
path matched that of another rule. For example, if you
had rules that monitored "c:\lab\" and "c:\lab1\", and
added a file "c:\lab1\sample.txt", both rules would be
triggered.
Solution 6: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 7: [DSSEG-2608/SEG-32198]
When upgrading Deep Security Agent, the operating
system would sometimes reboot automatically.
Solution 7: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Trend Micro Deep Security on AWS (AWS Quick Start) (English Edition)
- 作者: AWS Whitepapers,Amazon Web Services
- 出版社/メーカー: Amazon Web Services
- 発売日: 2016/10/26
- メディア: Kindle版
- この商品を含むブログを見る
