Asana
Connect Asana to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Asana to collect ticketing evidence with automated compliance tests, switched on per workspace.
| Category | Ticketing |
| Connect with | API token, MCP server |
| What a connection produces | Automated compliance tests |
| Asana's guide | developers.asana.com |
Connect with an API token
-
In Asana:
- Sign in to Asana and open the developer console (https://app.asana.com/0/my-apps).
- Select + Create new token.
- Enter a Token name that describes its use (for example Safeguard).
- Click Create token, then copy the token; you will only see it once.
Where to find the other values:
- Workspace ID (optional): While signed in, open https://app.asana.com/api/1.0/workspaces and copy the gid of your workspace from the JSON.
Asana shows the secret only once, so copy it before you leave the page.
The fetched docs show no scope selection for personal access tokens: the token acts with the full access of the user who created it, so the read-only grants (workspace_memberships:read, users:read, tasks:read, tags:read) cannot be narrowed here. Use a dedicated user with the least access that still sees the workspace.
Source: developers.asana.com, developers.asana.com, checked 2026-10-07.
The permissions Safeguard needs:
workspace_memberships:read,users:read,tasks:read,tags:read. -
On Compliance › Connectors, open Asana, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. Workspace ID (optional) — -
Click Connect with token.
Connect with the MCP server
Choose MCP server: the address https://mcp.asana.com/sse is filled in. Sign in to Asana when asked. It lets Griffin AI search Asana; the compliance evidence comes from the API token connection.
Frameworks
Safeguard's automated tests read Asana 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