Vercel
Connect Vercel to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Vercel to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.
| Category | Cloud Infrastructure |
| Connect with | API token, MCP server |
| What a connection produces | Automated compliance tests |
| Vercel's guide | vercel.com |
Connect with an API token
-
In Vercel:
- In the scope selector at the top left of the Vercel dashboard, make sure you are viewing your personal account, then open the Account Tokens page (https://vercel.com/account/tokens) under your account's Settings.
- Enter a descriptive token name.
- Open Scope and select the team Safeguard should read. If a project list opens, select All Projects to make a team-scoped token.
- Choose an expiration and select Create.
- Copy the token (it begins with vcp_): Vercel shows the value only once.
Where to find the other values:
- Team ID (optional): Open your team's dashboard, go to Settings in the sidebar, choose General, and scroll to the Team ID section (or open https://vercel.com/teams/<your_team_name>/settings#team-id).
Vercel shows the secret only once, so copy it before you leave the page.
Vercel issues no read-only token: a team-scoped token can read and write that team's resources. Some teams require two-factor authentication or SAML before you can create tokens scoped to them. Team-scoped tokens do not need the Team ID on API requests.
Source: vercel.com, vercel.com, checked 2026-10-07.
The permissions Safeguard needs:
team-scoped token. Vercel issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time. -
On Compliance › Connectors, open Vercel, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. Team ID (optional) — -
Click Connect with token.
Connect with the MCP server
Choose MCP server: the address https://mcp.vercel.com/ is filled in. Sign in to Vercel when asked. It lets Griffin AI search Vercel; the compliance evidence comes from the API token connection.
Frameworks
Safeguard's automated tests read Vercel 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.1, CC6.2, CC6.3, CC8.1 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.3, A.8.5, A.8.9 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(d) | 4 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5, 8.4.2 | 4 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05, PR.PS-01 | 6 |
These tests are switched on per workspace by the Safeguard team.
Related
- Cloud Infrastructure 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