Introducing the Huntress detection module: escalations and incident reports in your queue

By ContraForce · Published

Announcement · November 20, 2026 · 5 min read

Huntress escalations and incident reports now open as ContraForce incidents, in the same queue as the rest of your customers. Security Delivery Agents investigate the escalations, and closing a report in ContraForce resolves it in Huntress.

Your SOC works Microsoft Defender XDR and Microsoft Sentinel incidents in ContraForce. Plenty of your customers also run Huntress, and Huntress's output lands in the Huntress portal: incident reports from the Huntress SOC, and escalations that wait for someone on your side to make a call. Covering those customers means another console on the shift checklist, and an escalation can sit there until somebody happens to look.

With the Huntress detection module, each of that customer's incident reports and escalations opens as a ContraForce incident, in the same queue as the rest of your customers. Huntress keeps doing its detection and its SOC work. Your team sees the results next to everything else it's working.

What lands in the queue

ContraForce checks the customer's Huntress organization about every two minutes. Each incident report and each escalation becomes its own incident under that customer, labeled with its type, because the two ask different things of your team:

Work the incident report without leaving ContraForce

Open an incident report and your analyst gets the report text formatted for reading, with the hosts, processes, files and registry entries it names listed as evidence. When a report includes simulated evidence, ContraForce labels it, so nobody mistakes a test for the real thing. The report's comments are there too, and your analyst can add their own.

So is the remediation plan. Workspace Owners and Incident Responders can review the plan Huntress proposes, approve it and mark manual tasks complete from the ContraForce incident. Host containment shows separately from the report's status, so your analyst can see whether the host is still contained no matter where the report stands.

Closing a report resolves it in Huntress

Close an incident report in ContraForce and it's resolved in Huntress. If someone resolves it in Huntress first, ContraForce closes the incident for you. When a report is waiting on its remediation plan, approve the plan first; Huntress won't close the report until you do.

Escalations work the other way round. An escalation is Huntress waiting on your decision, and Huntress takes that decision in its own portal, so your analyst answers it there. When Huntress marks the escalation resolved, ContraForce closes the incident.

One record for every customer

Owner, status changes and the audit trail live on the ContraForce incident, in the same place as your Defender XDR and Sentinel work, so your record of a customer doesn't stop at the edge of the Huntress portal.

Security Delivery Agents take the escalations

Escalations are the part of Huntress that waits on your team, so they're the part the agent picks up. If a Security Delivery Agent runs on the customer's workspace, it investigates each new escalation from the same queue and records its findings on the ContraForce incident. Your analyst starts from the agent's write-up, not from a blank page, before answering Huntress.

Incident reports don't start an agent run on their own. The Huntress SOC has already investigated and confirmed them, and a second verdict would add nothing and could contradict Huntress's analysts. They still reach the queue, notifications and real-time updates like any other incident.

The agent answers to the per-workspace controls you already use for your Defender XDR and Sentinel customers: which severities it picks up on its own (On Queue), investigation policies and agent shifts. Huntress's critical and high severities come in as High, low as Low, and the rest as Medium. When you first connect, the agent only gets escalations from the last 24 hours, so connecting a customer doesn't hand it a backlog.

Connecting the customer's Huntress organization

Setup starts in Huntress, under your account menu, then API Credentials. Create the credential as a user with an account-level role, such as Admin or Security Engineer, because organization-level roles can't see escalations. To close incident reports from ContraForce, use a user-based key whose user has write permissions; a read-only account key lets ContraForce read but not resolve.

A Workspace Owner then enters the key and secret on Huntress in the workspace's Security Modules page. The connection test lists the Huntress organizations the credential can see, and you choose the one this workspace covers. One account-level credential can serve every customer you manage in Huntress, with each workspace reading only its own organization. The module also shows which Huntress products that organization uses, from Managed EDR and Managed ITDR to Managed SIEM and Security Awareness Training, and whether the key can resolve incidents.

Where to start

Start with the customer whose escalations wait longest today. That's where an unanswered question from Huntress is most likely to be sitting.

Set the agent controls on that workspace and start the agent on Manual. Then connect Huntress, wait for the next escalation and open the incident. The agent's findings should be on it, next to the details Huntress sent. Once you've reviewed the agent's first investigations, move severities to On Queue.

The Huntress module is in the ContraForce release notes for 12 and 18 November 2026.

Covering customers on Rapid7 InsightIDR too? Their investigations land in the same queue with the Rapid7 detection module.

Questions about connecting Huntress to ContraForce? Contact us at support@contraforce.com.

Sources

  1. ContraForce Docs, Release Notes (Huntress module, 2026-11-12; Huntress investigation tools, 2026-11-18) · verified November 20, 2026
  2. ContraForce Docs, Configuring Security Delivery Agents · verified November 20, 2026
  3. ContraForce Docs, Workspace Policies · verified November 20, 2026
  4. ContraForce Docs, Agent Shifts · verified November 20, 2026

More posts

Keep reading

Announcement

Introducing the Rapid7 detection module: InsightIDR investigations become incidents

Rapid7 InsightIDR investigations now open as ContraForce incidents, in the same queue as the rest of your customers. Closing one writes the status, disposition and your comment back to Rapid7.

Announcement

Your Security Delivery Agent can now review detection rules

Start an agent rule review from a Microsoft Sentinel scheduled or NRT analytics rule, or from a Defender XDR custom detection. Your Security Delivery Agent reads the rule's recent incidents and recommends whether and how to change it, with the detection coverage risk and a validation plan for your team to weigh.

See it run on your own incidents.

Connect one supported workspace, validate access and your Gamebook workflow, then measure an eligible investigation in your own environment.

Start for free Read the docs

Connect one workspace: scoped Entra ID application consent, no endpoint agents, no log forwarding.