One Identity Defender Reviews

My main use for One Identity Defender is monitoring and securing privileged accounts and detecting any unusual or risky behavior in real time. For example, on a day-to-day basis, I use it to track login activities of admin users. If there is any abnormal behavior, such as a login from an unusual location, odd timing, or multiple failed attempts, the system alerts me immediately.

One of the best things about One Identity Defender is the advanced threat detection and user behavior analytics. What stands out to me the most is behavior-based anomaly detection. Instead of relying only on predefined rules, it builds a baseline of normal user behaviors and detects deviations using machine learning. This helps identify even unknown or insider threats. Another significant feature is real-time monitoring and alerting. It continuously tracks privileged sessions and generates alerts instantly when any suspicious activity is detected, which is critical for quick response.

In addition to monitoring privileged access, One Identity Defender integrates well with other security tools in our environments. For example, it works alongside our SIEM solutions, where the logs and alerts generated are forwarded to centralized monitoring and correlation. This helps us obtain a broader view of security events across the organization.

We have seen some clear, measurable improvements after implementing One Identity Defender. For example, our incident response time improved by thirty to forty percent because alerts are generated in real time and include enough context to act quickly without deep manual investigations. We also notice a reduction in false positives by roughly twenty to twenty-five percent.

While One Identity Defender is a strong solution overall, there are a few areas where I feel it could be improved. One area is the user interface and dashboard customization. Although it is functional, making it more modern and allowing deeper customization would improve the user experience, especially for quick monitoring. Another improvement could be in reporting flexibility. While it provides good reports, having more custom report building options and easier export features would be helpful for different compliance and manageability needs.

From an integration perspective, while One Identity Defender works well with core systems, having more out-of-the-box integrations with modern cloud services and SaaS platforms would reduce the need for custom configuration. In terms of support, the overall support is good, but faster response times for critical issues and more detailed troubleshooting documentation would help teams resolve problems more efficiently.

I have been using One Identity Defender for around one to two years.

Overall, One Identity Defender has been quite stable and reliable in our environment. We have not experienced any major downtime affecting business operations. Most of the time, the system runs smoothly and handles authentication and monitoring without issues.

One Identity Defender is generally quite scalable and can handle organizational growth effectively. One of the key reasons is that it leverages Active Directory as its core, which already has built-in scalability. As the number of users grows, it can scale along with the existing identity infrastructure without requiring a completely separate system.

Overall, our experience with customer support for One Identity Defender has been positive. For most standard issues and inquiries, the support team is responsive and knowledgeable, and we have been able to resolve problems within a reasonable time frame. They also provide access to a detailed support portal and knowledgeable base, which helps in troubleshooting common issues without always needing to raise a ticket.

I would rate the customer support for One Identity Defender an eight out of ten. The support team is generally positive, responsive, and knowledgeable and helpful, especially for standard issues. The only reason it is not a ten is because response time can sometimes be slower for complex or escalated cases.

Before implementing One Identity Defender, we were using a combination of basic access control tools and native logging solutions.

We have definitely seen a positive ROI from using One Identity Defender. For example, in terms of time saving, our security team now spends about twenty to thirty percent less time on manual log analytics and investigations because the system automatically highlights high-risk activities. From an operational efficiency perspective, we did not need to increase team size despite growing infrastructure as the tool helps us handle more security events with the same team.

Our experience with pricing and licensing for One Identity Defender has been generally positive. In terms of pricing, it is on the higher side compared to basic security tools, but it is justified because of its advanced features such as behavioral analytics, real-time monitoring, and privileged access protection. For setup cost, there was an initial investment involved, mainly around deployment, configuration, and integration with existing systems. However, since we implemented it in a hybrid environment, we were able to optimize some infrastructure costs. Regarding licensing, it is quite flexible and typically based on users or tokens, which allows scaling according to organizational needs.

Before finalizing One Identity Defender, we evaluated a few other solutions to compare features and fit for our environment. Some of the options we looked at included CyberArk Privilege Access Manager, BeyondTrust Privilege Access Management, and Delinea Secret Server.

My advice to anyone considering One Identity Defender would be to first clearly define your security and privileged access requirements. It is a powerful tool, so to get the most value, you should plan the deployment carefully, properly configure policies and user roles, and integrate it with your existing systems. Initial training for your team is crucial so they can fully utilize its features.

Overall, One Identity Defender is a reliable and effective solution for securing privileged access and improving visibility into user activities. One thing I would highlight is that its real value comes when it is properly implemented and integrated with the existing security ecosystem. I would rate this product nine out of ten overall.

Hybrid Cloud

Microsoft Azure

Our main use case for One Identity Defender is enforcing least privilege and controlling application access on endpoints. A common day-to-day example is when a user needs to run an application that typically requires admin rights. Instead of giving full administrative access, we allow controlled privilege elevation for that specific application through defined policies so the task gets completed without exposing the systems to unnecessary risks.

At the same time, we monitor and log such activities to maintain security and compliance.

In addition to the core use case, One Identity Defender also plays a key role in standardizing endpoint security across our organization by ensuring consistent policy enforcement for all users and devices. This helps us eliminate the need for permanent admin rights while still allowing flexibility through controlled privilege elevation. One Identity Defender also supports application control by allowing only trusted software to run, which reduces the risk of malware or unauthorized tools. Overall, it fits seamlessly into our workflow by balancing security with user productivity without creating unnecessary restrictions.

The best features of One Identity Defender are its privilege elevation control, application whitelisting, and centralized policy management. The feature that stands out the most is its ability to enforce least privilege while still allowing users to run necessary applications without granting full admin rights because this directly reduces security risk while maintaining productivity.

In daily work, it makes things easier by eliminating the need for constant admin intervention for routine tasks while also ensuring all actions are controlled, monitored, and aligned with security policies, which significantly improves both efficiency and overall endpoint security.

One Identity Defender has positively impacted our organization by improving productivity, speeding up communications, and saving a significant amount of time for the team. We have also noticed faster turnaround in daily work, such as preparing reports and understanding new tools.

With One Identity Defender, we have achieved around 40 to 50% time saving in maintaining privilege access tasks. Activities like password rotation and access approval are automated, and audit preparation time has reduced significantly since all session recordings and logs are readily available. This improves overall productivity and reduces manual efforts for the IT team.

One Identity Defender can be improved by simplifying the user interface and making navigation more intuitive, especially for new administrators who may find the initial setup and policy configuration somewhat complex. There is also room to enhance reporting and dashboard customization to provide clear, real-time insights without extra efforts. Improving integration capabilities with more third-party tools and cloud platforms would make it more flexible in modern environments.

Overall, while it is a strong solution, making it more user-friendly and easier to configure would significantly enhance the overall experience.

In addition to the earlier points, one improvement we would like to see in One Identity Defender is more detailed and user-friendly documentation along with in-product guidance. This would make it easier for new users to understand advanced configuration and troubleshoot issues without relying heavily on support. While customer support is generally helpful, faster response time for complex queries would further improve the experience. Enhancing performance for large-scale environments along with more flexible policy customization options would make the solution even more efficient and adaptable to different organizational needs.

I have been using One Identity Defender for around one to two years in our organization.

One Identity Defender has been quite stable in our organization. We have not experienced any major downtime or critical reliability issues so far. There have been occasional minor issues during updates or maintenance windows, but overall, the platform has been reliable and consistent in day-to-day operations. As our organization expands, it has been able to accommodate additional users, systems, and data without significant performance impact, making it suitable for growing environments.

Customer support for One Identity Defender has been generally good. Our experience with their support team has been positive as they are responsive and technically knowledgeable. For critical issues, the turnaround time is quite fast, providing clear guidance for resolution. While for less urgent inquiries, response times can be slightly slower, overall, the support quality is reliable and helpful. I would rate the customer support of One Identity Defender around eight out of 10, considering their responsiveness, technical expertise, and overall support experience.

Before switching to One Identity Defender, we were using a mix of traditional security tools and manual processes for identity and access management. However, those solutions lacked centralized visibility and real-time threat detection and required significant manual effort. We decided to switch to One Identity Defender because it offers a more integrated and automated approach with better security insights.

Our experience with pricing, setup cost, and licensing for One Identity Defender has been fairly straightforward. Its licensing is typically based on the number of users or endpoints, which makes it scalable and predictable. While the initial setup and implementation required some investment in terms of time and cost, it was manageable with vendor support. Although the overall pricing is on the higher side compared to basic solutions, it is generally considered cost-effective when looking at the security benefits and risk reduction it provides.

We have seen a clear return on investment with One Identity Defender as it has reduced manual IT effort by around 40 to 50% by eliminating the need to manage admin rights for users, ultimately decreasing security risks. It is generally considered cost-effective when looking at the security benefits and risk reduction it provides.

Before finalizing One Identity Defender, we evaluated a few other solutions in the market, such as Microsoft Defender for Identity, Okta Identity Cloud, and CyberArk Identity. Each of these had strong capabilities, especially in identity management and threat detection, but we found that One Identity Defender offered a better balance of integration, ease of management, and advanced threat visibility, which aligned more closely with our requirements.

My advice to anyone considering One Identity Defender would be to start with a clear understanding of your organization's identity security needs and existing infrastructure, making sure to plan the implementation properly, especially integration with current systems to get the most value from the platform. It is also helpful to involve your security and IT teams early in the process for smoother deployment. I recommend starting with a pilot phase to understand its features and fine-tune configuration before a full-scale rollout, as overall, it is a strong solution, but like any advanced security tool, its effectiveness depends on how well it is configured and aligned with your environment. I would rate this product an 8 out of 10.

Hybrid Cloud

Microsoft Azure

One Identity Defender strengthens identity and access security through MFA, helping us ensure that only authorized users can access critical systems, especially for privileged accounts, with a focus on remote access security by securing remote access with MFA. It adds an external, extra layer of security when users log in from outside the corporate network, with the primary purpose being securing privileged access. We use One Identity Defender to enforce MFA for admin and high-risk accounts to prevent unauthorized access.

In our environment, we use One Identity Defender, and a specific example of how we use it for privileged access and remote login is that whenever an admin user tries to log in to critical servers remotely, they must complete MFA, which helps us prevent unauthorized login attempts from unknown devices.

Overall, we use One Identity Defender daily to enforce multi-factor authentication and ensure secure access from both privileged and remote users, reflecting its importance in our day-to-day operations.

One Identity Defender offers multi-factor authentication to strengthen login security, especially for privileged and remote access users, alongside its integration with Active Directory, ensuring smooth operation with existing user identities. It also provides centralized administration, token-based authentication, and strong audit logs for tracking all login activities overall, helping to enforce secure access control and reduce the risk of unauthorized access.

We rely on centralized administration and strong audit logs daily, with centralized administration helping us manage users and policies from one place, saving time and reducing manual work. Audit logs help us track all authentication activities, allowing us to quickly review who accessed what and when.

One Identity Defender is quite easy to integrate with existing systems like Active Directory and other applications, which makes deployment smoother. It also supports flexible authentication methods, enabling us to adapt security based on risk level and user type. Overall, it improves security without adding much complexity for end-users.

One Identity Defender has positively impacted our organization by improving overall security through the addition of MFA, which reduces the risk of unauthorized access and makes user authentication more controlled and reliable.

One Identity Defender is a strong product, but there are a few areas where it can be improved. First, the user interface and reporting dashboards could be made more intuitive and customizable for faster analysis. Second, the integration with more modern cloud-native applications could be expanded to better support hybrid environments. Additionally, adding more advanced analytics or AI-based risk detection would help in identifying suspicious login patterns proactively. Overall, it is very effective, but these improvements could make it even more powerful and easier to use at scale.

Another area for improvement would be the support and deployment experience. While the product is stable, faster support response times and more detailed documentation would help during troubleshooting and upgrades. Additionally, deployment could be simplified in the future with more guided step options or automated configuration attempts, especially for large environments. This would reduce implementation effort and make onboarding quicker for new teams.

It has been a year since we started using One Identity Defender.

One Identity Defender is generally very stable in our environment. After implementation, we have not faced major downtime or authentication failures, and it runs reliably in the background while consistently enforcing multi-factor authentication from both privileged and remote access users.

One Identity Defender has shown good scalability in our environment, enabling us to scale it from a smaller user base to a much larger number of users without major changes to architecture. It integrates tightly with Active Directory and maintains excellent performance, continuing to handle increased authentication requests smoothly as we onboard more users and privilege accounts.

The customer support experience with One Identity Defender has generally been good. Whenever we raise tickets for configuration or integration issues, the support team is responsive and provides proper guidance to resolve the issue.

Previously we were using a more basic authentication approach, mainly Active Directory, password-based login, and limited or no MFA for privileged access. We switched to One Identity Defender because the earlier setup was not sufficient from a security standpoint, lacking strong MFA enforcement and increasing the risk of unauthorized access. There was also limited visibility and control over authentication events. With One Identity Defender, we strengthened security with MFA, improved control over privileged accounts, and gained better audit and monitoring capabilities.

Overall, the pricing and licensing for One Identity Defender is on the enterprise side, but it is justified by the security value it provides. It is typically based on our users or tokens, depending on the deployment model. From a setup cost perspective, there is some initial work involved in infrastructure setup and integration with Active Directory, but once configured, it is quite stable and does not require heavy ongoing maintenance.

We have seen a positive return on investment after implementing One Identity Defender, with one of the biggest benefits being the reduction in operational effort for the team, especially in handling password resets and access-related issues. Since MFA has reduced a lot of login failures and security incidents, the ROI is seen in reduced support effort, improved efficiency, and a stronger security posture rather than direct headcount reduction.

After implementing One Identity Defender, we noticed specific outcomes, such as fewer unauthorized access attempts getting through because MFA is enforced for all privileged and remote logins. It has also reduced dependency on manual password resets and improved control over user access.

Before selecting One Identity Defender, we were evaluating a few other multi-factor authentication and identity security solutions available in the market, including options such as Microsoft authentication based on MFA, Azure AD, RSA SecurID, and Duo Security.

My advice for others looking into using One Identity Defender would be first to clearly define your use case, especially whether you need MFA mainly for privileged access, remote users, or both, as this will help design the right policy structure from the beginning. Second, ensure proper planning for integration with existing identity systems like Active Directory, as that is key for smooth deployment and scalability. Finally, keep user training and communication in mind because user adoption is important for MFA success. I would rate this product an 8 out of 10.

On-premises

Other

The solution works very well.

The initial setup is pretty easy.

It is stable and pretty reliable in general.

We find that the product scales very well. 

Technical support is responsive.

The interface is good. 

It is compatible with other products. 

It has everything we need right now.

The login capabilities could be better.  

I've used the solution for three years. It's been a while at this point. 

The stability is very good. It is reliable and offers good performance. There are no bugs or glitches. It doesn't crash or freeze. 

It's easily scalable. We work with small, medium, and large size organizations and the solution works well for any of them.

Technical support is fine. The response time is great. If we need them to, they will scale all the way to development.

I have not worked with similar products.

The implementation process is straightforward. It's not complex. 

To start working with out-of-the-box scenarios, it'll take about maybe 30 minutes to set up. Most of it is waiting for the results to finish the stuff.

I do not deal with licensing and do not know what the exact pricing would be.

I'm a sales engineer for One Identity Safeguard. I'm a reseller.

If you decide to activate this solution, your infrastructure will be centered around flexibility.

I'd rate the solution ten out of ten.

Our primary use cases include functions such as role-based access control, user registration, and integration with other systems. 

We use it to improve the security of our web applications. Additionally, we utilize it for reviewing and safeguarding sensitive information.

We wanted to use it to secure our Windows system and Azure application logins. It also provides security for other web applications. Additionally, we use it for RBAC (Role-Based Access Control) to authenticate users before they log in to Azure or our servers. By adding more security, we aim to improve our overall security system.

We find it very helpful for multifactor authentication and other purposes. It has improved our overall security and usage.

We use it effectively with Safeguard and Windows Server. For Safeguard, it serves as a second-factor authentication when logging in to Safeguard for Privileged Password or Safeguard for Privileged session. The user enters their credentials and then receives a token on their observed soft token on Android or Total Connect Windows, which they can use. 

It's also used when a user needs to use RDP on a machine. After entering the password, they need to enter the Defender token. 

Moreover, it was easy to integrate these solutions. They work very well together. We haven't had any problems.

It's very fast, and it's easy to use because it's integrated with Active Directory. Any changes made are quickly reflected, and it doesn't require much storage space on the installed driver or any other system.

Maybe it could provide support for more web applications. It would be useful to focus on other web applications. 

For example, if an application needs to be installed on an iOS server and it's not, it can be used with another product like OneLogin, but not with One Identity Defender.

I have been using One Identity Defender for a year now.

One Identity Defender is very stable. Since it's related to Active Directory, as long as the server is functioning correctly and connected to Active Directory, it remains stable.

One Identity Defender is very scalable because it integrates with Active Directory. We just need to ensure we have enough licenses for the users or tokens required. So, there are no scalability issues.

The initial setup was very straightforward.

One Identity Defender needs to be installed on our server and integrated with Active Directory to manage users and groups directly. It also provides a self-service portal for quick user access.

It just works. Maybe some maintenance if there's a server failure. Before, we had only one Defender server, so we had to quickly solve any problems to ensure uninterrupted user logins. But now, we have another server as a secondary authentication service, which mitigates this issue. 

If any problems occur with the primary server, the secondary server continues to work, and users can log in properly.

I deployed the solution myself. It was very easy to use, and the administration guide covered most of the necessary use cases.

We are also reselling One Identity Defender, as with Safeguard. We have installed it in our company and for other users in different companies.

I have had a great experience with it, so I would rate it highly.

On-premises

We use One Identity Defender for network protection.

One Identity Defender has good network protection.

We have some clients that are wanting to protect their Apache web servers with One Identity Defender but all the research I have done says cannot be done. It can only be oriented to an IIS server. One Identity Defender should have more integration with more types of web servers. 

Here in Africa, most of the environments are still using UNIX. It might be because it would cost more to move to a Microsoft environment and that is why it is being avoided. However, some are using UNIX but One Identity Defender only supports SSH and an active directory environment. They should look into expanding their environment integration to incorporate all the Unix system services.

I have been using this solution for approximately one year.

One Identity Defender is stable. I have worked with Vasco previously and One Identity Defender is better.

The solution is scalable.

The technical support is good, but we receive a quick response. However, their knowledge and information are typically good.

I have previously used Vasco.

The installation is straightforward.

In attempting to have One Identity Defender work with the Apache web server I asked the users to use their active directory password to authenticate themselves as a user of Apache and it worked. However, using the password of the active directory is not a problem but using the OTP has been giving us difficulties. If they could fix this it would be perfect.

My advice to others is before implementing One Identity Defender, you have to know what environment you are using. You cannot implement One Identity Defender if there is no active directory (AD) environment, this is the only challenge. There are other solutions that can handle other environments but not this solution.

I rate One Identity Defender a seven out of ten.