44 : Renforcer la sécurité grâce à l'AMF : réflexions et mises en œuvre

19 février 2025

Strengthening Security with MFA: Insights and Implementations 

In today’s digital landscape, ensuring robust security measures is no longer optional—it’s a necessity. With cyber threats on the rise, organizations must adopt stringent authentication methods to protect their systems and data. One of the most effective strategies is Multi-Factor Authentication (MFA). As ServiceNow prepares for its new Yokohama release, MFA is set to become a default security requirement for all internal users who log in without Single Sign-On (SSO). Here’s what you need to know about MFA, its benefits, and how to implement it effectively. 

Why Multi-Factor Authentication (MFA) Matters 

MFA adds an extra layer of security by requiring users to verify their identity using more than just a password. Even if a password is compromised, unauthorized access is still prevented due to the additional authentication factor. Research suggests that MFA can reduce unauthorized access by up to 99%, making it a crucial component of IT security best practices. 

How MFA Affects ServiceNow Users 

With the upcoming ServiceNow Yokohama release, MFA will be enforced for all internal users who do not use SSO. Here’s what organizations need to know: 

  • 30-Day Setup Window – After the first login post-upgrade, users have 30 days to enable MFA. 
  • Mandatory Enforcement – After 90 days, MFA setup will become a requirement for login. 
  • External Users Not Affected (Yet) – At present, MFA enforcement applies only to internal users, but future expansions may include external users as well. 

Available Authentication Methods 

ServiceNow provides several authentication methods to support MFA, allowing users to choose the one that best fits their needs. These include: 

  • Passkeys – Secure, cryptographic authentication keys. 
  • Authenticator Apps – Such as Google Authenticator and Microsoft Authenticator. 
  • Hardware Security Keys – Devices like YubiKey provide an additional security layer. 
  • Biometric Authentication – Face ID, Touch ID, and Windows Hello for seamless access. 
  • Email & SMS One-Time Passwords (OTPs) – Though effective, these are considered less secure due to potential interception risks. 

Implementing MFA in ServiceNow 

To ensure a smooth transition, organizations should take proactive steps before the enforcement deadline: 

  1. Assess Current Authentication Practices – Determine if your organization already uses MFA or if implementation is needed. 
  1. Enable MFA for Admin & High-Privilege Users First – Prioritize protecting users with elevated permissions. 
  1. Educate Users on MFA Benefits – Provide training to ensure users understand the importance of MFA and how to set it up. 
  1. Test Before Full Rollout – Implement MFA in phases to troubleshoot potential issues before full enforcement. 
  1. Integrate with Single Sign-On (SSO) – Using MFA within an SSO environment enhances security while improving user convenience. 

The Future of ServiceNow Security 

With ServiceNow evolving beyond IT Service Management (ITSM) into a full enterprise platform, security is more critical than ever. MFA is not just about compliance—it’s about ensuring the integrity of digital infrastructure and safeguarding sensitive business operations. Organizations that fail to implement strong authentication measures risk exposing their systems to unauthorized access and data breaches. 

Get Expert Assistance 

Need help implementing MFA within your ServiceNow environment? Our team of experts can guide you through the process, ensuring seamless integration with your existing security infrastructure. Contact us today to strengthen your security posture and stay ahead of upcoming changes. 

Security isn’t just a feature—it’s a foundation. Make sure your organization is prepared for the future of digital security with enforced MFA in ServiceNow. 


Podcast Episode Description:

Rejoignez Andy Whiteside et ses invités Mike Sabia et Fred Reynolds pour une plongée dans le thème central de l'authentification multi-facteurs (MFA). Alors que ServiceNow se prépare pour sa nouvelle version Yokohama, l'application du MFA n'est plus seulement une recommandation, mais une nécessité.

Nos experts discutent de l'importance du MFA pour la protection de votre infrastructure numérique, de la manière dont les utilisateurs de ServiceNow peuvent passer en toute transparence à des protocoles de sécurité améliorés et des implications des changements à venir. Que vous soyez un utilisateur chevronné de ServiceNow ou que vous commenciez à peine, cet épisode est rempli d'informations essentielles pour rendre vos mesures de sécurité infaillibles et prêtes pour l'avenir. Ne manquez pas la discussion sur les différentes méthodes d'authentification, y compris la biométrie et les clés de sécurité matérielles, et apprenez comment elles peuvent être intégrées dans vos opérations quotidiennes. 

MFA Becomes the Default in ServiceNow

With its Yokohama release, ServiceNow will enforce multi-factor authentication as a default security measure for internal users who log in without single sign-on. For organizations using ServiceNow as a platform that runs significant parts of the business, and not only as a help desk tool, knowing who is signing in matters a great deal.

The change applies to internal users, meaning those without the external role, who sign in with local or LDAP credentials. External users, such as customers raising tickets, are not covered yet, although expansion to them is possible, particularly for organizations like health systems where outside users view sensitive records.

What Changes and When

After the upgrade, internal users have a 30-day window following their first login to set up MFA, during which they are warned but can still sign in normally. Setup becomes mandatory after the 90-day period. Organizations should expect many people to wait until the last day to act.

Customers that already use single sign-on with MFA at the identity provider do not need the additional MFA that ServiceNow is introducing. Single sign-on and multi-factor authentication belong together: MFA protects entry to the single sign-on environment, and the user then moves efficiently between applications. The change mainly catches the exceptions, such as backdoor or emergency administrator accounts kept for when SSO is down, test users, and organizations that still log in with LDAP credentials instead of SSO.

Why MFA Matters and Which Methods to Use

Credentials can be lost, stolen, intercepted, or mistyped into the wrong system, and passwords are still written on sticky notes and reused. A second factor confirms that the person signing in is who they claim to be. Research cited in the article suggests MFA can cut unauthorized access by up to 99 percent.

ServiceNow supports several methods. Passkeys, authenticator apps such as Google Authenticator and Microsoft Authenticator, hardware security keys such as YubiKey, and biometric options such as Face ID, Touch ID, and Windows Hello are the recommended choices. Email and text message one-time passwords are the least secure because they can be intercepted, and security experts advise against relying on them. Biometrics tie the second factor to a specific device, so teams should consider how people actually work, including from mobile devices and virtual desktops.

How to Prepare

The advice is to start now and not wait for Yokohama. Review current authentication practices, enable MFA for administrators and other high-privilege users first, and teach users how to set it up. Roll it out in phases so that problems can be found before enforcement, and integrate with single sign-on where possible, since that improves both security and convenience.

Because the 30-day window already gives people time, organizations can use it to get users familiar with the process, or move faster if the security team prefers. Disabling the requirement is technically possible but not recommended, since exceptions to good policy are how breaches happen.

Security Across the Platform

The change reflects how ServiceNow is being used. As the platform spreads beyond IT service management into customer, HR, and other business data, protecting access becomes a larger concern, and it is likely that enforcement will reach external users in the future.

Many organizations, especially in the mid-market, may not be ready, and some may not have single sign-on connected at all. For them, the work includes identity, security, and platform upgrades together. Organizations with a ServiceNow instance should confirm now which accounts sign in without SSO and plan for them before the release arrives.

fr_CAFrench