Vercel checks
26 articles
- Ensure Vercel project has skew protection enabled to prevent version mismatches during deployments
- Ensure Vercel project has deployment protection enabled on preview deployments
- Ensure Vercel project has no environment variables targeting all three environments
- Ensure Vercel project has automatic exposure of system environment variables disabled
- Ensure Vercel project has no secret-like environment variables stored as plain text
- Ensure Vercel sensitive production environment variables do not target preview
- Ensure Vercel project has directory listing disabled
- Ensure Vercel project has deployment protection enabled on production deployments
- Ensure Vercel project has password protection configured for deployments
- Ensure Vercel project has Git fork protection enabled to prevent untrusted forks from accessing secrets
- Ensure Vercel project has custom firewall rules configured
- Ensure Vercel project has managed WAF rulesets enabled
- Ensure Vercel project has rate limiting rules configured
- Ensure Vercel project has the Web Application Firewall enabled
- Ensure Vercel project has IP blocking rules configured
- Ensure Vercel domains are verified
- Ensure Vercel domain DNS records are properly configured
- Ensure Vercel domains have a valid, non-expired SSL certificate
- Ensure Vercel team has SAML SSO enabled for centralized identity management
- Ensure Vercel team enforces SAML SSO for all members
- Ensure Vercel team has directory sync (SCIM) enabled for automated provisioning
- Ensure Vercel team follows least privilege with a limited number of owner roles
- Ensure Vercel team has no stale pending invitations older than 30 days
- Ensure Vercel API tokens are not stale or unused for over 90 days
- Ensure Vercel API tokens have not expired
- Ensure Vercel production deployments originate from a stable branch