Insights & updates from our experts
To make multi-factor authentication (MFA) a little easier for users, Xurrent now supports the use of hardware security keys, such as the ones provided by Yubico, Thetis and FEITIAN. A hardware security key does not rely on the user receiving a code in a text message or email so this code can be used to confirm the user’s identity. Instead, a physical key that the user owns is used as the second factor in the authentication process. Not having to wait for a code and not having to entering this code makes the whole authentication process much more convenient.
In the Xurrent Specialist Interface, users can add a security key by clicking on their picture or initials in the upper right of the browser window and selecting the ‘My Profile’ option. They can then open the ‘Access & Security’ section. That is where, if multi-factor authentication has not yet been activated, they can click on the option ‘Set up 2FA in Xurrent’.

Apart from the option to set up two-factor authentication with an authentication app (like Authy or Google Authenticator), users now see the option to add a security key.

When the option to add a security key is selected, users can give their security key a name.

After pressing the Register button, Xurrent will guide them through the last steps.

Users then have the ability to download or copy a set of recovery codes before 2FA is actually activated.
After a security key has been registered, additional keys can be added, for the Xurrent App on the user’s smartphone.

The built-in TouchID sensor on MacBooks can also be added as a security key. It is even possible to use both security keys and an authentication app.
All in all, Xurrent’s support for hardware security keys gives users a lot more flexibility when they are making use of two-factor authentication to protect their Xurrent access.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)


.webp)











