Pangea Docs FAQ Get early access

Docs / Observability and data

Secureframe

Connect Secureframe read-only so the agent can find failing compliance tests and help you fix them.

Pangea connects to Secureframe with an API key and secret that you create in your company settings. The connector is read-only. The agent reads which compliance tests are failing, for frameworks such as SOC 2, ISO 27001, HIPAA, PCI and GDPR, and helps you fix them. It never writes to Secureframe.

Connect

1. Create an API key

  1. Sign in to Secureframe as an admin.
  2. Open Company settings → API keys.
  3. Click Create API key.
  4. Copy the API key (the key id) and the API secret. Secureframe shows the secret only once.

2. Connect in Pangea

As a team Administrator, open Connectors → Connect → Secureframe and fill in:

Field Notes
Label A friendly name, for example Acme Secureframe
Region US (api.secureframe.com) or UK (api-uk.secureframe.com). It must match your account's data region
API Key The key id
API Secret Shown once when you create the key. Stored encrypted

Pangea verifies the credentials with the Secureframe API before it saves them. The secret stays on Pangea's servers. The agent reads through a Pangea proxy and never sees your Secureframe credentials.

In the Pangea app

A connected organization gets a Failed Tests page. The connection itself lives in Connectors, where an Administrator can manage its allow-list or remove it.

What the agent can do for you

The agent reads the failing tests, all tests, or a custom query, each with its failure message and fix steps. The real value is fixing things across connectors:

Permissions

Team Administrators connect and remove this connection. They can limit who uses it with a member allow-list. Fixes made through other connectors follow Auto Mode and Full Access, and significant infrastructure work goes through plans.

Good to know