Skip to content
plugboard.appRequest a demo

Connectors

ThreatLocker

Zero-trust endpoint allowlisting. Application approval requests surface in Plugboard so the ICT team actions them in one place, with a ticket attached.

CategorySecurity
AuthenticationAPI key
ReachesYour ThreatLocker portal API
Needs an agentNo
Demo modeYes

security.listComputers, security.getComputer, security.listRequests, security.resolveRequest, security.deviceHistory

Which lights up the security page, gated by the module.security module.

  1. Sign in to the ThreatLocker portal as an administrator.
  2. Find the API section under your organisation’s settings and generate an API key.
  3. Note your organisation id, which identifies your tenant within ThreatLocker.
  4. Note the portal API URL for your region.

ThreatLocker’s portal layout changes between versions. If you cannot find the API section, your ThreatLocker partner or account manager can point at it, and in some plans has to enable it first.

Settings, Connectors, ThreatLocker, Configure.

FieldDefaultValue
baseUrlemptyThe ThreatLocker portal API URL
organizationIdemptyYour organisation, or tenant, id
demoModefalseReturn fixture data
FieldValue
apiKeyThe API key

Save and test.

An approval request is a service desk request. Handling it in the queue fixes the two things that go wrong with allowlisting in a school.

It gets actioned. Approval requests that live only in a security console get looked at when somebody remembers. In the queue alongside everything else, they get worked.

It gets a reason. Attaching the request to a ticket means the record of why an application was approved sits next to who asked and who decided. Six months later, when somebody asks why a piece of software is allowed, there is an answer that is not “somebody clicked approve”.

ActionNotes
See pending approval requestsWith their details
Approve or denySent back to ThreatLocker
Follow its ticketEach request is mirrored to its own ticket automatically
See per-device historyPrevious approvals and decisions on that machine

Demo mode gives you sample requests to approve, deny and ticket, so the team knows the flow before real requests start arriving.

SymptomCause
Sample requests appeardemoMode is still on
401 on testWrong API key
403The key lacks the scope, or API access is not enabled on your plan
Empty request listThere are none, or the organisation id is wrong
Approvals do not take effectThe key is read-only. Resolving a request needs write access
Page says ThreatLocker is not connectedThe connector is not enabled, or module.security is off