Security approvals
/security. Needs module.security and the ThreatLocker
connector.
Application approval requests from ThreatLocker, shown alongside the rest of the desk.
What you can do
Section titled “What you can do”| Action | Notes |
|---|---|
| See pending requests | With their details |
| Approve or deny | Sent back to ThreatLocker |
| Follow its ticket | Each request is mirrored to its own ticket automatically, and that ticket is closed when the request is decided |
| See per-device history | Previous approvals and decisions on that machine |
The linked ticket keeps the reason an application was approved next to who asked and who decided.
Working a request
Section titled “Working a request”Open the request, see what is being asked for and on which machine, check the device history for whether this has come up before, and decide. A machine generating a request a week says something about how it is being used.
If ThreatLocker is not connected
Section titled “If ThreatLocker is not connected”The page links you to Connectors to set it up. See the ThreatLocker connector.
Demo mode gives you sample requests to approve and deny, so the team can practise before real requests arrive.
The page needs module.security.
| Permission | Allows |
|---|---|
device.view | See requests and per-device history |
device.manage | Approve or deny a request, here or on its ticket |
Auditing
Section titled “Auditing”Every approval and denial is written to the audit log, in addition to ThreatLocker’s own record.