Tines
Connect Tines to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Tines 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 |
| Tines's guide | tines.com |
Connect with an API token
-
In Tines:
- Sign in to Tines as a tenant owner (listing all users needs tenant admin access).
- From the Tines settings page, select API keys under Access & security.
- Create a new key manually from this page. Choose a Tenant owner API key (full Owner access to the tenant, linked to a separate service account user) or a Personal API key created by a tenant owner.
- Copy the key value.
Where to find the other values:
- Instance URL: Your Tines tenant address (the tines.com URL you sign in to).
Tines's public documentation does not cover every step.
Tines' public docs name the API keys page and key types but not the create button or form labels, and don't say whether the key is shown once. A tenant owner can restrict API key creation to owners and users with the API_KEY_CREATE permission. Service API keys can be given specific tenant permissions instead of full owner access; whether a narrower permission covers user listing was not verified.
Source: tines.com, tines.com, checked 2026-10-07.
The permissions Safeguard needs:
tenant admin. Tines shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. -
On Compliance › Connectors, open Tines, click Connect, choose API token and fill in:
Field What to enter Instance URL Required. An address under tines.com. API key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Tines 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 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
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