Transitioning from Deep Security as a Service

Trend Cloud One - Endpoint & Workload Security was formerly known as Trend Micro Deep Security as a Service. The transition to Trend Cloud One is seamless to existing customers for all functionality relating to protection of your workloads. There is no action required on your part to ensure protection remains in place during the transition. Visually, you start to see changes in the web console and product documentation as this transition from Deep Security as a Service to Workload Security takes place.

The changes:

• Beginning March 30 2020, if you create a new account or request a password reset from Deep Security as a Service, you receive a link that directs you to the Trend Cloud One management console. However, Trend Micro continues to provide access to Deep Security as a Service at https://app.deepsecurity.trendmicro.com.
• Beginning May 1 2020, the sender email address for Deep Security as a Service changes from deepsecurityasaservice@trendmicro.com to no-reply-cloudone@trendmicro.com. If you use spam filters or email routing rules, update them to include this new email address.
• When you access the legacy Deep Security as a Service console (https://app.deepsecurity.trendmicro.com), you are redirected to the Trend Cloud One console. You can log in with the same credentials and navigate to the Workload Security tile to continue using the service. Your account is now a Trend Cloud One account. Bookmark the Workload Security console page and use that URL to log in to the service moving forward.

If you are currently using SAML single sign-on, support for SAML is not part of the initial Trend Cloud One launch. You can continue to access Deep Security as a Service using SAML without changes, through the existing Deep Security as a Service URL. Support for SAML will be rolled out after the initial launch.