Trend Micro Deep Security 11.0 Update 3 公開のお知らせ：サポート情報 : トレンドマイクロ
（情報元のブックマーク数 
Trend Micro Deep Security 11.0 Update 3リリース、
Deep Security 11.0 Update 3 のモジュールを公開いたします。
■ 公開開始日2018 年 10 月 24 日 (水)
■ 対象モジュール
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 11.0 Update 3
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancement(s) are included in this release:
Enhancement 1: [DSSEG-2684]
With this release, customers can add an NSX Manager
when Deep Security Manager is operating in FIPS mode.
When adding an the NSX Manager to Deep Security
Manager, after you enter the NSX Manager information
and click "Next", Deep Security Manager gets the NSX
server certificate. After adding the vCenter and NSX
server successfully, you can install the Deep Security
Virtual Appliance and enable FIPS mode for the
appliance.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 2: [DSSEG-2901]
In this release, a time zone improvement has been
added to the Deep Security Manager logging.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 3: [DSSEG-2724]
The version of the Java JRE used in Deep Security
Manager has been upgraded to Java 8 u181.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issue(s):
Issue 1: [DSSEG-2929/SEG-36736/01211295/GCC1-1-828168859]
The 'Cancel "Upgrade Agent"' button on the 'Actions'
tab of the Computer details page did not function
properly.
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-2892/SEG-37280/SF01255727]
Deep Security Manager does not successfully
synchronize with Microsoft Azure cloud accounts when
Deep Security Manager is using a proxy in an air-gap
environment.
Solution 2: With this release, Deep Security Manager is able to
synchronize when the proxy setting does not contain a
credential. However, the Azure connector cannot
synchronize successfully with a credential in the
proxy setting.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-2855]
"User Session Validation Failed" events occurred
unexpectedly when the Deep Security Manager sign-in
page was accessed.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 4: [DSSEG-2849/SEG-34129]
The status of the Deep Security Virtual Appliance
displayed as "Managed (VM Stopped)" instead of
"Offline" when the Deep Security Virtual Appliance was
power off.
Solution 4: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 5: [DSSEG-2848]
After migrating a virtual machine from one ESX host to
another, a duplicate entry for that virtual machine
was displayed on the Computers page in Deep Security
Manager.
Solution 5: The issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 6: [DSSEG-2791/SEG-13784]
Customers were prevented from upgrading Deep Security
Manager when their environment contained Deep Security
Agents on unsupported platforms.
Solution 6: The Deep Security Manager installer no longer performs
a pre-check of agents and relays, which unblocks the
Deep Security Manager upgrade.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 7: [DSSEG-2701]
The Deep Security Manager did not display system event
934 - Software Update: Anti-Malware Windows Platform
Update Successful.
Solution 7: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 8: [DSSEG-2691]
On Linux, Deep Security Manager files were readable by
all local users.
Solution 8: The permissions of Deep Security Manager files on
Linux have been changed so that they are no longer
accessible by local users.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 9: [DSSEG-2812]
Beginning with JDK version 8u181, the JVM enforces
endpoint identification for LDAPS connections by
default. The JVM verifies the server address of an
Active Directory connector against the server
certificate Common Name (or subjectAltName, if it
exists). As a result, if the existing Active Directory
connector uses a server address that does not match
the certificate CN (or subjectAltName), the connector
would not be able to synchronize successfully.
Solution 9: This issue is fixed in this release. When performing a
fresh install, endpoint identification is enabled.
When performing an upgrade, if any tenants have an
existing Active Directory connector (for either a
computer or a user) that connects using LDAPS, endpoint
identification is disabled. If no Active Directory
connector is found, endpoint identification is enabled
by default.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deep Security Agent 11.0 Update 3 for Linux
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancement(s) are included in this release:
Enhancement 1: [DSSEG-2828/SEG-34684]
Previously, the network engine would sometimes fill
the MAC field in event logs with zeros for outgoing
packets, to make the logs easier to read. This release
removes this behavior to avoid issues in an overlay
network environment. In the event logs, the MAC
address for outgoing packets may be empty or contain a
random number.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 2: [DSSEG-2745/00389528/441559/00513686/00611107/
00528775/SF00340345/00425845/538145/SF00374619/
SF179909/SF159145/SF318628/00368352]
In this release, the Deep Security Agent installer
checks the installation platform to prevent
installation of an agent that does not match the
platform. This feature is supported on:
- Amazon Linux and Amazon Linux 2
- Red Hat Enterprise Linux 6 and 7
- CentOS 6 and 7
- Cloud Linux 7
- Oracle Lnux 6 and 7
- SUSE Linux Enterprise Server 11 and 12
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 3: [DSSEG-2606]
The version of OpenSSL used by the Deep Security Agent
and Deep Security Relay has been updated
to openssl-1.0.2o.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issue(s):
Issue 1: [DSSEG-2875/SEG-28060/00853021]
After upgrading Deep Security Agent from version 9.6
to 10.0 on a Linux platform, the Component Set version
was not updated, which caused the Security Update
Status to display "Out-of-Date".
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-2835/SEG-33414/00854640]
The Deep Security Agent's CPU usage spiked every 10
seconds.
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-2739]
When Deep Security Agent was installed on a virtual
machine (VM) and the VM was reverted to an earlier
state, Log Inspection event data was not synchronized
properly between the Deep Security Agent and Deep
Security Manager.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deep Security Agent 11.0 Update 3 for Windows, and Deep Security Notifier 11.0 Update 3 for Windows
2. What's New
========================================================================
2.1 Enhancements
=====================================================================
The following enhancement(s) are included in this release:
Enhancement 1: [DSSEG-2769]
The Deep Security Agent installer no longer installs
all feature modules when the module plug-in files are
located in the same folder as the installer. The
required plug-in files are downloaded from a Relay
when a policy is applied to a protected computer.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 2: [DSSEG-2258]
The Anti-Malware engine offline error is no longer
reported when the computer is preparing to shutdown.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enhancement 3: [DSSEG-2606]
The version of OpenSSL used by the Deep Security Agent
and Deep Security Relay has been updated
to openssl-1.0.2o.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.2 Resolved Known Issues
=====================================================================
This release resolves the following issue(s):
Issue 1: [DSSEG-2875/SEG-28060/00853021]
After upgrading Deep Security Agent from version 9.6
to 10.0 on a Linux platform, the Component Set version
was not updated, which caused the Security Update
Status to display "Out-of-Date".
Solution 1: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 2: [DSSEG-2835/SEG-33414/00854640]
The Deep Security Agent's CPU usage spiked every 10
seconds.
Solution 2: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue 3: [DSSEG-2739]
When Deep Security Agent was installed on a virtual
machine (VM) and the VM was reverted to an earlier
state, Log Inspection event data was not synchronized
properly between the Deep Security Agent and Deep
Security Manager.
Solution 3: This issue is fixed in this release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Trend Micro 情報漏えい対策オプション 最新モジュール (ビルド1.0.1034) 公開のお知らせ：サポート情報 : トレンドマイクロ
（情報元のブックマーク数 
Trend Micro 情報漏えい対策オプション 最新モジュール (ビルド1.0.1034) リリース、オプションライセンス更新に失敗する問題対応って・・・・
Trend Micro 情報漏えい対策オプションにて、ライセンス更新に関連する修正を含む最新モジュールを下記日程にて公開いたします。
■公開開始日
2018年10月10日 (水)
■新機能・修正内容
ウイルスバスター コーポレートエディション管理コンソールの[プラグイン]画面にて、Trend Micro 情報漏えい対策オプションのライセンス更新に失敗する問題を修正いたしました。
■入手方法
2018年10月10日 (水)以降、以下モジュールが弊社Active Update サーバから配信されます。
Trend Micro 情報漏えい対策オプション (ビルド 1.0.1034)配信されたモジュールは、ウイルスバスター コーポレートエディション管理コンソールの[プラグイン]画面にて、それぞれの製品のセクションに表示されている[ダウンロード]ボタンをクリックする事により適用されます。
サポート情報 : トレンドマイクロ
ご注意：マシンの再起動は必要ありません。
【やじうまPC Watch】セキュリティチップ搭載のMac、部品交換が困難に 〜自己診断プログラムのパスには特殊ソフトが必要 - PC Watch
（情報元のブックマーク数 
（セキュリティホール memo経由）
メモ
米メディアMacRumorsは4日(現地時間)、Apple独自のセキュリティチップ「T2」を搭載するiMac Proおよび2018年モデルのMacBook Proについて、同チップによる部品紐づけのために自家修理が困難であると報じた。
【やじうまPC Watch】セキュリティチップ搭載のMac、部品交換が困難に 〜自己診断プログラムのパスには特殊ソフトが必要 - PC Watch
これは入手したAppleの内部文書に基づいたもので、正規サービスプロバイダ以外での修理(DIYなど)の場合、部品の交換後に自己診断プログラム(Apple diagonostics)でエラーが発生するとのこと。エラーを解消するためには、認証を受けたサービスプロバイダに提供される「Apple Service Toolkit」とよばれるソフトを用いて修理を完了する必要がある。
Apple、iOSとWindows向けiCloudの脆弱性を修正 - ITmedia エンタープライズ
（情報元のブックマーク数 
iCloudアップデート、iOS12.0.1もリリースとのこと
米Appleは10月8日、iPhoneやiPad向けのiOS更新版「iOS 12.0.1」と、Windows向けのiCloud更新版「iCloud for Windows 7.7」を公開した。それぞれ複数の脆弱性を修正している。
Apple、iOSとWindows向けiCloudの脆弱性を修正 - ITmedia エンタープライズ
Appleのセキュリティ情報によると、iOS 12.0.1では「VoiceOver」と「Quick Look」の脆弱性を修正した。悪用された場合、ロックがかけられた端末でローカルの攻撃者に写真や連絡先を見られたり、共有機能を不正に利用されたりする恐れがあった。
コンシューマー向け「Google+」打ち切りへ APIの不具合で50万人の個人データ露呈 - ITmedia エンタープライズ
（情報元のブックマーク数 
Google+が漏洩問題と使用率の状況からサービス終了方向とのこと。2019年8月に終了か・・・
ユーザーが非公開に設定した情報にまでアプリがアクセスできてしまう不具合が発覚。利用が極めて低調だったということもあり、コンシューマーバージョンについては、2019年8月末にサービスを終了する。 [鈴木聖子，ITmedia]
コンシューマー向け「Google+」打ち切りへ APIの不具合で50万人の個人データ露呈 - ITmedia エンタープライズ
米Googleは10月8日、ソーシャルネットワーキングサービス「Google+」のコンシューマー向けバージョンを閉鎖すると発表した。APIの不具合が原因でユーザーが非公開に設定した情報にアプリがアクセスできる状態になっていたことや、利用が極めて低調だったことを理由として挙げている。
農業IoTサービスのリスク対策に「Trend Micro IoT Security」を採用（セラク、トレンドマイクロ） | ScanNetSecurity[国内最大級のサイバーセキュリティ専門ポータルサイト]
（情報元のブックマーク数 
農業IoTサービスにトレンドマイクロIoTソリューションを採用らしい
株式会社セラクとトレンドマイクロ株式会社は10月4日、農業IoTの分野で提携し、セラクが提供する農業IoTサービス「みどりクラウド」のセキュリティ対策として、トレンドマイクロのIoT機器向けセキュリティソリューション「Trend Micro IoT Security（TMIS）」を実装、よりセキュアな農業IoTサービスの提供を実現すると発表した。
農業IoTサービスのリスク対策に「Trend Micro IoT Security」を採用（セラク、トレンドマイクロ） | ScanNetSecurity[国内最大級のサイバーセキュリティ専門ポータルサイト]
「みどりクラウド」は、農業にIoT技術を融合した圃場環境モニタリングサービス。温度センサやカメラなど圃場のセンサデータを可視化する、圃場の「センサデータモニタリングサービス」を提供している。11月15日からは、複数のセンサから収集したデータをAIにより分析し、ボイラーなどの環境制御機器を連動、圃場環境を最適にする「環境制御サービス」を、オプションとして提供開始する。
