# Vercel Security Dashboard is now generally available

**Published:** August 26, 2026 | **Authors:** Roman Olynyk, Kostyantyn Voytenko, Sam Bernhardt, Jathin Singaraju | **Contributors:** Kevin Corbett, Eric Dodds

---

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.

![See a complete list of security misconfigurations in your terminal.](//images.ctfassets.net/e5382hct74si/5ZgDXXhK3FBZcsHMpPyw02/84e107e7da59b68207fc439044891682/Frame_4.png)
*See a complete list of security misconfigurations in your terminal.*

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

### The Security Dashboard UI

Misconfigurations are ordered by risk with the most severe first, and each finding links to the settings that fix them.

![See all security misconfigurations, ordered by severity. Each issue links directly to the settings you can configure to resolve it.](//images.ctfassets.net/e5382hct74si/3dVl8ZFo9jL3UkFpVWOVtB/2e577626835d247eb2e1cb0d0a0ce700/350a16d9-4b55-4468-896d-b58c93ff7e24.png)
*See all security misconfigurations, ordered by severity. Each issue links directly to the settings you can configure to resolve it.*

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.

### The Security Dashboard CLI

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).

---

📚 **More updates:** [View all changelog entries](/changelog/sitemap.md) | [Blog](/blog/sitemap.md)