Archived Workload Security release notes

Starting December 10 2020, customers subscribed to the Trend Micro Cloud One listing on AWS will see usage for Workload Security consolidated to 4 billing dimensions, instead of the previous 8. There is no change in price to your services and no change to how your usage is calculated and charged.

Usage prior to this change will still be charged on the previous dimensions, so you may see a combination of the previous and updated dimensions in this month's bill.

You can now add your VMWare vCenter accounts to Workload Security. Adding a vCenter account to Workload Security allows Workload Security to retrieve your virtual machine inventory from the vCenter server. This provides visibility to all workloads from vCenter as well as automated management of the lifecycle of these workloads (which is consistent with adding accounts from AWS, Azure, or Google Cloud Accounts to Workload Security).

For customers that are familiar with Workload Security, the addition of this support provides a consistent experience with the features and functionality that you are already familiar with.

Adding a vCenter account to Workload Security requires a new component called the data center gateway. For more information, see setup a data center gateway.

For more information about which DNS names to allow, see Port numbers, URLs, and IP addresses

Usage prior to this change will still appear as "host / hour" so you may see a combination of "host / hour" and "units" in this month's line items.

The new Deep Security 20 Agent has been released to the download center and will be available in all Workload Security accounts by August 4th.

If you have a firewall or AWS security group that restricts which IP addresses are allowed outbound from your network, you must add the new IP addresses.

Re-ordered the protection modules into the following categories:

Malware Prevention:

• Anti-Malware
• Web Reputation

System Security:

• Application Control
• Integrity Monitoring
• Log Inspection

Network Security:

• Firewall
• Intrusion Prevention

If you are using metered billing and looking for a way to break out costs by individual cloud accounts, we have made the Security Module Usage Report (Event & Reports > Generate Reports) available. This report contains a detailed breakout of consumption hours by cloud account. This data can be used to breakout the single Workload Security line item on your marketplace bill supporting chargeback to your teams.

In a heartbeat, if the number of agent events is very high, they will be split under more than one "Events Retrieved" system event.

This feature is being gradually rolled out. For more information, see What does preview mean?

Aggregated identical agent events in a single heartbeat under a single event.

Scheduled tasks have been enhanced:

• On the last screen of the New Scheduled Task Wizard, 'Task enabled' has been renamed to 'Enable task'.
• The 'Synchronize cloud account' task now indicates that it only supports vCloud and Azure accounts.
• The Scheduled Tasks page now includes details for any 'Scan Computers for Malware' or 'Scan Computers for Integrity Changes' tasks that you have configured.

Agent version control gives you and your security operations team control over the specific versions of the Deep Security Agent that can be used by features like deployment scripts and upgrade on activation. This provides increased control over the Deep Security Agent used in your environment. For more information, see Configure agent version control.

Using a local key secret containing the "$" symbol stopped the upgrade or fresh install of Deep Security Manager.

Deep Security as a Service stopped displaying the alert "Agent/Appliance Upgrade Recommended (New Version Available)", even though the agent had not been upgraded.