Download Deep Security Manager
Lucrecio Poinson
On the Master Key screen, configure a master key. This key will be used to encrypt the passwords in the manager's database, dsm.properties file, and configuration.properties file. Choose one of the following options:
When you run the Deep Security Manager installer, it searches its local directory for a full ZIP package of the agent installer. (Relays are agents whose relay feature is enabled.) If the ZIP is not found, then the manager's installer will try to download it from the Trend Micro Download Center on the Internet.
Updated Deep Security Manager to allow the removal of Integrity Monitoring baseline data using a console (dsm_c) command. Removing baseline data does not affect the protection you receive from Integrity Monitoring, but does remove the following:
- The option to "View Baseline" data from the manager consoleThe ability to use the "Trusted Common Baseline" as a source of Auto-TaggingThe ability to generate an "Integrity Monitoring Baseline Report"
Re-parent agents: Deep Security Manager now supports moving agents to Trend Micro Cloud One Workload Security using the new "MoveAgent" API command. This command automates the process of re-parenting an activated Deep Security Agent from its current on-premise manager to a Workload Security tenant. If re-parenting is unsuccessful, the agent will re-activate with its on-premise manager, retaining its previous configuration.
Due to feature differences between the Deep Security and Workload Security managers, move tasks may be refused to prevent unexpected behaviors. Customers should disable the following features before moving agents:
To better align with AWS best practices and improve AWS account security, we have made a change to the process of adding a new AWS account into Deep Security using cross-account roles. Previously, when using a cross-account role for authentication, Deep Security required two pieces of information: a role ARN, and an external ID trusted by the role. This has now changed to a new process where Deep Security provides the external ID, and requires that the role provided has included this external ID in its IAM trust policy. This change provides stronger security in shared Deep Security environments, and ensures that strong external IDs are always used. For details on the new process of adding cross-account roles using manager-generated external ID, see Add an AWS account using a cross-account role.