ServiceNow supports local logins with MFA, however most organisations prefer Single Sign-On (SSO) for its security and convenience, with benefits including:
Centralised Authentication – minimises the number of passwords/passphrases that a user needs to keep track of, reducing the risk of weak or re-used passwords. It also makes it easier to enforce password/passphrase standards and reduces effort for on-boarding and off-boarding users.
Auditability and Compliance – particularly in high-governance environments, this will enhance an organisation’s ability to audit access to systems.
Reduced Attack Surface – by locking out local sign-on capabilities, the potential entry points for attack are minimised, therefore reducing the risk of unauthorised access, credential theft and other threats associated with managing local accounts.
Adaptive Authentication takes this further by allowing or denying access based on factors such as user role, device type, or login location. For example, you might enforce MFA for admins but not for standard users already challenged by your identity provider (IdP).
Regardless of your setup, it important to always maintain strong password policies, regularly review inactive or departed users, and have processes in place to ensure that access to sensitive data is always minimised. If you are using local accounts, you can configure a password exclusion list in ServiceNow to prevent users from using known bad passwords and even better, ServiceNow does support the use of Passkeys to avoid using passwords at all and make local accounts a little more secure.
If you’re subscribed to ServiceNow Vault, you can enable Zero Trust Access which allows for additional conditions and actions. For example, if your IdP performs a security posture assessment of the user’s device, those attributes can be passed across to ServiceNow. You can also leverage Continuous Authentication to enforce step-up authentication or re-authentication based on what data the user is accessing or what tasks they are performing.