Sweet Security

Record your Sweet Security connection as cspm evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Sweet Security:

   1. Sign in to the Sweet platform (https://app.sweet.security).
   2. Go to Settings › API Tokens and create a tenant API token; copy the api key and secret it gives you.

   Where to find the other values:

   • Base URL (optional): The Sweet platform address, https://app.sweet.security.

   Sweet Security's public documentation does not cover every step.

   Sweet Security's product docs (docs.sweet.security, including its llms.txt) require sign-in. The location comes from the README of Sweet's official Terraform provider (github.com/sweet-security), which says to obtain the tenant API key and secret from Settings -> API Tokens and to use the Admin role for that provider, because it writes cloud-account configuration. Whether a read-only role exists, the button labels, and whether the secret is shown only once were not verified. The credential is a key-plus-secret pair.

   Source: raw.githubusercontent.com, raw.githubusercontent.com, checked 2026-10-07.

2. On Compliance › Connectors, open Sweet Security, 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

Sweet Security publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

These tests are switched on per workspace by the Safeguard team.

Related

• CSPM 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