Netlify

Connect Netlify to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Netlify:

   1. In Netlify, open your user settings and go to Applications › Personal access tokens.
   2. Select New access token and enter a descriptive name.
   3. If your team uses SAML SSO, select Allow access to my SAML-based Netlify team (you must be logged in with SSO).
   4. Select an Expiration date.
   5. Select Generate token, copy the token (you can't access it again after leaving the page), then select Done.

   Netlify shows the secret only once, so copy it before you leave the page.

   Source: docs.netlify.com, checked 2026-10-07.

   The permissions Safeguard needs. Netlify issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time.

2. On Compliance › Connectors, open Netlify, click Connect, choose API token and fill in:

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.
   Account (optional)	—

3. Click Connect with token.

Connect with the MCP server

Choose MCP server: the address https://netlify-mcp.netlify.app/mcp is filled in. Sign in to Netlify when asked. It lets Griffin AI search Netlify; the compliance evidence comes from the API token connection.

Frameworks

Safeguard's automated tests read Netlify 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.

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