Introducing the Rapid7 detection module: InsightIDR investigations become incidents
By ContraForce · Published
Announcement · November 20, 2026 · 5 min read
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.
Your SOC works Microsoft Defender XDR and Microsoft Sentinel incidents in ContraForce. A customer whose SIEM is Rapid7 InsightIDR is harder to cover, because their investigations open in InsightIDR, outside the queue your analysts work. Covering that customer can mean a Rapid7 login on the shift checklist and closing each investigation there by hand.
With the Rapid7 detection module, each of that customer's InsightIDR investigations opens as a ContraForce incident, in the same queue as the rest of your customers. Detection carries on in InsightIDR, on the rules the customer runs today, and what your team decides goes back to Rapid7.
What lands in the queue
ContraForce checks the customer's InsightIDR about every two minutes for new and changed investigations. Each investigation becomes its own incident under that customer, with its severity taken from the investigation's priority, and tagged by who is responsible for it:
- SIEM: an investigation the customer's side works in InsightIDR, which is the work you've taken on.
- MDR: an investigation the Rapid7 MDR SOC is responsible for, when the customer also buys Rapid7 MDR.
Your analyst opens the incident and sees the investigation's title, priority, status and disposition, when its latest alert fired, and who it's assigned to in Rapid7.
Your decision is written back to Rapid7
Triage in ContraForce and the investigation in Rapid7 keeps up. Move the incident to In Progress and the investigation shows Investigating. Close it with a classification and Rapid7 records the matching disposition, and your closing comment is added to the investigation, so the customer's team sees the outcome and the reasoning in their own console.
| You close the incident as | Rapid7 records the disposition |
|---|---|
| True positive | Malicious |
| Benign positive | Benign |
| False positive | Not applicable |
| Undetermined | None; it stays Undecided |
It works in the other direction too. If someone on the customer's team closes the investigation in Rapid7, ContraForce picks up the closure and closes the incident.
Both sides keep the record
The status, disposition and closing comment land in Rapid7. Owner and the full audit trail stay on the ContraForce incident, alongside your Defender XDR and Sentinel work.
MDR investigations stay with Rapid7's analysts
Some customers buy Rapid7 MDR on top of InsightIDR. Their MDR investigations still show in your queue, tagged MDR, so you can see everything open for that customer in one place. They're Rapid7's to work, though: ContraForce leaves their status to the Rapid7 MDR SOC and updates when Rapid7 does, and the agent doesn't run on them.
Security Delivery Agents work the SIEM investigations
If a Security Delivery Agent runs on the customer's workspace, it picks up the SIEM investigations from the same queue, runs its investigation and records its findings on the ContraForce incident for your analyst to read. It 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.
Decide up front whether the agent should close incidents on this workspace. When the agent closes one, the disposition and comment go back to Rapid7, just as they do when an analyst closes it, so anyone on the customer's team who checks that investigation will see the agent's outcome.
Connecting the customer's InsightIDR
Setup starts in the Rapid7 Command Platform, under Administration, then API Key Management. An organization key works, or a user key whose user can manage investigations; a read-only key lets ContraForce read investigations but not update them. If you're a Rapid7 partner with a multi-tenant key, the same key can serve every customer you manage there, with each workspace pointed at its customer's Organization ID.
A Workspace Owner then enters the region the customer's Rapid7 data lives in, the key and, for a multi-tenant key, the Organization ID, on Rapid7 SIEM in the workspace's Security Modules page. The connection test has to pass before you can save. It confirms the key reaches that customer's investigations and tells you whether the customer has Rapid7 MDR.
Where to start
Start with the customer whose InsightIDR investigations your team closes by hand in Rapid7 today, since that's where the double handling is. When you first connect, ContraForce looks back 24 hours, so the queue starts with today's investigations rather than the customer's whole history.
Set the agent controls on that workspace and start the agent on Manual. Then connect, wait for the next investigation and close it from ContraForce. In Rapid7, the investigation should show Closed, with the disposition and your comment. Once you've reviewed the agent's first investigations, move severities to On Queue.
The Rapid7 module is in the ContraForce release notes for 18 November 2026.
Covering customers on Huntress too? Their escalations and incident reports land in the same queue with the Huntress detection module.
Questions about connecting Rapid7 to ContraForce? Contact us at support@contraforce.com.
Sources
- ContraForce Docs, Release Notes (Rapid7 module, 2026-11-18) · verified November 20, 2026
- ContraForce Docs, Configuring Security Delivery Agents · verified November 20, 2026
- ContraForce Docs, Workspace Policies · verified November 20, 2026
- ContraForce Docs, Agent Shifts · verified November 20, 2026
Keep reading
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.
Guide
How to govern AI agents in incident response
An AI agent that can isolate a device or reset a password needs controls that still hold when it's wrong. See how ContraForce's gates stack before a Gamebook™ workflow runs, and how to review, audit, and widen what agents may do.
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.
Connect one workspace: scoped Entra ID application consent, no endpoint agents, no log forwarding.