Jira
Connect Jira Cloud so Safeguard can check how security issues, incidents and offboarding tickets are handled.
Connect Jira
Safeguard reads Jira Cloud as a ticket tracker, with read access: security, incident, offboarding and post-mortem tickets, their priority, assignee, status and resolution dates, the issues linked to incidents, and the site's user accounts for access reviews.
Jira Cloud only. Jira Data Center and Jira Server are not supported.
Option A: OAuth
- Open Compliance › Connectors, search for Jira and click Connect.
- Choose OAuth and approve Atlassian's consent screen. Safeguard asks for
read:jira-workandoffline_access.
An OAuth connection reads up to three Jira sites that your Atlassian account can reach. Everything is read as your account, so it sees what you can see.
Option B: API token
- Sign in to id.atlassian.com with the account Safeguard should read as, and open Security › API tokens to create a token. The token has that account's Jira permissions, so use an account that can browse the projects holding security and incident tickets.
- In Safeguard, open Compliance › Connectors › Jira › Connect and choose API token:
| Field | What to enter |
|---|---|
| Atlassian account email | The account the token was created on |
| API token | The token |
| Site URL | Your site, for example https://your-team.atlassian.net |
Several sites
Jira can be connected more than once, one connection per site. When multiple accounts are switched on for your workspace, open the connected card and choose Add another account.
What Safeguard checks
Safeguard finds tickets by label or issue type (security, incident, offboarding, post-mortem) that are open or were resolved recently, then checks:
- Security issues are assigned, and the highest-priority ones are resolved within their time limit
- Incidents have their follow-up work closed, and a post-mortem
- Every departure has an offboarding ticket
- Jira accounts belong to people in your personnel register, and people who left no longer have access (bots and service-desk customers are left out)
A ticket counts as resolved at its resolution date, or, in a workflow that sets no resolution, when it moved to a Done status.
Troubleshooting
- Not working with an API token: check the email matches the account that created the token, and that the site URL is your
atlassian.netaddress. - Tickets are missing: the connecting account cannot browse that project. Grant it browse access, or connect with an account that has it.