{"slug": "vercel-security-dashboard-is-now-generally-available", "title": "Vercel Security Dashboard is now generally available", "summary": "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.", "body_md": "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.\n\nYou can access the Security Dashboard in [the UI](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fsecurity&) or run `vercel security check`\n\nin the Vercel CLI.\n\nAs teams grow and coding agents make it faster to spin up projects, small misconfigurations add up quietly. The Security Dashboard automatically flags issues like:\n\nTeam members without 2FA\n\nLong-lived credentials that can be replaced with OIDC\n\nPublic preview deployments\n\nNon-sensitive and stale environment variables\n\nMisconfigurations are ordered by risk with the most severe first, and each finding links to the settings that fix them.\n\nFindings 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.\n\nYou can also run the same checks in your terminal through the [new Vercel CLI](https://vercel.com/docs/cli/security) `vercel security check`\n\ncommand, allowing your agents to work through the findings for you.\n\nAn agent using `vercel security check --findings`\n\ncan read what failed, apply the fix and re-check to confirm. Fixes an agent can apply include:\n\nTurning on Git fork protection\n\nMarking an environment variable as sensitive\n\nReplacing a static credential with OIDC federation\n\nYou can also scope the check to one project with `--project`\n\nwhen you want a narrow change set.\n\nIn CI or any other non-interactive environment, the command writes the report to stdout as JSON automatically, giving agents structured output without extra flags.\n\nGet 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).", "url": "https://wpnews.pro/news/vercel-security-dashboard-is-now-generally-available", "canonical_source": "https://vercel.com/changelog/vercel-security-dashboard-is-now-generally-available", "published_at": "2026-08-26 00:00:00+00:00", "updated_at": "2026-08-26 14:16:27.560673+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools"], "entities": ["Vercel", "Vercel Security Dashboard", "Vercel CLI"], "alternates": {"html": "https://wpnews.pro/news/vercel-security-dashboard-is-now-generally-available", "markdown": "https://wpnews.pro/news/vercel-security-dashboard-is-now-generally-available.md", "text": "https://wpnews.pro/news/vercel-security-dashboard-is-now-generally-available.txt", "jsonld": "https://wpnews.pro/news/vercel-security-dashboard-is-now-generally-available.jsonld"}}