Jira Integration
BreachSpider can create Jira issues directly from findings, enabling your team to manage vulnerability remediation in their existing Jira workflow. Available on Professional tier and above.
Setting Up the Connection
- Navigate to Integrations > Connections > Add Connection.
- Select Jira as the connection type.
- Fill in the connection details:
Jira Instance URL (required): Your Jira Cloud or Server URL. Examples: https://yourcompany.atlassian.net (Cloud) or https://jira.internal.yourcompany.com (Server).
Authentication: BreachSpider supports two authentication methods:
- API Token (Jira Cloud): Generate an API token at id.atlassian.com/manage-profile/security/api-tokens. Enter your Atlassian email and the generated token.
- Personal Access Token (Jira Server/Data Center): Generate a PAT in your Jira profile settings. Enter the token only.
Default Project Key (required): The Jira project key where issues will be created. Example: OT-SEC, VULN, WPA. You can override this per auto-ticket rule.
Default Issue Type (required): The issue type for created tickets. Common choices: Bug, Task, Story, or a custom type like "Vulnerability". Must match an issue type that exists in the target project.
- Click Test Connection to verify BreachSpider can authenticate and create issues.
- Click Save.
How Issues Are Created
When a ticket is created with Jira as the destination (manually or via auto-rule), BreachSpider creates a Jira issue with:
Summary (title): The ticket title. Example: "CVE-2025-32433 - Patch Erlang/OTP SSH - CVSS 10.0"
Description: A formatted description including:
- CVE ID, BSID, and severity
- Affected asset name and environment
- BCS, CVSS, and EPSS scores
- KEV status and exploit maturity
- SAGE summary (ICS context and remediation guidance)
- Patch status and patch URL (if available)
- Direct link to the CVE in BreachSpider
Priority: Mapped from BCS score:
| BCS Range | Jira Priority |
|---|---|
| 9.0 - 10.0 | Highest |
| 7.0 - 8.9 | High |
| 4.0 - 6.9 | Medium |
| 0.1 - 3.9 | Low |
Assignee: Set to the assignee specified in the ticket or auto-rule, if the email matches a Jira user.
Due Date: Set from the ticket's due date field.
Labels: BreachSpider adds labels: breachspider, cve, and the severity level (e.g., critical).
Syncing State
BreachSpider does not currently sync ticket state back from Jira. When you close a ticket in Jira, you should also close the corresponding ticket in BreachSpider to keep the audit trail complete.
Future versions may support bidirectional sync. For now, treat BreachSpider as the authoritative audit record and Jira as the workflow tool.
Multiple Jira Projects
You can create multiple Jira connections pointing to different projects:
- Connection 1: Project OT-SEC for OT findings
- Connection 2: Project IT-PATCH for OS findings
- Connection 3: Project NET-OPS for NETWORK findings
Reference the appropriate connection in each auto-ticket rule to route findings to the correct project.
Troubleshooting
"Authentication failed": Verify your API token is correct and has not expired. For Jira Cloud, ensure the email address matches the account that generated the token.
"Project not found": The project key must match exactly (case-sensitive). Verify the project exists and your Jira user has permission to create issues in it.
"Issue type not found": The issue type must match an existing type in the target project. Check your Jira project settings for available issue types.
"User not found for assignee": The assignee email must match a Jira user with access to the project. If the email does not match, the issue is created without an assignee.