Redmine
Connect Redmine to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Redmine 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 |
| Redmine's guide | redmine.org |
Connect with an API token
-
In Redmine:
- As a Redmine administrator, go to Administration › Settings › API and check Enable REST API, then save.
- Sign in to Redmine as the user whose rights Safeguard should use and open your account page (/my/account).
- Copy the API key shown in the right-hand pane of the account page.
- Make sure the user is a member of every project Safeguard should read, with a role that has the View Issues permission ("Allow user to view project issues").
Where to find the other values:
- Instance URL: The https address of your Redmine server, the same base address you use in the browser (for example https://redmine.example.com).
Redmine's public documentation does not cover every step.
The API key carries the rights of the user it belongs to; Redmine has no read-only key type. The official pages do not name the exact link label for revealing the key in the right-hand pane or the menu path to role editing, so those labels are left out. The key stays visible on the account page (not a one-time display), per the wiki saying it can be found there when logged in.
Source: redmine.org, redmine.org, checked 2026-10-07.
The permissions Safeguard needs:
View issues. -
On Compliance › Connectors, open Redmine, 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. API key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Redmine 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, CC7.1, CC7.3, CC7.4, CC7.5 | 5 |
| ISO/IEC 27001 | Automated tests | A.5.18, A.5.25, A.5.26, A.5.27, A.6.5, A.8.8 | 5 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(6) | 5 |
| PCI DSS | Automated tests | 6.3.3, 8.2.5, 12.10.1, 12.10.6 | 5 |
| NIST CSF 2.0 | Automated tests | ID.IM-03, PR.AA-05, RS.MA-02, RS.MA-03, RS.MI-02 | 5 |
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