Vercel Security Dashboard is now generally available

Vercel's Security Dashboard is now generally available on all plans, providing a unified view of security posture across accounts and projects, with automatic flagging of issues like team members without 2FA, long-lived credentials, public preview deployments, and stale environment variables. The dashboard orders misconfigurations by risk and offers CSV export, while a new Vercel CLI command `vercel security check` enables agents to apply fixes such as enabling Git fork protection, marking environment variables as sensitive, and replacing static credentials with OIDC federation.

The Vercel Security Dashboard is now generally available on all plans, giving you one place to see your security posture across every account and project. You can access the Security Dashboard in the UI https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fsecurity& or run vercel security check in the Vercel CLI. As teams grow and coding agents make it faster to spin up projects, small misconfigurations add up quietly. The Security Dashboard automatically flags issues like: Team members without 2FA Long-lived credentials that can be replaced with OIDC Public preview deployments Non-sensitive and stale environment variables Misconfigurations are ordered by risk with the most severe first, and each finding links to the settings that fix them. Findings that are just noise for your team can also be muted, and all results can be exported to a CSV file for triage or reporting. You can also run the same checks in your terminal through the new Vercel CLI https://vercel.com/docs/cli/security vercel security check command, allowing your agents to work through the findings for you. An agent using vercel security check --findings can read what failed, apply the fix and re-check to confirm. Fixes an agent can apply include: Turning on Git fork protection Marking an environment variable as sensitive Replacing a static credential with OIDC federation You can also scope the check to one project with --project when you want a narrow change set. In CI or any other non-interactive environment, the command writes the report to stdout as JSON automatically, giving agents structured output without extra flags. Get started by running your first scan from the Security Dashboard https://vercel.com/~/settings/security , and learn more in the Security Dashboard documentation https://vercel.com/docs/security/security-dashboard .