Automatically enabled when you configure Huntress permissions in your agent workflow. No manual toggle needed.
What It Does
- Pull the incident report behind a Huntress ticket — findings, indicators, severity, affected host
- Approve or reject the report’s remediations, then resolve the incident or escalation
- Look up any deployed host, edit its tags and tamper protection, isolate it or release it, or uninstall its Huntress agent (offboarding, or before a reinstall)
- Investigate signals, managed identities and their MFA/risk state, exposed ports, and SIEM logs
- Create time-boxed travel/geolocation exceptions that expire on their own, plus VPN and IP rules
- Enumerate, create, rename, or remove customer organizations
- Read who has portal access, invite users, change permission levels, revoke access
- Read summary reports for QBRs and invoices for billing reconciliation
Permission Groups
Each group has an access level: Disabled, Read Only, or Read/Write. Detections and Reporting & Billing only ever offer Read Only — Huntress has no write endpoint for them.
Access Profiles
Read Only
Read Only
All groups Read Only. The agent can investigate any alert, host, identity, or report but never changes anything.
Helpdesk
Helpdesk
Incidents at Read/Write, with technician approval on every write. Everything else Read Only — enough to work an alert to resolution without touching hosts, access rules, organizations, or users.
IT Admin
IT Admin
Every writable group at Read/Write. Host isolation, remediation approval, incident and escalation resolution, and organization changes run autonomously. Unwanted access rule changes and portal user changes require technician approval: a travel, VPN, or IP exception quietly widens what Huntress allows, and a new portal member widens who can sign in to Huntress. Uninstalling an agent, turning tamper protection off, and removing an organization or account also wait on a technician, as under every profile.
Full Automation
Full Automation
Every write runs autonomously, host isolation, remediation approval, and portal access changes included. Uninstalling an agent, turning tamper protection off, and removing an organization or account still wait on a technician.
Safety Controls
Host isolation is asynchronous. A successful call returns the host as “Pending Isolation”, not isolated — the agent is instructed not to report a host as contained until Huntress confirms it.
How to Configure
1
Connect Huntress
Save your Huntress API key pair in the Neo Dashboard under the Endpoint Security integrations category. See Connecting Huntress to Neo.
2
Configure permissions
On the agent’s Tools & Settings tab, click Endpoint Security and expand the Huntress block. Pick one of its Presets, which are the access profiles above, or set each permission group yourself.
3
Set approval requirements
Decide which groups’ writes require technician approval. Approving a remediation executes assisted remediations on the endpoint immediately, so keep approval on Incidents until you trust the agent’s judgment.
