Trend Micro Deep Security 12.0 Update 1 公開のお知らせ：サポート情報 : トレンドマイクロ＠ Tomcat8.5.43にアップデートだったり、累積修正対応

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

otifier
■ 追加機能/修正内容

追加機能や修正内容は付属の Readme をご覧ください。
※日本語のReadmeは一か月以内を目安に公開いたします。

■ 入手方法

Deep Securityヘルプセンターからダウンロードできます。

DeepSecurityヘルプセンター
また、以下の製品 Q&A も合わせてご参照ください。
Update プログラムとは

サポート情報 : トレンドマイクロ

Deep Security Manager - 12.0 update 1

Resolved issues

• New groups added to an AWS connector were not inheriting the existing permissions assigned to that connector. (SF01112604/SEG-35024/DSSEG-4205)
• When a policy was created based on a relay-enabled agent, the policy contained the relay state. All agents that were assigned the policy automatically became relays. (DSSEG-3550)
• Application Control events did not include a "Size" column. (DSSEG-4256)
• In the Deep Security Manager, the entry for the Release Notes column is replaced from readme.txt to Release Notes. (DSSEG-4331)
• In Deep Security Manager, some AWS EC2 hosts were left without matching cloud instance records when many hosts needed to be removed during an AWS cloud connector synchronization. (DSSEG-4317)
• When Deep Security Manager was connected to both a case-sensitive Microsoft SQL database and VMware NSX, the Deep Security Manager upgrade readiness check would sometimes fail and block the upgrade. (SF02060051/DSSEG-4268/SEG-52044)
• The latest kernel update for some Linux operating systems, including RHEL7 and Amazon Linux, made a change that causes failures during agent initiated communication heartbeats. (DSSEG-4315)
• In Deep Security Manager, under Policies > Intrusion Prevention Rules > Application Types > (select DNS client) > Properties > General the Port setting would change to "Any" after any updates to the port list. (DSSEG-4370/SEG-55634)
• Deep Security Manager logged a 'Disable all features' log at the INFO level with no indication of which features had been disabled. (DS-33927)

Security Updates
Security updates are included in this release. For more information about how we protect against vulnerabilities, visit https://success.trendmicro.com/vulnerability-response. (SF02112629/SEG-53014/DSSEG-4097)

• Upgraded Tomcat to 8.5.43. (DSSEG-4335)

Deep Security Manager - 12.0 update 1 | Deep Security

Deep Security Agent - 12.0 update 1

New features

• Linux
  • Debian Linux 10 is supported in this release. (DSSEG-4262)

Resolved issue

• Linux
  • Red Hat Enterprise Linux 8 changed the default behavior of DHCP, which impacts Deep Security Agent's ability to detect whether it's running on an Azure VM instance. Therefore, the agent does not carry enough information in HostInfo to Deep Security Manager and fails to re-home to an Azure connector. (DSSEG-4085)
  • The advanced network engine option "Maximum data size to store when packet data is captured" did not work. (DSSEG-4113/SEG-48011)
  • Deep Security Agent real-time Anti-Malware scans and Application Control didn't work on kernel version 5.0.0-15-generic. (DSSEG-4228)
  • Deep Security Agent failed to install on Ubuntu 18.04. (SF01593513/SEG-43300/DSSEG-4119)
  • When using Ubuntu with Netplan network interface, Deep Security Anti-Malware and the network filter driver would not start correctly. (DSSEG-4306)
  • In some cases Integrity Monitoring Events dose not include Entity Name. (SF00889757/DSSEG-3761/SEG-31021)
  • The agent operating system would sometimes crash when Firewall interface ignores were set. (DSSEG-4377)
• Unix
  • Network events were sometimes lost in certain conditions. (DSSEG-4159)
  • In some cases Integrity Monitoring Events dose not include Entity Name. (SF00889757/DSSEG-3761/SEG-31021)
• Windows
  • The advanced network engine option "Maximum data size to store when packet data is captured" did not work. (DSSEG-4113/SEG-48011)
  • In some cases Integrity Monitoring Events dose not include Entity Name. (SF00889757/DSSEG-3761/SEG-31021)
  • An incorrect reboot request event sometimes occurred. (DSSEG-3722)

Deep Security Agent - 12.0 update 1 | Deep Security

働きアリからの脱出 個人で始める働き方改革