Affected customers will see the specific error presented through the Deep Security Manager user interface when a manual import is triggered, or via system events for automated processes.
An attempt to install a new deployment of Deep Security Manager will fail with the error certificate timestamp expired during the installation process.
In a multi-tenant Deep Security Manager deployment, creation of new tenants will fail with a signature validation failure.
For Existing Deep Security Deployments
Any existing updates that have previously been imported to Deep Security Manager can continue to be used.
To address issues with the import of new Deep Security components, Trend Micro has released the following updates:
- April 26, 2020: Linux Kernel support updates released to ensure kernel support updates can be applied successfully after this date.
- April 26, 2020: Deep Security Rule Update to ensure rule updates can be applied successfully after this date.
- April 29, 2020: Deep Security Agent updates to ensure the import of Deep Security Agents will complete successfully after this date.
To address tenant creation failures in a multi-tenant deployment, administrators can use Deep Security Rule Update 20-020 (April 26, 2020) or later to create a tenant template and then use that template to successfully create new tenants. Alternatively, administrators can upgrade the Deep Security Manager to any version released after April 27, 2020.
For New Deep Security Manager Installations
Trend Micro will provide a new release of Deep Security Manager for all actively supported Long-Term Support (LTS) releases as wall as a Deep Security Feature Release (FR) 12 update during the week of April 27, 2020. Please use this new release of Deep Security Manager for all new Deep Security Security Software deployments to address this issue.