Identity & security
Vanta
Create a read-only app in Vanta so Dave can see which controls and tests are failing.
Vanta is connected by creating an app in its developer console. The app issues the credentials Dave uses to read compliance frameworks, controls, and failing tests.
Connect
Section titled “Connect”-
In Vanta, go to Settings → Developer console and create an app of type Manage Vanta.
-
Give the app read access only. Dave never writes to Vanta.
-
Copy the Client ID and Client secret the app generates. The secret is shown once, at creation.
-
In Dave, go to Integrations → Add integration → Vanta.
-
Paste the Client ID and Client secret.
-
Set a Label — the name you will use to refer to this account, e.g.
prod. -
Choose Connect Vanta.
The secret is stored encrypted and never shown again.
Permissions
Section titled “Permissions”Dave requests one scope when it signs in with the app’s credentials:
vanta-api.all:readThe app must allow read access. Dave only sends read requests, so it never needs write access.
Creating the app needs an Admin in Vanta.
Manage the connection
Section titled “Manage the connection”Review, rotate the secret of, or delete the app in Vanta under Settings → Developer console.
Disconnect in Dave stops Dave using the credentials, but the app stays in Vanta until you delete it there.
To rotate the secret, Disconnect, then add the connection again with the same label and the new secret. Connect again only re-checks the credentials Dave already has.
Troubleshooting
Section titled “Troubleshooting”- Vanta rejected the credentials. Check the client ID and client secret, then Disconnect and add the connection again with the same label and the correct values.
- Validation takes long. Dave keeps retrying while Vanta is unreachable. Confirm the app is still active in Vanta.