Torq
Connect Torq to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Torq to collect security automation evidence with automated compliance tests, switched on per workspace.
| Category | Security Automation |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Torq's guide | developers.torq.io |
Connect with an API token
-
In Torq:
- In Torq, open the workspace Safeguard will read, click your user icon at the bottom of the navigation bar and select API Keys.
- Click Create API Key and enter a meaningful key name.
- Select an expiration date (predefined, or Select from calendar).
- Set Type to Service account and select the least-privileged role that can read cases (or keep Personal access to inherit your own role).
- Click Create, then copy the client ID and the secret; the secret will not be displayed again.
Where to find the other values:
- Client ID: Shown with the secret right after you click Create on the API Keys page.
- Region: If you sign in on the eu.torq.io domain, your workspace is in the EU (token endpoint auth.eu.torq.io); otherwise it is US (auth.torq.io).
Torq shows the secret only once, so copy it before you leave the page.
API keys are specific to a workspace. Choosing service-account scope across workspaces is limited to Org Admins. Torq's role names for read-only case access were not listed on the fetched page.
Source: kb.torq.io, developers.torq.io, checked 2026-10-07.
The permissions Safeguard needs:
read on cases. -
On Compliance › Connectors, open Torq, click Connect, choose API token and fill in:
Field What to enter Client ID Required. Client secret Required. Stored encrypted and never shown again. Region Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Torq 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.3, CC7.4 | 2 |
| ISO/IEC 27001 | Automated tests | A.5.26 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(6) | 2 |
| PCI DSS | Automated tests | 12.10.1 | 2 |
| NIST CSF 2.0 | Automated tests | RS.MA-03, RS.MI-02 | 2 |
These tests are switched on per workspace by the Safeguard team.
Related
- Security Automation 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