Salesforce is strengthening security by enforcing more stringent controls across user identity, data protection, and access controls. Details surrounding the specific controls being rolled out will be published once those plans are finalized. Take action now to ensure a seamless transition and maintain your organization's security posture.
Beginning June 2026, Salesforce plans to require the implementation of additional security controls and settings.
Salesforce Platform Admins
Require Multi-Factor Authentication (MFA): Ensure MFA is required in sandbox and production orgs, for all employee license users, either through Salesforce or through an Single Sign-On (SSO) provider. Even with MFA enabled for login, certain sensitive actions after login will trigger step-up authentication. For help with implementing MFA, see Multi-Factor Authentication for Salesforce Orgs.
Ensure all System Administrator users adopt Phishing-Resistant MFA for login: Phishing-Resistant MFA requires built-in authenticators, security keys, or equivalent. To make phishing-resistant MFA options available to users, enable built-in authenticators or security keys.
Restrict Login IP Addresses in Profiles: Specifying allowed IP address ranges on profiles denies a user access if they attempt to sign in from an unauthorized IP address. Note that by default, this check applies at login time only and users are not automatically logged out mid-session if their IP address changes. To enforce IP range validation on every request (not just at login), "Enforce login IP ranges on every request" must be enabled in Session Settings. Only when this setting is active will users be logged out mid-session due to an IP address change. This additional protection is particularly important if your org has not implemented Phishing-Resistant MFA. See Restrict Login IP Addresses.
Enable a Transaction Security Policy (TSP) that Restricts Large Data Exports: It has been previously recommended that Salesforce Shield and Event Monitoring customers have a TSP on ReportEvent that triggers step-up authentication when report data is downloaded. In June 2026, if an org with Shield or Event Monitoring does not already have one of these TSPs in place, one will be added and enabled automatically. See Transaction Security.
Avoid Connecting from Anonymizing Proxies and High-Risk IP Addresses: Ensure your users are not connecting to Salesforce via anonymizing VPNs or from other high-risk IP addresses. Salesforce monitors for and blocks high-risk connections and will continue to do so.
|
Date |
Change |
|
March 26, 2026 |
Initial publication |
005317465

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.