Strengthening Agent Onboarding in Endpoint DLP Plus

Strengthening Agent Onboarding in Endpoint DLP Plus


Agent installation in ManageEngine Endpoint DLP Plus is getting an upgrade. Agent Installation Protection is an enhancement to agent onboarding that ensures every agent installation is authorized before the computer joins your managed environment.

We're sharing this early so you know what to expect and can plan at your own pace. This post covers what the feature does, how it fits with your current setup, and what changes for existing users.


Why Agent Onboarding Needs Stronger Protection

The Endpoint DLP Plus agent is a trusted component on every managed computer. Once it registers with your server, it monitors and enforces data loss prevention policies across supported channels, helping organizations prevent unauthorized transfers of sensitive information.

These operations include monitoring and restricting file transfers to removable storage devices, controlling web uploads and email transfers, enforcing printing restrictions, and managing other data movement activities. The agent performs these operations with system-level privileges, while your server treats the registered computer as part of your managed environment.


This trust is what makes the agent installer a sensitive file. Installers are routinely copied to shared drives, attached to emails, or handed to partners, and a copy can easily travel beyond the people it was meant for. If anyone holding an installer can register a computer, an unauthorized device could appear as a trusted endpoint, receive your DLP policies and establish a communication channel with the Central server.

An unauthorized endpoint joining your environment could undermine your data protection strategy. Controlling who can complete an agent installation is therefore as important as controlling who can access the console.


How Agent Onboarding Is Secured Today

Computers for Approval, released in build 11.3.2414.01 (April 2024), adds an administrator approval step on your Central server. New agents are held in an approval list and cannot perform critical operations until an administrator approves them. A rejected computer never becomes part of your managed environment.


This gives administrators visibility into every new endpoint and the final say over which computers join the network.

However, this review happens only after the agent is installed and has already contacted your server. And because approval is a manual step, a computer can occasionally be approved by mistake through simple human error.


What's New: Agent Installation Protection

Agent Installation Protection introduces install-time authentication. During agent installation, the installer must be verified using a one-time password (OTP) or deployment token issued by the Central server. The computer is not onboarded until verification succeeds, and an invalid or expired credential prevents the installation from proceeding.


  1. Manual Installation: For a manual installation on a single computer, the Central server generates a time-bound, 6-digit one-time password (OTP). The administrator performing the installation enters this OTP, and the agent installs only if the OTP is valid.
  2. Bulk Agent Installation: Installations using the downloaded agent installer, whether through GPO, SCCM, MDT, or in Azure and AWS environments, require a time-bound deployment token generated from the Central server. Silent deployments continue to work without end-user intervention.


How Agent Installation Protection Strengthens Your Security

  1. Verification happens before onboarding, not after. Computers for Approval reviews a computer after its agent is installed and has contacted the server. Agent Installation Protection verifies authorization during installation, before the computer joins your managed environment.
  2. A copied installer is no longer enough. Agent installation now requires an OTP or deployment token issued by the Central server. This prevents someone with only a copy of the installer from independently onboarding an unauthorized computer.
  3. OTPs and tokens are time-bound. Each OTP and deployment token expires after a set period, limiting the window in which an exposed credential could be misused.


For Existing Users: Once this release is available, you will need to transition to OTP- or token-based agent installation. We will keep the existing installation flow working for a short period to give you time to switch. Computers for Approval will continue to work as before.

After this transition period, the new installation flow will be enforced. We recommend downloading the updated agent installer and updating your existing deployment workflows ahead of time. Agents that are already installed will not be affected.


Release Availability: Stay tuned! More details are on the way. We will announce the release in a dedicated forum post and include the relevant information in the release notes.