SolarWinds Service Desk
Connect SolarWinds Service Desk to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect SolarWinds Service Desk 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 |
| SolarWinds Service Desk's guide | apidoc.samanage.com |
Connect with an API token
-
In SolarWinds Service Desk:
- Sign in to Service Desk as the user Safeguard will act as; only someone with a Service Desk administrator license can generate a token, and administrators cannot generate tokens for other users. The token shares the same permissions as that user's role.
- Go to Setup › Users & Groups › Users and open your own user detail page (not your User Profile Card).
- Click Actions and select Generate JSON Web Token from the dropdown menu.
- Under JSON Web Token on the user detail page, click Copy.
SolarWinds Service Desk's public documentation does not cover every step.
The token stays on the user detail page with Copy, Reset, Delete and Hide Token; tokens can only be viewed by the user who created them. If the user is disabled, the token is disabled too. On ESM accounts, administrators generate a separate token per service provider. The regional API hosts for the Region field were not confirmed: apidoc.samanage.com returned no readable content.
Source: documentation.solarwinds.com, apidoc.samanage.com, checked 2026-10-07.
The permissions Safeguard needs:
view incidents, audits and users. -
On Compliance › Connectors, open SolarWinds Service Desk, click Connect, choose API token and fill in:
Field What to enter Region Required. API token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read SolarWinds Service Desk 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