Integrations

Everything connects from inside the app. Open Integrations in the sidebar, choose a service and enter its details. There is nothing to install and no command line to configure. Integrations are available on Hacker and above, except where noted.

Connect your tools

GitHub: Issues and repository access
Jira: Security tickets
Slack: Real-time alerts
Microsoft Teams: Channel notifications
Discord: Alerts to channels
Burp Suite: Enterprise scans and findings
AWS: Cloud scanning
Azure: Cloud scanning
Google Cloud: Cloud scanning

Development and ticketing

GitHub

Sync vulnerabilities with GitHub issues and track remediation. You will need:

Field	Notes
Personal access token	Needs repository and issues permissions.
Organization	Optional.
Default repository	In `owner/repo` form.

To scan private repositories and browse them in the New Scan wizard, install the Cyrion AI GitHub App from the same page.

Jira

Create and manage security tickets straight from findings.

Field	Notes
Jira domain	For example `yourcompany.atlassian.net`.
Email	The account that owns the token.
API token	Created in your Atlassian account.
Default project key	For example `SEC`.

Once connected, choose Send to Jira on any finding. The issue key and link are stored on the finding.

Alerts and collaboration

Service	What you need
Slack	An incoming webhook URL. Optionally a default channel such as `#security-alerts` and a bot token for interactive features.
Microsoft Teams	An incoming webhook URL from a Teams channel connector. Tenant and app details are optional.
Discord	A channel webhook URL. A bot token and server ID are optional.

Security tooling

Burp Suite Enterprise

Drive Burp Suite Enterprise scans and pull its findings into Cyrion AI. Provide your Burp Enterprise URL and an API key created under Settings → API in Burp Enterprise.

Cloud accounts

Connect AWS, Azure or Google Cloud so cloud scans can authenticate. See Cloud Security for the credentials each provider needs and the roles to grant.

MCP servers

Extend agents with extra intelligence sources. Add them from the MCP catalogue with a click.

Server	Gives agents
Vulnerability Intelligence	NVD, EPSS, CISA KEV, OSV and GitHub Advisory data.
MITRE ATT&CK	Techniques, tactics, groups and mitigations.
Certificate Transparency	Subdomains from the public CT logs.
Wayback Machine	Historical URLs from the Internet Archive.
GreyNoise	Targeted traffic versus internet background noise.
Shodan	External attack surface without touching the target.
VirusTotal	Reputation and passive DNS lookups.
urlscan.io	Sandboxed page analysis using private submissions.
Agent Memory	A knowledge graph agents build and read across a scan.

Secrets Vault

Store credentials once and reuse them across scans: application logins, API keys, cloud credentials and source-control tokens. Scans reference a stored credential by ID, so secrets never appear in scan settings, and you can rotate one in a single place. Available on Hacker and above.

Webhooks

Send scan events to your own systems by adding a webhook URL under Integrations.

{
  "webhook_url": "https://your-server.com/cyrion-webhook"
}

API keys and CI/CD

Create API keys under API Keys to call the REST API from scripts and pipelines. A typical CI step launches a scan against a staging environment, waits for it to finish, then fails the build if new critical or high findings appear.

curl -X POST "https://app.cyrion.ai/api/scans" \
  -H "Authorization: Bearer $CYRION_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "https://staging.example.com",
    "target_type": "web_application",
    "scan_mode": "quick",
    "run_name": "pr-1234-quick-scan"
  }'

Then read the results with GET /api/scans/{run_name}/vulnerabilities. Every endpoint is documented in the API Reference.

Info: API requests are rate limited per plan: 120 per minute on Hacker, 300 on Red Team and 1,000 on Enterprise.

Enterprise

Enterprise adds SIEM integrations and custom integrations built with your team.