Bridgecrew

Record your Bridgecrew connection as infrastructure evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Bridgecrew:

   1. Sign in to Prisma Cloud as a System Admin, or as an administrator whose role has API access enabled (by default only the System Admin has API access).
   2. Go to Settings › Access Control › Access Keys and select Add › Access Key.
   3. Enter a descriptive Name for the key.
   4. Optionally select Key Expiry and set a date and time (unchecked means the key never expires).
   5. Click Create.
   6. Copy or download the Access Key ID and Secret Key as CSV; after you close the window you cannot view the secret key again.

   Where to find the other values:

   • Base URL (optional): Your tenant's Prisma Cloud API URL (for example https://api.prismacloud.io), from Prisma Cloud's API URL list (https://pan.dev/prisma-cloud/api/cspm/api-urls/).
   • API token / Personal access token: Checkov expects a Prisma Cloud access key in the form access_key_id::secret_key.

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

   Bridgecrew's public documentation does not cover every step.

   No current Bridgecrew-branded docs were reached; the Bridgecrew platform's API keys are now Prisma Cloud access keys (Checkov's CLI reference accepts *.bridgecrew.cloud and *.prismacloud.io API URLs with a key in access_key_id::secret_key form). Prisma Cloud's pages do not document a read-only role for access keys; access follows the creating administrator's role, and some roles (e.g. Build and Deploy Security) may create only one key. Legacy bridgecrew.cloud standalone token steps were not verified.

   Source: docs.prismacloud.io, docs.prismacloud.io, checkov.io, checked 2026-10-07.

2. On Compliance › Connectors, open Bridgecrew, 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 Bridgecrew yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• 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