Skip to main content
Connect your Huntress account and the agent works the tickets Huntress opens in your PSA, without a technician opening the Huntress portal. When Huntress opens a ticket for an unexpected login, a noncompliant Microsoft 365 setting or a confirmed incident, the agent finds the escalation or incident report behind it, reads what Huntress saw, and writes it up in an internal note. It then proposes the next step: mark the login expected or unauthorized, approve the SOC’s remediation plan, or isolate or release a host. Nothing changes in Huntress until a technician approves the plan.

Prerequisites

  • A Huntress account with your customers set up as organizations.
  • A Huntress user for the key to act as. The key carries that user’s role:
    • Admin, if the agent may make approved changes (resolve escalations, approve remediations, isolate hosts).
    • Read-only, if the agent should only read.

How to connect

1

Create a user API key

Sign in to Huntress as an Admin. Open the menu at the top right and choose API Credentials. Under User API Credentials, click Add, pick the Huntress user the key acts as, and name the key (for example, Rallied).
2

Copy the key and secret

Copy the API Key and the API Secret Key right away. Huntress shows the secret only once.
3

Connect Huntress

In Rallied, go to Settings → Integrations, find the Huntress card and click Connect. Paste the API Key and API Secret Key and click Connect. The card shows Connected when it’s ready.
Use a user API key. Rallied rejects the older account API key, because Huntress has deprecated it: it is read-only and does not return all data. If you lost the secret, create a new key in Huntress and reconnect.

Mapping organizations to clients

When you connect, Rallied syncs the organizations in your Huntress account. Review how each organization maps to a Rallied client on the Companies tab of the integration’s detail page. Click Sync organizations to pick up customers you’ve added since. On a client’s ticket, the agent reads and changes only that client’s organization. It fills in the organization ID automatically. A record that belongs to another customer, or to several customers at once, is answered as not found. In the MSP admin Chat, the agent can also list across every organization and read account-level data: all organizations, everyone with access to your Huntress account, invoices, and Managed SIEM log searches. End users can’t run any Huntress tool.

How the agent uses it

Huntress records the PSA ticket ID on what it opened, so the agent finds the record from the ticket itself. Unexpected login (ITDR). For a ticket like “Unexpected Country” or “Unexpected VPN”, the agent:
  1. Finds the escalation and reads the user, country, VPN or IP, and time.
  2. Reads the user’s identity in Huntress (MFA, risk level) and any access rules already set for the customer.
  3. Writes an internal note with what it found and proposes one resolution for approval:
    • Expected, for that user or for the whole customer. It can expire on a date, for example after a trip.
    • Unauthorized, for that user. It can also sign the user out and disable the account, only when the evidence points to a compromise.
Incident report (EDR or identity). The agent summarizes the SOC’s findings and remediation plan in an internal note. Then it proposes, in one plan:
  • approving the plan, which starts the steps Huntress runs itself, or rejecting it with a comment that goes back to the Huntress SOC;
  • the manual steps for a technician, and marking each one done;
  • releasing the host or identity once it is clean.
When the whole plan is approved, Huntress closes the incident report on its own and undoes its containment: an isolated host is released and a disabled identity is enabled again. Agent down. For an RMM alert that the Huntress agent stopped on a computer, the agent looks the computer up in Huntress and reports whether it is still checking in, has stopped reporting, or is not enrolled in the customer’s organization. Microsoft 365 settings (ISPM) and platform health. These are fixed in the customer’s tenant or devices, not in Huntress. The agent says which setting or devices are affected and what the recommended state is. It proposes resolving the escalation only after the fix is in place.

What to know

  • Isolating a host cuts it off the network until it is released. The agent proposes it only when the SOC or the evidence calls for it.
  • Comments on an incident report are visible to everyone who can see the report in Huntress, which can include the customer’s own Huntress users. Comments do not reach the SOC. Only rejecting the remediation plan does.
  • Changes that reach every customer are only available in the admin chat. That covers creating a new organization, resolving an escalation for the whole account, and access rules for the whole account. On a client’s ticket, a plan with one of these steps is refused before anyone approves it.
  • Invitations to a customer’s organization don’t show in Huntress’ API until the person accepts. Until then, the agent can’t change or remove that person’s access.
  • Permission errors that name a Huntress role mean the key’s user lacks that permission. Give the user a role with it, or leave the change to someone who has it.

Tools

Reads default to Auto. Every change defaults to Approval needed. To change a default, open the Policies tab on Settings → Integrations → Huntress. See Approval settings.

Reads

Changes

Deleting an organization and uninstalling an agent can’t be undone from Rallied.

See also