Secureframe

Record your Secureframe connection as compliance as code evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Secureframe:

   1. Sign in to Secureframe as a user with the Super Admin access role (Admins do not see the create button).
   2. Open your profile in the top right, then click Company Settings.
   3. Open the API keys tab, then click Create API Key.
   4. Assign an Owner (the key acts with this user's role, so pick a user with the least-privileged role that can read the data), add an API Key Name, then click Generate Key.
   5. Copy both the API key and the API secret. Secureframe expects them together in the header Authorization: <API_KEY> <API_SECRET>, so paste them in that form into API token / Personal access token.

   Where to find the other values:

   • Base URL (optional): US (default): https://api.secureframe.com; UK: https://api-uk.secureframe.com. Use the region your Secureframe account is hosted in.

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

   Source: support.secureframe.com, checked 2026-10-07.

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

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads Secureframe yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Compliance As Code 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