Integrations

Connect third-party services for deeper security analysis.

Integrations let Vergate access your cloud provider accounts and run provider-specific security checks. Credentials are encrypted with Fernet encryption before storage.

#Supported Providers

#How Credentials Are Stored

All credentials are encrypted using Fernet symmetric encryption before being stored in the database. The encryption key is set via the INTEGRATION_ENCRYPTION_KEY environment variable.

Caution. If you lose the encryption key, all stored credentials become permanently unreadable. Generate it once and keep it safe.

#Health Checks

Each integration has a health check that validates the stored credentials against the provider's API. If a token expires or is revoked, the integration will show as unhealthy.

#Security Scanning

Once connected, you can run security scans against your integrations. Each provider has a dedicated analyzer that checks provider-specific security configurations:

ProviderChecks
GitHubToken validity, branch protection, secret scanning, Dependabot
VercelToken validity, password protection, sensitive env vars
NetlifyToken validity, SSL, HTTPS, security headers (CSP, HSTS)
SupabaseConnectivity, RLS, API exposure, MFA, OTP expiry
CloudflareSSL mode, Always HTTPS, HSTS, DNSSEC, min TLS, WAF
FirebaseService account auth, Firestore rules, hosting sites
RailwayToken validity, env var secrets, deployment URLs
StripeKey validity, test/live mode, webhook config, API keys
Fly.ioToken validity, TLS cert expiry, IP assignments
RenderToken validity, env var secrets, auto-deploy
SlackToken validity, token type, channel exposure, message access