A finding that lives only in a security console tends to wait. The Jira integration puts it where engineers already work. This guide follows the Safeguard Jira integration page.
What it is
The docs list full support for Jira Cloud, Jira Server 8.x and later, and Jira Data Center. Safeguard can create issues from findings, keep statuses in sync in both directions, and map fields.
How to use it
First create a token.
- Jira Cloud: in Atlassian Account Settings, choose Create API token. It is shown once.
- Server or Data Center: in your Jira profile open Personal Access Tokens and click Create token. Give it a name and an expiry.
Then connect, under Settings → Integrations → JIRA.
- Click Connect JIRA.
- Enter the JIRA URL, the Email (Cloud email or Server username) and the API Token.
- Click Test Connection, then Save.
- Click Configure Projects. For each organization set the JIRA Project, Issue Type and Default Assignee.
The docs advise a dedicated service account, limited token permissions and regular rotation.
Automatic issues
Four trigger rules create issues: New Critical Vulnerability, New High Vulnerability, Gate Failure and Policy Violation. The summary follows the pattern [SEVERITY] CVE-XXXX-XXXXX in {component}, and the description carries the CVE, severity, CVSS score, component, project, remediation advice and links to Safeguard and NVD.
Custom field mapping covers Severity (to Priority or a custom field), CVE ID, Component (labels or a custom field), CVSS Score and Project (labels).
Status sync
From Jira to Safeguard, Done or Resolved marks the finding resolved, Won't Fix creates a risk-acceptance mitigation, and Duplicate links to an existing finding. From Safeguard to Jira, a resolved finding moves the issue to Done, a new mitigation adds a comment and a severity change updates priority. To configure, open the integration settings, click Status Mapping, map statuses and enable bidirectional sync.
Manual and bulk
In the Findings tab, select findings, then Actions → Create JIRA Issue, review and click Create. For many at once, filter, select, then Bulk Actions → Create JIRA Issues. Link JIRA Issues attaches existing issue keys.
The docs say the REST endpoints for linked issues are planned and not available yet.
Quick check
What does Won't Fix in Jira do in Safeguard?
It creates a risk-acceptance mitigation on the finding.
Which events create Jira issues automatically?
New Critical Vulnerability, New High Vulnerability, Gate Failure and Policy Violation.
