This page serves as the ongoing roadmap for critical security-related product changes to Marketing Cloud Engagement. Our intention is to provide you with the necessary lead time, technical clarity, and architectural guidance to maintain the security of your data as these changes are rolled out.
Please note that this roadmap focuses on specific features designed to minimize risk from phishing attacks, data exfiltration, and account takeover attempts. It is evolving and not inclusive of all Salesforce security-related changes.
Find details for each planned change in the table below.
|
Security Control |
Implementation Timeline / Recommendations |
Knowledge Article / Resources |
|
Step-up Authentication |
July 30, 2026: Rollout staggered over 5 days | |
|
Secret Expiration and Time-To-Live |
September 30, 2026 |
Marketing Cloud Engagement Secret Expiration and Time-To-Live (TTL) |
|
IP Allowlisting |
July 30, 2026: Recommendations start for IP allowlisting. Technical enforcement is planned for the future; details will be emailed. | |
|
Phishing-Resistant Multi-Factor Authentication for Admins |
Status: Currently strongly recommended. Technical enforcement is planned for the future; guidance will follow. | Phishing Resistant MFA (PR-MFA) for High-Privilege Marketing Cloud Engagement Administrator Accounts |
|
Multi-Factor Authentication for SSO Users |
Status: MFA for SSO users has been required since February 1, 2022. Technical enforcement is planned for the future; guidance will follow. |
MFA Requirement for Marketing Cloud Engagement (MCE) SSO Users |
|
Date |
Change |
|
August 11, 2026 |
Added the link to the new article for MFA Requirement for Marketing Cloud Engagement (MCE) SSO Users |
|
July 21, 2026 |
Corrected timelines:
|
|
July 16, 2026 |
Initial publication |
005389116

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.