# Ensure password changes require current password or reauthentication

- Source: https://support.icompaas.com/support/solutions/articles/a_1790103912395733-ensure-password-changes-require-current-password-or-reauthentication
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Supabase cloud](https://support.icompaas.com/support/solutions/c_1790103054038308) › [supabase checks](https://support.icompaas.com/support/solutions/folders/f_1790103067540538)
- Last updated: 2026-09-22
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure the Email provider settings require users to confirm their identity before changing their password, either by entering their current password or by completing reauthentication with a code sent to them. This stops someone with access to an open session from silently changing the password.

**Rationale**

If an attacker gets access to a signed-in session, for example on a shared or stolen device or through a stolen token, they could change the password and lock the real user out. Requiring the current password or a reauthentication code makes sure only the person who knows the account's credentials can change the password.

**Impact**

-   Stops session hijackers from changing passwords
    
-   Protects users from being locked out of their accounts
    
-   The application's password change form may need updating
    

**Default Value**

By default, secure password change and the current password requirement are disabled.

**Pre-Requisites**

-   Project Owner or Admin role
    
-   Application support for the current password field or the reauthenticate() call
    

**Test Plan**

1.  Sign in to the Supabase Dashboard at [https://supabase.com/dashboard](https://supabase.com/dashboard).
    
2.  Select your project.
    
3.  Open Authentication in the sidebar, select Sign In / Providers, and open the Email provider.
    
4.  Verify that Secure password change or Require current password when updating is enabled.
    
5.  If neither is enabled, follow the implementation steps.
    

**Implementation Steps**

1.  Update the application's password change form to send the current password or a reauthentication code.
    
2.  Sign in to the Supabase Dashboard at [https://supabase.com/dashboard](https://supabase.com/dashboard).
    
3.  Select your project.
    
4.  Open Authentication in the sidebar, select Sign In / Providers, and open the Email provider.
    
5.  Enable Require current password when updating, or enable Secure password change.
    
6.  Select Save.
    

**Backout Plan**

1.  Sign in to the Supabase Dashboard at [https://supabase.com/dashboard](https://supabase.com/dashboard).
    
2.  Select your project.
    
3.  Open Authentication in the sidebar, select Sign In / Providers, and open the Email provider.
    
4.  Disable the setting that was enabled.
    
5.  Select Save.
    

**Reference**

-   [https://supabase.com/docs/guides/auth/password-security](https://supabase.com/docs/guides/auth/password-security)

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