OneLogin is primarily used for privileged access to applications. OneLogin enables access to applications without needing to use a single sign-on, as it connects seamlessly between systems.
For the end user, the experience with OneLogin is transparent. Previously, users had to log in to Office and then log in again to another application such as Monday. When synchronizing or running OneLogin together with those applications, the user only needs to be redirected to OneLogin by the application itself, and with that single sign-on they can then connect to other applications.
OneLogin offers the ability to update role permissions, which makes the task easier when disabling a user or changing their role or lowering their privileges. This is straightforward to manage from the same console.
OneLogin offers dynamic MFA, where the platform can decide, based on user behavior, whether or not to ask for MFA. This helps significantly. Additionally, intelligent flows, known as Smart Flows, help create highly customized authentication flows all from within OneLogin itself.
Another relevant feature of OneLogin is role assignment, which allows us not only to create the user in the final application, but also for OneLogin to assign the roles, groups, and permissions of those apps, attributed or associated with Active Directory.
OneLogin helps improve security posture. We base ourselves on ISO 27001, and they require us to have controls for secure access control, which OneLogin has helped us with. Another benefit is user productivity, because users do not have to enter multiple passwords in different applications to access them. One password is sufficient, and if OneLogin detects that the user is benign or not malicious, it makes it easier for them to access the other applications. There was also a reduction in support tickets. Although initially there were quite a few as a result of the tool's implementation, the reduction became clear as users fully learned how to use the tool, so there are no issues from that point of view.
OneLogin could benefit from additional dynamic security enhancement. The solution itself can decide whether or not to require MFA from users based on the user's behavior, where they are connecting from, their IP, what device, and what time. It allows us to identify and automatically trigger an MFA flow or simply deny access due to the dynamic risk that the user may present.
In terms of OneLogin, integrations or the integration list could be improved. There are applications that perhaps do not use the REST API, so providing the ease of being able to integrate more applications would be beneficial.
OneLogin has been used for approximately a year and a half.
The idea of implementing OneLogin was also to keep users under control and also to protect the applications they access with OneLogin by protecting them from the identity side. Though exact figures are not available, this impact can be described as positive for our organization.