Prowler

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

Connect with an API token

1. In Prowler:

   1. Sign in to Prowler Cloud as a user whose role has the MANAGE_ACCOUNT permission (without it the API Keys section stays hidden).
   2. Go to Profile › Account and click Create API Key.
   3. Copy the full key value now. It appears only once and cannot be retrieved later; afterwards only the key prefix stays visible.

   Where to find the other values:

   • Base URL (optional): Prowler Cloud's API is at https://api.prowler.com (examples use https://api.prowler.com/api/v1/...). Leave blank for Prowler Cloud; for a self-hosted Prowler Local Server use your own address.

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

   The fetched page documents no per-key scope, so a 'read findings' only key could not be confirmed; the key acts with the creating user's access. Prowler App is now called Prowler Local Server for self-hosting.

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

   The permissions Safeguard needs: read findings.

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

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.
   Base URL (optional)	—

3. Click Connect with token.

Frameworks

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

• 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