I have been dealing with OneLogin Customer Identity for around one and a half years. The major use case for identity management includes a multifactor authentication module and identity management for both internal and external CIAM (Customer Identity Management). Since it deals with financial and banking, it is crucial to identify the customer accessing core banking and mobile banking, as well as managing internal identities such as privileged access management and employee-to-employee management.
The biggest benefit of OneLogin Customer Identity for cybersecurity in a banking environment is the ability to manage many virtual machines, servers, and applications that require different credentials and privileges by using single sign-on, which automates the process. It can be challenging to remember every application's password, so managing access centrally with single sign-on and multifactor authentication is recommended for both financial institution customers and internal employees.
Furthermore, identity access management encompasses more than just credentials and privileges; it includes user identity, behavior, and characteristics, driven by machine learning, and is increasingly required in my country, Ethiopia.
Passwordless login may improve user satisfaction and security in general by functioning in a manner similar to single sign-on, as it allows users to log in using their email account to access LinkedIn and other social media in a similar fashion.
Analytics is valuable in OneLogin to optimize customer identity strategy by characterizing user behavior and characteristics for security posture. It helps identify unusual activities or deviations from normal behavior, enabling actions such as blocking access or sending notifications. Each user has unique characteristics, making identity management encompass more than just a password and username.
I see areas for improvement with OneLogin as most clients require a market reference or evaluator report, such as a Gartner report, to be convinced to use a new product. Many vendors lack clear documentation or site references. Clarity in documentation, similar to that with Thales and Fortinet, simplifies our job and helps us convince clients by providing links to credible sources.
There may be latency issues with OneLogin Customer Identity, as most of these security products are virtual and software-based. Latency and performance depend on the physical server, and fulfilling vendor-recommended resource requirements will ensure functionality; thus, if those requirements are met, there should be no issues.
I have been in the domain of identity management for more than one and a half years, with a strong focus on cybersecurity products, not limited to OneLogin Customer Identity.
I see no limitations regarding scalability with OneLogin Customer Identity.
I am not certain about ROI related to OneLogin Customer Identity, but it is vital to protect financial institutions' resources and core banking, which I consider a significant ROI. Protecting these assets is crucial, especially for financial institutions, to mitigate risks.
Compared with CyberArk, I would say OneLogin Customer Identity is affordable. Comparing OneLogin Customer Identity with CyberArk technically, I think CyberArk is better; I have had CyberArk for around two years or more, and I know of two or three customers in Ethiopian financial institutions using CyberArk Identity Access Management. According to Gartner, CyberArk is superior, but we are also competitive with OneLogin Customer Identity.
I have worked in presales and deployment in my country, Ethiopia, specifically with load balancers. I have been involved in presales and deployment with the F5 load balancer and Radware load balancer.
For the F5 load balancer in presales, I have been involved with LTM (Local Traffic Manager) and ASM (Advanced Application Firewall) for the WAF in a single appliance, which integrates WAF and load balancer in a single appliance. In deployment after-sales, I have worked with the basic load balancer only, specifically not for the WAF; however, in terms of WAF deployment, I have experience in FortiWAF deployment, presales, and deployment, while for load balancer, I have worked with Radware ADC load balancer and F5 LTM.
I do work with F5 Silverline Managed Services for firewall and Web Application Firewall. I do not work with F5 Distributed Cloud Services, as most of our customers' current need is on-premises products and solutions.
I do not work with NGINX products such as NGINX App Protect or NGINX Ingress Controller. I have experience with LTM, WAF, and BIG-IQ, the central manager.
For other products regarding identity management, I have been involved with CyberArk in presales only. For CyberArk, I work only with Identity Access Management. I do not work with CyberArk IGA powered by Zilla, as CyberArk's offerings are on-premises.
For Fortinet products, I am involved with Fortinet WAF, specifically on-premises and the physical appliance. For Fortinet AppSec, the application monitoring is a cloud-based software as a service, and as I highlighted earlier, most of my clients, such as financial institutions and banks, need on-premises solutions; thus, for the majority of the vendors, I have been involved in the on-premises solutions.
For API capability, I think this is common and a must for the majority of the vendors, as API is essential for integration; for instance, in identity management, integrating with SIEM to centralize logs is crucial for security management, allowing security operators to analyze logs for attacks or activities. API integration with third-party applications is vital; the customer typically handles third-party API sections, while we manage our product integration using vendor support procedures.
For the centralized management console, I note that in terms of deployment, if the IAM application, specifically OneLogin Customer Identity, is deployed in a main data center, DR, and various servers as high availability in a multi-deployment architecture, central management is indispensable. It allows management of configurations and operations centrally from one machine instead of logging into multiple instances.
Regarding OneLogin Customer Identity, for deployment options and license comparisons with other vendors, I am involved in the presales; if we win an opportunity, we will deploy together with vendors. After deployment, I will assess the ease of deployment, such as for Fortinet products where I have been involved with SIEM, next-generation firewall, and WAF along with F5 and Radware load balancers. For OneLogin Customer Identity specifically, it is still in progress, and I will provide updates once I am involved in the deployment.
My overall review rating for OneLogin Customer Identity is 8 out of 10.