Lifecycle Manager + ThreatLocker

Ishita Snehil
Ishita Snehil
  • Updated

Bring ThreatLocker client and device data into Lifecycle Manager to keep asset records current and support security-aware lifecycle planning.

ThreatLocker data flows into Lifecycle Manager in one direction: ThreatLocker to Lifecycle Manager. The integration is read-only.

Who can use this feature?

  • A Lifecycle Manager account with permission to manage integrations or Manage Sync permissions.

What you'll need:

  • ThreatLocker administrator or API-user access.

Generate a ThreatLocker Auth Key

ThreatLocker API documentation

  1. Sign in to the ThreatLocker portal with an account that can manage API users and organizations.
  2. Open the API or API user settings.
  3. Create or select an API user for Lifecycle Manager.
  4. Grant access to the organizations and computer data that Lifecycle Manager should read.
  5. Generate an Auth Key.
  6. Copy the Auth Key and store it securely.
Important: Use the raw Auth Key only. Do not add Bearer, quotation marks, or extra spaces.

Connect ThreatLocker to Lifecycle Manager

  1. 1. Log into the ScalePad Hub and click Integrations
  2. Click + Add Integration
  3. Search and Select ThreatLocker.
  4. Enter the ThreatLocker Auth Key.
  5. Enter the Managed Organization ID.
  6. Select Save and sync now.
  7. Confirm that the integration status changes to Connected or Syncing.

If the connection fails, generate a new Auth Key, confirm that the API user can access the required organizations and assets, and enter the raw key again.

Fields we are syncing data for

ThreatLocker data is synced into Lifecycle Manager as client and device records.

ThreatLocker field Lifecycle Manager field
organizationId Client identifier
Display name Client name
computerId Asset identifier
Hostname or computer name Asset name
organizationId Client association
threatLockerVersion Agent version
lastCheckin Last check-in
dateAdded Date added or first seen
isTamperProtectionDisabled Tamper protection status
isIsolated or isIsolationMode Isolation status

How syncing works

Lifecycle Manager retrieves accessible ThreatLocker organizations and their computers.

Troubleshooting

Symptom Likely cause Resolution
The integration rejects the credentials The Auth Key is invalid, expired, or formatted incorrectly Generate a new Auth Key and enter the raw value without Bearer or extra spaces
The connection succeeds but no devices appear The API user cannot access the selected organizations Confirm organization access and the Managed Organization ID
Some organizations are missing Child-organization access or routing is incomplete Confirm that the API user can read the required child organizations
The integration remains queued or syncing The initial vendor sync is still running or the vendor request failed Wait for the sync to complete, then review the integration status and retry
ThreatLocker blocks the ScalePad agent A ThreatLocker policy is blocking the ScalePad service Allow the required ScalePad agent activity in ThreatLocker
Any questions? Reach out to our Lifecycle Manager support team by submitting a support ticket.
:sparkles: NEW :sparkles: Join our MSP Power-Ups - Free 15-minute micro-workshops + live Q&A with our Lifecycle Manager experts. Sign up here to reserve your spot.

Was this article helpful?

Yes! No