๐ Salesforce security requirements are evolving, and an important deadline is approaching.
Hi all! There have been a lot of discussions about Salesforce's upcoming enforcement deadline for phishing-resistant multi-factor authentication (MFA), so I thought I'd share our Time Technology blog to help break it down for everyone. (See link below).
Beginning 22 June for Sandboxes and 1 July for Production, Salesforce will enforce phishing-resistant MFA for administrators and other privileged users. Traditional MFA methods, such as authenticator apps and push notifications, may no longer meet the new requirements, with stronger authentication methods like passkeys, built-in device authenticators, and security keys becoming the standard.
The change is designed to help organisations better protect against increasingly sophisticated phishing and social engineering attacks, which continue to be one of the most common causes of security breaches.
If your organisation uses Salesforce, now is a good time to understand:
โ Who is affected
โ What authentication methods qualify
โ What actions administrators should take before enforcement begins
We've put together a practical overview of what is changing, why it matters, and how to prepare.
๐ Read the full blog here: https://time-technology.com/salesforce-insights/salesforce-phishing-resistant-mfa-what-is-changing-and-why-it-matters/?utm_source=Nonprofit+Hub&utm_medium=Trailblazer+Community&utm_campaign=Nonprofit+Hub+Salesforce+Community&utm_id=2026Q2
