Jira Service Management
Connect Jira Service Management to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Jira Service Management to collect ticketing evidence with automated compliance tests, switched on per workspace.
| Category | Ticketing |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Jira Service Management's guide | developer.atlassian.com |
Connect with an API token
-
In Jira Service Management:
- Log in to https://id.atlassian.com/manage-profile/security/api-tokens with the Atlassian account Safeguard will use.
- Select Create API token with scopes.
- Give the token a name that describes what it does (for example Safeguard) and select an expiration date (1 to 365 days).
- Select Jira as the app the token can access, then select the read scopes Safeguard needs.
- Select Create, then select Copy to clipboard and save the token.
Where to find the other values:
- Atlassian account email: The email address of the Atlassian account you were logged in to when you created the token.
- Site URL: The address of your Jira Cloud site (the URL you open Jira Service Management at).
Jira Service Management shows the secret only once, so copy it before you leave the page.
Jira Service Management's public documentation does not cover every step.
Atlassian says you can't recover the API token after copying it. The token inherits the account's Jira permissions. The exact app label shown for Jira Service Management in the scoped-token dialog was not quoted on the fetched page. Verification: the scope names (read:servicedesk-request, read:jira-work) are not listed on the fetched page and were removed.
Source: support.atlassian.com, checked 2026-10-07.
The permissions Safeguard needs:
read:servicedesk-request,read:jira-work. -
On Compliance › Connectors, open Jira Service Management, click Connect, choose API token and fill in:
Field What to enter Atlassian account email Required. The account the API token was created on. API tokens authenticate as email + token. API token Required. Create at id.atlassian.com → Security → API tokens. The token inherits this account’s Jira permissions. Stored encrypted and never shown again. Site URL Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Jira Service Management and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC7.4, CC7.5, CC8.1 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.26, A.5.27, A.8.32 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1), 164.308(a)(6) | 3 |
| PCI DSS | Automated tests | 6.5.1, 12.10.1, 12.10.6 | 3 |
| NIST CSF 2.0 | Automated tests | ID.IM-03, PR.PS-01, RS.MA-03 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- Ticketing connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks