ContraForce Integration with Microsoft Defender XDR
How incidents, evidence, approvals, and response actions move through the delivery loop.
Reviewed by ContraForce team
The ContraForce integration with Microsoft Defender XDR turns Defender incidents into governed security-delivery work. Defender remains the detection and response control. ContraForce applies the provider's Gamebook, gathers supported evidence, records a verdict, routes approvals, executes permitted actions, and synchronizes the service record.
Integration boundary
| System | Responsibility |
|---|---|
| Microsoft Defender XDR | Detection, incident correlation, security evidence, and supported response controls |
| ContraForce | Investigation procedure, action governance, multi-tenant delivery, evidence record, ticketing, reporting, and tuning workflow |
| Human operator | Policy ownership, approval of consequential actions, exception handling, and customer accountability |
Delivery flow
- Defender XDR creates or updates an incident.
- ContraForce receives the eligible incident through the configured tenant connection.
- A Security Delivery Agent follows the assigned Gamebook and queries approved evidence.
- The agent records observations and reaches an auditable verdict.
- Low-risk actions may run automatically; controlled actions stop for approval.
- The final outcome and evidence synchronize to the configured service workflow.
Multitenant access
Microsoft's multitenant management model respects permissions granted by each managed tenant. Providers should grant only the roles and actions required for the agreed service. See Microsoft Defender multitenant management requirements.
Controls to validate
- Tenant connection and delegated relationship
- Read permissions for incidents, alerts, identities, devices, and relevant evidence
- Write permissions for incident state and comments
- Separate permission for containment or remediation actions
- Customer-specific approval gates
- Ticket board, priority, and closure mapping
- Failure behavior when an API, credential, or evidence source is unavailable
Proof-of-value test
Use an approved benign incident or simulation. Verify that the incident is acquired, the correct Gamebook runs, evidence remains tenant-scoped, the response authority is enforced, the ticket receives the expected record, and every action is attributable.
Related pages
- Microsoft Defender XDR for MSPs
- Automated incident response for Microsoft Defender XDR
- Defender portal multitenant management
Continue the evaluation
Sources and review method
Product capabilities were reviewed against the page-specific primary sources below on 2026-11-05. Performance claims require the population and limitations stated in the linked methodology.
- Microsoft Defender multitenant management requirements (verified 2026-11-05)
- ContraForce platform (verified 2026-11-05)
- NIST SP 800-61 Revision 3: Incident Response Recommendations and Considerations (verified 2026-11-05)
Related guides on Microsoft security operations
- Zero-Data-Custody AI Security Operations, An architecture guide to federated security automation without central log duplication.
- ContraForce Integration with Microsoft Sentinel, How Sentinel incidents and customer workspaces connect to governed service delivery.
- Browse all integrations
- See how the ContraForce platform works
Ready to Transform Your Security Operations?
See how ContraForce runs the full delivery loop for service providers. Connect a supported tenant and validate the workflow in your own environment.
No credit card. Connect one workspace: scoped Entra ID application consent, no endpoint agents, no log forwarding.