Adversarial offers three kinds of integrations. Incident and Risk integrations pull data in: records flow from the source tool into Adversarial, and all syncing is asynchronous. Ticketing integrations create and link records in the external tool from Adversarial, and notification integrations deliver messages from Adversarial to your team’s channels.
The Adversarial integration configuration supports automatic syncing from the source, AI scoring upon ingestion, and automatic AI rescoring on description changes for integration-sourced records. Platform administrators have the necessary permissions to enable sync and AI scoring at the tool level (Wiz, HackerOne, Bugcrowd, GreyMatter, etc.). Integrations sync every 15 minutes for new and updated records, with a full re-sync of all records once nightly. Ticketing integrations are not on this schedule — Jira issues are imported on demand.
| Integration |
Description |
| CrowdStrike |
Import alerts from CrowdStrike Falcon (NGSiem, CWPP, EPP) as Incident records |
| GreyMatter |
Sync GreyMatter incidents to the Incident Register |
| Integration |
Description |
| Wiz |
Sync Wiz cloud configuration issues to the Risk Register |
| HackerOne |
Import HackerOne bug bounty reports as Risk records |
| Bugcrowd |
Import Bugcrowd bug bounty submissions as Risk records |
| watchTowr |
Sync watchTowr attack surface findings to the Risk Register |
| GitHub Dependabot |
Import GitHub Dependabot alerts across your organization as Risk records |
| Integration |
Description |
| Jira |
Create and link Jira tickets from risks and incidents for remediation tracking; import Jira issues via JQL search |
| Linear |
Create and link Linear issues from risks and incidents for remediation tracking |
| ServiceNow |
Create and link ServiceNow records from risks and incidents for remediation tracking |
| Integration |
Description |
| Slack |
Deliver org-level notifications to a Slack channel |
| Teams |
Deliver org-level notifications to a Microsoft Teams channel |