Private Vanta connection

A customer-managed VeriProof deployment can connect through a private Vanta app owned by the customer. The customer stores the app secret in the customer’s Azure Key Vault. VeriProof SaaS and VeriProof-owned Azure resources are excluded from the connection.

Before you connect

Confirm these owners and decisions:

• a Vanta administrator who can create and approve the private app;
• an Azure administrator who can store the secret and manage Key Vault access;
• the Vanta region and organization that will receive the resources;
• the approved member, governance-task, and assurance-document scope; and
• the owners for credential rotation, disablement, and incident response.

Configure the connection

1. Open Settings → Vanta in the customer-managed VeriProof portal.
2. Create the private Vanta app with the scopes shown by the setup flow.
3. Store its client secret in the customer Key Vault named by the deployment.
4. Run the setup command shown in Settings → Vanta from an approved administrator workstation.
5. Return to the portal and select Verify connection.
6. Confirm the accepted member and governance-task counts after the next refresh.

The private connection uses the same resource, evidence, retention, and data-exclusion boundaries as the SaaS integration. See Vanta for those details.

Operate the connection

• Rotate or revoke the secret in the customer Key Vault.
• Select Verify connection after a credential or permission change.
• Review the last resource update and accepted counts in Settings → Vanta.
• Select Disconnect Vanta to stop future resource and evidence updates.

Data already accepted by Vanta remains subject to the customer’s Vanta retention and access controls.