What is our primary use case?
I am familiar with One Identity Safeguard and am also evaluating it for the organization.
For our primary use case for evaluating One Identity Safeguard, we aim to strengthen privileged access management across our environment. Currently, we are looking to improve how we control, monitor, and secure access to critical systems, especially for admin and high-privilege accounts. Additionally, as our infrastructure is a mix of on-premises and cloud, we need a solution that can provide centralized visibility and control across the environment. One Identity Safeguard aligns well with that need while also helping us streamline access workflows and improve audit readiness.
A good example of a scenario where One Identity Safeguard would really help my team is managing third-party vendor access. When external vendors need access to our critical servers for maintenance or troubleshooting, it often involves sharing credentials or giving standing access, which increases risk. With One Identity Safeguard, we could provide temporary, just-in-time access without exposing actual passwords. The vendor would request access, get approval, and then log in through One Identity Safeguard. Their entire session would be monitored and recorded. This helps us in multiple ways: no credential sharing, full visibility of what actions were performed, and an audit trail for compliance. Once the task is done, access is also automatically revoked. In this scenario, One Identity Safeguard directly reduces security risk while also making the process more controlled and compliant.
There is one important scenario related to internal privileged user management that I would like to add about my use case for One Identity Safeguard. For example, our system administrators currently have standing access to central servers. With One Identity Safeguard, we can shift to a just-in-time access model where admin rights are granted only when needed and for a limited time. This significantly reduces the risk of misuse or accidental changes. Another scenario would be audit and compliance. During audits, it is often challenging to provide clear evidence of who accessed what and what actions were performed. One Identity Safeguard helps by maintaining session recordings and detailed logs, making audits much smoother and faster.
What is most valuable?
In my opinion, the best features of One Identity Safeguard are the ones that directly improve both security and operational control. First, privileged session monitoring and recording stand out. One Identity Safeguard can capture and replay entire sessions with searchable logs, even down to the commands and screen activity. This is extremely useful for audits and incident investigations. Second would be secure password vaulting with automated rotation, which is a big advantage. It eliminates manual credential handling and reduces the risk of password exposure while enforcing strong security policies. Another key feature is real-time monitoring and threat detection. One Identity Safeguard can detect suspicious behavior during a session and even block unsafe actions, which adds a proactive security layer rather than just reactive logging. Finally, centralized privileged access governance is an essential feature. Bringing password management, session control, and analytics into a single platform makes it much easier to manage hybrid environments effectively.
Session monitoring and recording, even from demos and industry feedback, has the biggest impact on audits in terms of clarity and speed. Instead of relying only on logs or user statements, with One Identity Safeguard, I can actually replay a full session, see exactly what commands were run, what changes were made, and in what sequence. During an audit or investigation, instead of spending hours correlating logs, my team can directly pull the session recording as evidence. It reduces ambiguity, speeds up root cause analysis, and makes compliance reporting much stronger and more defensible. For example, if there is any suspected misconfiguration or data change, I do not have to guess; I can literally watch what happened.
For day-to-day operations, automated password rotation in One Identity Safeguard shifts us from a manual, reactive process to a fully automated, policy-driven approach. Today, IT teams often spend time resetting privileged passwords, handling access requests, and responding to potential credential exposure. With automation in place, most of the effort is eliminated. Passwords are rotated automatically after each use or on a scheduled basis, so there is no need for frequent manual resets. In fact, it does not just reduce how often we reset passwords; it removes the need for manual resets almost entirely. In terms of workload, this means fewer support tickets related to password issues, less coordination between teams for credential sharing, and reduced human error. The IT team can shift focus from routine tasks to more strategic work like security improvements and system optimization. One important operational change is that users no longer handle actual credentials. They request access, get approved, and One Identity Safeguard manages everything in the background. That is a big shift in thinking, but it slightly improves security.
What needs improvement?
The feature I think is a bit underrated in One Identity Safeguard is the approval workflow and access request system. It might sound basic, but having a structured, policy-based approval process really improves governance. It ensures that every privileged access is justified, approved, and tracked, which is especially useful in large teams where accountability can get blurred. Another underrated aspect is integration flexibility. One Identity Safeguard can integrate with directories, SIM tools, and hybrid environments, making it easier to fit into existing infrastructure rather than focusing on a complete overhaul. If I had to point out something that could be improved or is sometimes seen as missing, it would be user experience or UI. Some users feel it could be more intuitive, especially for non-technical users. Initially, deployment complexity, as with many PAM solutions, means setup and fine-tuning policies can take time. Advanced analytics depth is another area where, while good, some organizations compare it to competitors that offer more mature, AI-driven insights. Overall, One Identity Safeguard is very strong in core PAM capabilities such as session control and credential security, but there is room to improve usability and advanced analytics.
One area where the UI in One Identity Safeguard could improve is navigation and ease of use, especially for first-time or non-technical users. For example, when a user wants to request access to a resource, the process can feel a bit layered. Users may need to navigate through multiple menus to find the right asset or account. A more guided, simplified request flow, such as a single dashboard with request access front and center, would make it more intuitive. Another example is session management and monitoring views. While the data is very powerful, the interface can sometimes feel dense. There is a lot of information on screen. For someone who just wants to quickly check activity sessions, review a recording, or identify risk behavior, it could benefit from a more clean dashboard-style layout with clear visuals highlighting instead of heavy tables. Also, in policy configuration, setting up rules for access or password rotation can be a bit complex. It often requires understanding multiple parameters and dependencies. A more wizard-based setup or user-friendly policy builder would make it easier, especially for teams that are not deeply specialized in PAM.
While One Identity Safeguard is strong in core PAM capabilities, there are a few areas where it could be improved in the future. One area is deeper integration, especially with modern cloud-native and DevOps tools. While it integrates well with traditional infrastructure, tighter, more seamless integration with platforms such as CI or CD pipelines or container environments could make it even more relevant for evolving architecture. Another improvement could be in advanced analytics and AI-driven insights. The current monitoring and alerting are solid, but having behavior analytics with more predictive capabilities, such as identifying malicious behaviors before they become risks, would add a strong proactive security layer.
From a documentation perspective, it would be helpful if there were more real-world use cases and step-by-step implementation examples. Sometimes the current documentation feels a bit too feature-focused, and adding practical scenarios would make onboarding easier. Regarding training, more structured learning paths or short guided tutorials for different user levels, from beginners to advanced, would be helpful.
For how long have I used the solution?
I have been using One Identity Safeguard for a year now.
What do I think about the stability of the solution?
Overall, we have seen good stability and strong scalability with One Identity Safeguard, especially after the initial tuning phase. Once the system was properly deployed and integrated, it has been very reliable in day-to-day operations. We have not experienced any major unplanned outages in production. Most issues, when they occurred, were related to initial configuration changes or network level dependency. In terms of downtime, we only see planned downtime during upgrades or maintenance windows. Even those were manageable because we schedule them during off-peak hours. The system supports clustering or redundant configuration, so access can often continue through other nodes depending on the setup. Overall, downtime impact has been minimal.
What do I think about the scalability of the solution?
One Identity Safeguard has met our needs well as the environment has grown. As we added more privileged accounts, systems, and user groups, we were able to scale by expanding the virtual appliance footprint and clustering. The platform is designed to support horizontal scaling, so adding capacity is relatively straightforward without redesigning the entire architecture.
How are customer service and support?
I have had to reach out to One Identity customer support a few times, mainly during the initial development phase or for a couple of integration-related queries. Overall, the experience has been decent to good, but it varies depending on the type of issue. For critical or well-defined technical issues, especially around configuration or known product behavior, the support team has been quite effective. They have provided clear guidance and documentation references, and in some cases, helped us resolve issues within a reasonable timeframe. Overall, the responsiveness from the technical side has been generally good, and the knowledge of the support team has been useful. Resolution time has been good for common use issues but slow for complex or custom scenarios, and handling escalations has been manageable.
Which solution did I use previously and why did I switch?
Previously, we used a more basic PAM approach built around a legacy vaulting solution combined with manual approval workflows, ticket-based access, and shared admin controls. We switched mainly because of limited access visibility and auditing, too much manual effort, weak hybrid or cloud integration, especially as we moved more workloads to Azure, and scaling challenges that arose as the number of privileged accounts and systems increased.
How was the initial setup?
The initial deployment of One Identity Safeguard on virtual appliances took roughly six to eight weeks end-to-end, including planning, setup, integration, and user rollout. The process was done in phases. First, we set up the core One Identity Safeguard appliance in a controlled environment and integrated it with our identity sources such as Active Directory. After that, we configured privileged accounts, session policies, and audit requirements. We also ran a pilot with a small group of administrators to validate session recording, access workflows, and reporting before going wider. In terms of disruption, it was minimal for most privileged users, but not completely zero. During the pilot phase, there were some adjustments needed because users had to get used to logging in through One Identity Safeguard gateways instead of directly accessing the system. Overall, the phased rollout approach helped reduce disruption significantly, and most users adapted quickly after the initial onboarding period.
What about the implementation team?
For the administration team, we needed more structured training, roughly a few days of focused hands-on sessions, plus some internal sandboxing practice. This covered things such as configuring safe rules, policies, integration with Active Directory, and audit logs. The learning curve is a bit steep initially because One Identity Safeguard has a lot of depth, especially around policy design and access control models. For end users, the training was relatively light. Most of it was around how to access systems through One Identity Safeguard gateways, how session recording works, and what changes in other login workflows. A short one to two-hour walkthrough session plus quick reference guides were usually enough for them to get comfortable with it.
What was our ROI?
Overall, we have seen a clear ROI from One Identity Safeguard, mostly in the form of time savings, reduced manual effort, and improved audit efficiency rather than just direct headcount reduction. In terms of time saved, one of the biggest gains is the privileged access workflow, such as password rotation and session approvals. What used to require manual coordination or admin intervention is now largely automated. This has noticeably reduced day-to-day operational overhead for the infrastructure team, amounting to multiple FTE days per week after deployment. From a security and compliance standpoint, the ROI is more evident. Session recording and audit trails have reduced the time spent preparing for audits and investigating incidents. Instead of manually reconstructing activity, everything is already logged and searchable, which has improved response time during internal reviews.
What's my experience with pricing, setup cost, and licensing?
We evaluated the pricing and setup cost as part of the overall deployment, and as with most enterprise PAM solutions, it is not cheap, but it is fairly aligned with what you get in terms of capability and security coverage. From a licensing perspective, One Identity Safeguard follows a custom enterprise model, typically based on factors such as the number of privileged accounts, users, and the modules you deploy. It is negotiated based on scope and scale rather than a simple per-user licensing. In our case, the initial setup cost was higher than expected, mainly because it was not just a software license; it included infrastructure planning, virtual appliance development, integration work, and security configuration.
Which other solutions did I evaluate?
Before choosing One Identity Safeguard, we did evaluate a few other enterprise PAM solutions. The main ones were CyberArk Privileged Access Manager and BeyondTrust Privileged Access Manager. We compared them mainly on session recording and monitoring capabilities, ease of deployment in hybrid environments, and integration with Active Directory. One Identity Safeguard stood out because it offered a strong balance of deep session monitoring and solid integration with our identity stack, along with easier appliance-based development. It aligned well with our internal compliance and auditing requirements without adding too much operational complexity. Overall, the decision came down to fit with our hybrid infrastructure, ease of control, scalability, and compliance readiness rather than just feature comparison.
What other advice do I have?
Even during the evaluation phase, One Identity Safeguard has shown clear positive impacts across key areas in my organization. From a security posture perspective, the biggest improvement is the elimination of direct credential exposure. Instead of sharing admin passwords, access is brokered through One Identity Safeguard, which significantly reduces the risk of credential misuse or leakage. In terms of audit readiness, we have seen a big improvement in visibility. The ability to track sessions and maintain detailed logs means we can quickly answer questions such as who accessed what, when, and what actions were performed. Even in a pilot, this level of transparency makes audits much more straightforward. On the operational efficiency side, processes such as access requests and approvals have become more structured instead of informal or manual coordination. Everything follows a defined workflow, which reduces delays and confusion.
Since we are still in the evaluating or pilot phase of One Identity Safeguard, we do not have long-term production metrics yet, but we have observed some early indicators and rough estimates. For example, in terms of operational efficiency, we have seen a noticeable drop of roughly thirty to forty percent in password-related support requests within the pilot group, mainly because users no longer need to request or manage credentials manually. From an audit perspective, the time required to gather access logs and evidence has reduced significantly. Tasks that earlier took hours, such as correlating logs, can now be done in minutes using session recordings. We estimate around fifty to sixty percent reduction in audit preparation time for privileged access reviews. On the security side, while it is early to quantify incidents, we have effectively reduced the risk surface by eliminating shared credentials in the pilot scope. That alone is a major improvement, even if it is not directly measurable yet. Earlier estimates show thirty to forty percent fewer password-related tickets and fifty percent faster audit preparation, along with reducing risk and eliminating shared credentials.
The integration of One Identity Safeguard has had a clear positive impact on both security and operational efficiency. From a security perspective, the most noticeable improvement is tighter controls over privileged access across systems. For example, before One Identity Safeguard, some privileged accounts, especially service accounts used in automation, had unrestricted access. Just-in-time access and session recording have significantly improved visibility. Now, even when an automation job or admin session runs, we can trace exactly what was accessed and when.
My advice for others looking into using One Identity Safeguard is that it offers a positive ROI overall, but it is mostly reflected in time savings, operational efficiency, and risk reduction rather than a single direct cost metric. In practical terms, the biggest measurable benefit has been time saved for IT and security teams. Tasks such as privileged access approvals, password rotation, and session audits are now largely automated or centralized. Another key area is auditing and compliance efficiency. Before One Identity Safeguard, preparing for audits required collecting logs from multiple systems and manually correlating activity. Now, session records and searchable audit trails make this process faster, saving a significant amount of effort during compliance cycles. Overall, the ROI is very real, but it shows more in time saved, reduced risk, and smoother operation rather than a direct headcount or cost-cutting figure.
Before wrapping up, I would say that my overall experience with One Identity Safeguard has been strong and reliable for our needs, especially for privileged access control in a hybrid environment. What stands out most is the visibility and control it brings to privileged activity, having full session recording and centralized access workflows. It has also helped us move away from fragmented manual processes towards a more structured and governed access model, which becomes very important as the environment scales. Overall, it has been a solid investment from both a security and operational standpoint. I would rate my overall experience with One Identity Safeguard as a nine out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure