Jira Integration
Create Jira tickets automatically from matching ThreatPurge alerts.
The ThreatPurge Jira integration allows security operations teams to automatically convert high-priority exposures and threat detections into actionable Jira issues. Seamlessly connect threat telemetry with your engineering and IT remediation queues.
Jira Integration Overview#
When critical vulnerabilities, brand impersonations, or leaked credentials are discovered, security teams need immediate remediation tracking. ThreatPurge connects directly to Atlassian Jira Cloud and Jira Data Center, automatically opening structured tickets with complete technical context and proof.
One-Time Connection Setup#
Connecting your Jira workspace takes only a few minutes from the ThreatPurge Integration Centre:
Open Jira Connector in Integration Centre
Navigate to Settings > Integration Centre and click on the Jira connector card.
Enter Jira Instance URL
Provide your primary Atlassian Cloud or Data Center URL (e.g., https://yourcompany.atlassian.net).
Provide Service Account Credentials
Enter the email address of your designated integration service account and an Atlassian API Token.
Select Target Project & Issue Type
Choose your primary SecOps or engineering project key (e.g., SEC, INFRA) and default issue type (e.g., Bug, Task, Security Incident).
Test Connection & Enable
Click 'Test Connection' to verify API reachability, then activate ticket routing.
Issue Mapping & Priority Rules#
ThreatPurge automatically populates Jira issue fields using standardized severity and asset mapping:
| ThreatPurge Attribute | Jira Target Field | Mapping Behavior |
|---|---|---|
| Alert Title | Summary | Prefixed with [ThreatPurge] and concise incident descriptor |
| Critical Severity | Priority: Highest | High-urgency triage queue placement for immediate attention |
| High Severity | Priority: High | Standard priority queue placement for fast sprint resolution |
| Medium / Low Severity | Priority: Medium / Low | Backlog assignment for scheduled maintenance and review |
| Affected Asset / Domain | Component / Custom Field | Populates affected root domain, IP, or brand keyword |
| Finding Details & Proof | Description | Markdown-formatted dossier with discovery timestamp and remediation recommendations |
| Threat Category | Labels | Tags issue with module label (e.g., asm, dark-web, brand-abuse, tprm) |
Ticket Lifecycle & Deduplication#
ThreatPurge guarantees that repeated scan detections do not flood Jira with duplicate tickets. A deterministic deduplication key ensures that a single Jira ticket is tracked per unique threat observable, keeping engineering queues focused and clean.
Related Documentation
Was this page helpful?
Your feedback helps us improve ThreatPurge technical documentation.