# Ensure Vercel project has skew protection enabled to prevent version mismatches during deployments

- Source: https://support.icompaas.com/support/solutions/articles/a_1790261996952918-ensure-vercel-project-has-skew-protection-enabled-to-prevent-version-mismatches-during-deployments
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Vercel cloud](https://support.icompaas.com/support/solutions/c_1790103019086234) › [Vercel checks](https://support.icompaas.com/support/solutions/folders/f_1790103034130491)
- Last updated: 2026-09-24
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure Skew Protection is enabled for the project, so that each user's browser keeps talking to the same deployment version it first loaded, even after a new deployment goes live. This prevents the client and server from running different versions of the application during a rollout.

**Rationale**

When a new version is deployed, users who already have the old version open may send requests that the new server code does not understand. This version skew can cause errors, failed form submissions, broken pages, and unexpected behavior. Skew Protection locks each client to its original deployment for a period of time, making rollouts safer and more reliable.

**Impact**

-   Reduces errors for users during new deployments
    
-   Client and server stay on the same version
    
-   Requires the Enable access to System Environment Variables setting to be checked
    

**Default Value**

Skew Protection is a paid feature: the dashboard shows it with a Pro badge and an Upgrade button on the Hobby plan. On paid plans, it is enabled by default for projects created after November 19, 2024 that use a supported framework, and older projects must enable it manually.

**Pre-Requisites**

-   Team Owner or Member role, or Project Administrator
    
-   Pro or Enterprise plan
    
-   A supported framework, or code that sends the deployment ID
    
-   Enable access to System Environment Variables checked
    
-   Deployments not created with the --prebuilt option
    

**Test Plan**

1.  Sign in to Vercel at [https://vercel.com](https://vercel.com/).
    
2.  Select your team from the team switcher.
    
3.  Select the project from the dashboard.
    
4.  Open Settings in the sidebar and select Advanced.
    
5.  In the Skew Protection section, verify that the toggle shows Enabled.
    
6.  If it is disabled, follow the implementation steps.
    

**Implementation Steps**

1.  Sign in to Vercel at [https://vercel.com](https://vercel.com/).
    
2.  Select your team from the team switcher.
    
3.  Select the project from the dashboard.
    
4.  Open Settings in the sidebar, select Environments, open Production, and confirm that Enable access to System Environment Variables is checked at the bottom of the Environment Variables section.
    
5.  Open Settings in the sidebar and select Advanced.
    
6.  In the Skew Protection section, turn on the toggle, optionally set a maximum age, and save.
    
7.  Redeploy your latest production deployment.
    

**Backout Plan**

1.  Sign in to Vercel at [https://vercel.com](https://vercel.com/).
    
2.  Select your team from the team switcher.
    
3.  Select the project from the dashboard.
    
4.  Open Settings in the sidebar and select Advanced.
    
5.  In the Skew Protection section, turn off the toggle and save.
    
6.  Redeploy your latest production deployment.
    

**Reference**

-   [https://vercel.com/docs/skew-protection](https://vercel.com/docs/skew-protection)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.