SURFsecureID: the new name of SURFconext Strong Authentication
28 MAR 2018
The name of SURFconext Strong Authentication is set to change to SURFsecureID. The new name will be introduced over the coming period. This name reflects the modifications made to the service: it can be used separately from SURFconext as required, and the focus is on security.
Not just for SURFconext services
SURFsecureID helps make access to online services even more secure with two-factor authentication. As of last year, it has been possible to connect SURFconext Strong Authentication to services that are not connected to SURFconext. For example, this service can now function with a central (authentication) facility such as ADFS, F5 or Citrix. The name has now been changed to SURFsecureID to avoid any confusion.
Make access more secure
SURFsecureID helps make access to online services even more secure with two-factor authentication: the user logs in with their username/password along with a second factor such as a SMS text message or USB key. This is primarily of interest for services that handle sensitive data, including eHRM, grade administration systems, student information systems and applications involving patent-sensitive research data or privacy-sensitive patient information. To cover the security risks, these services require stronger forms of login than just a username/password combination. This is possible with SURFsecureID.
Different services, a single token
Institutions can use SURFsecureID to implement a second factor check when logging in to different services. This can be set up for on-premise services and services behind ADFS, as well as for services already connected to SURFconext. Users can use the same token for all these services (SMS text message, tiqr or YubiKey).