Onboarding

Install security tools with install keys

Install Huntress, SentinelOne, ThreatLocker, CrowdStrike, Sophos, Bitdefender, Defender for Endpoint or Todyl from one blueprint, with each client's own key sealed to each device.

Your security tools tie each device to the right client with a key, a token or an installer link that's different for every client. In Enlist those are install keys. You set them once on the client, and a blueprint step names only which keys it needs. When the step runs, Enlist seals that device's own value to that device, so one blueprint works for every client and no key is ever in a blueprint.

Add a security tool to a blueprint #

  1. In the blueprint, add a Run a script step and pick Start from the script library.

  2. Choose the tool's Install script, for example Install Huntress. Its install keys appear under Install keys in the step, already filled in.

  3. Publish the blueprint as usual.

Set a client's keys #

  1. Open Clients, pick the client and scroll to Install keys.

  2. Under Which key, pick the key, for example Huntress organization key. Where to find it in the tool shows below the form.

  3. Under Used by, pick All clients, All of the client, or one site.

  4. Paste the key into Paste the key, pick Save key and confirm with your passkey.

A key for one site replaces the client's for that site, and the client's replaces one set for all clients. Keys that are the same for every client, such as your Huntress account key, start at All clients. Enlist never shows a key again, only its last four characters, and leaves keys out of data exports. Only owners and admins can see, set or remove install keys, and every change is in the activity log without the value.

What each tool needs #

ToolWindowsMacInstall keys
HuntressYesYesAccount key (all clients), organization key (each client)
SentinelOneYesYesSite token (each client or site), installer link (all clients)
ThreatLockerYesYesInstall key of the client's computer group
CrowdStrike FalconYesYesCustomer ID (each client), installer link (all clients)
Sophos EndpointYesYesThe client's installer link from Sophos Central
Bitdefender GravityZoneYesNot yetThe client's package installation link
Defender for EndpointYesYesA link to the tenant's onboarding package
Todyl SGN ConnectYesNot yetThe deployment key of the client's Todyl policy

SentinelOne, CrowdStrike and Defender for Endpoint have no public download. Put the installer or package where your devices can fetch it over HTTPS (your own file storage) and save its link as the install key. Links are kept secret just like keys, so a link with an access token in it is fine.

How Enlist checks what it installs #

  • On Windows the installer must carry a valid Authenticode signature. Steps for hosted installers also take an optional SHA-256 that the file must match.
  • On a Mac the package or app must be signed with the vendor's Apple Team ID and pass Gatekeeper.
  • Every download uses HTTPS, into a folder only the system can write. Links and keys never appear in the step's output or on a command line other accounts can read on the Mac.
  • If the tool already runs, the step says so and changes nothing, so you can run it again safely.

Macs need approval for security tools #

macOS lets a security tool's system extension, network filter and Full Disk Access run only once an MDM profile or a person approves them. Push the vendor's MDM profile before the step runs and nobody has to approve anything. Otherwise the step installs the tool and reports NEEDS APPROVAL, and someone allows it in System Settings > Privacy & Security.

When a key changes or is missing #

  • Replace a key: steps already on their way with the old one stop (install_key_changed). Resume those devices and they get the new one.
  • Remove a key: steps on their way stop, and later ones use a key set for all clients, if there is one.
  • No key for this device: the step fails before anything is sent (no_install_key) and names the key to add. Add it and resume the device.
  • Old agent: the step fails with agent_too_old until the agent updates.

Last updated 2026-11-15. Something wrong or missing? Email [email protected].