YouTrack
Connect YouTrack to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect YouTrack 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 |
| YouTrack's guide | jetbrains.com |
Connect with an API token
-
In YouTrack:
- Sign in to YouTrack as the user Safeguard will act as. Creating a token requires the Update Self permission, and the user needs permission to read the projects Safeguard should cover.
- From the main navigation menu, select your avatar, then select Profile.
- Select the Account Security tab and click New token.
- Enter a name and, under scope, select YouTrack only (it covers the /api/... endpoints). Do not add YouTrack Administration.
- Click Create token and copy the token; as soon as you close the dialog you can't access it again.
Where to find the other values:
- Instance URL: The https address you use to open your YouTrack server in the browser.
YouTrack shows the secret only once, so copy it before you leave the page.
A permanent token acts with the permissions of the user who created it; the scope only limits which services it can call. The role permission names for reading issues and users were not on the fetched page; the instance URL location is not stated on the token page.
Source: jetbrains.com, checked 2026-10-07.
The permissions Safeguard needs:
Read Issue,Read User (Hub). -
On Compliance › Connectors, open YouTrack, click Connect, choose API token and fill in:
Field What to enter Instance URL Required. Your own server: an https address reachable from the internet. Permanent token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read YouTrack 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 | CC6.2, CC6.3, CC7.1, CC7.3, CC7.4, CC7.5 | 8 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.5.25, A.5.26, A.5.27, A.6.5, A.8.2, A.8.8 | 8 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.308(a)(6) | 8 |
| PCI DSS | Automated tests | 6.3.3, 7.2.2, 7.2.4, 8.2.5, 12.10.1, 12.10.6 | 8 |
| NIST CSF 2.0 | Automated tests | ID.IM-03, PR.AA-01, PR.AA-05, RS.MA-02, RS.MA-03, RS.MI-02 | 8 |
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