Privileged access has become tightly controlled and audit trails now improve investigations
What is our primary use case?
One Identity Safeguard's main use case for us is securing and controlling privileged access to critical systems.
A common scenario with One Identity Safeguard is when a system administrator needs to access a production server for troubleshooting. Instead of logging in directly with a shared admin credential, the request is first routed through One Identity Safeguard for approval, which helps us with fine-grained control and accountability for high-risk administrative tasks.
What is most valuable?
The best features of One Identity Safeguard in my experience are its session recording and live monitoring capabilities, which give us visibility into what administrators are doing during privileged access.
Session recording in One Identity Safeguard has been especially useful for troubleshooting and audit purposes, adding a strong layer of accountability and making investigation much faster and more accurate.
The implementation of One Identity Safeguard has had a noticeably positive impact on our security posture and daily IT operations, helping us tighten security and gain operational visibility.
The positive outcomes from One Identity Safeguard have been quite clear for our team. From a security perspective, it has significantly reduced the risk of uncontrolled privileged access by enforcing approvals and session tracking, improving security visibility and operational efficiency at the same time.
For how long have I used the solution?
I have been using One Identity Safeguard for around two years now, and my experience with it so far has been exceptional and reliable.
What do I think about the stability of the solution?
One Identity Safeguard is very much stable in my experience.
What do I think about the scalability of the solution?
One Identity Safeguard's scalability is nice and it handles growth or increased users well.
How are customer service and support?
The customer support for One Identity Safeguard was good, and the process was smooth.
Which solution did I use previously and why did I switch?
We did not use any other solution before choosing One Identity Safeguard.
How was the initial setup?
The deployment of One Identity Safeguard in our environment took roughly a day's involvement.
The deployment of One Identity Safeguard had an initial adjustment phase for privileged users, but overall the transition was fairly smooth.
The training required to start using One Identity Safeguard was straightforward for both those who manage it and for end users.
Feedback from users regarding the usability and functionality of One Identity Safeguard was positive.
What was our ROI?
I have seen a return on investment by using One Identity Safeguard, which has reduced the time spent on managing privileged access and impacted the budget by reducing costs by an estimated 20 to 25 percent.
What's my experience with pricing, setup cost, and licensing?
The overall experience with pricing, setup cost, and licenses for One Identity Safeguard was positive.
Which other solutions did I evaluate?
We did not evaluate any other option before choosing One Identity Safeguard.
What other advice do I have?
For anyone considering One Identity Safeguard, I would suggest starting with a clear plan for what you want to achieve from a security and user access perspective before deployment, as a structured rollout approach makes the adoption much smoother and more effective. I have provided a review rating of 10 for One Identity Safeguard.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Privileged access has become controlled and auditable while password rotation runs automatically
What is our primary use case?
One Identity Safeguard's main use case in our organization is to manage and secure privileged access across our environment, primarily controlling administration access to critical systems like servers, databases, and network devices. It helps us enforce secure password management and provides session monitoring, allowing us to track what privileged users are doing in real time or review it later for auditing purposes. In day-to-day operations, we use it to grant temporary access to admins, rotate credentials automatically, and ensure that no one has standing privileged access longer than necessary. It has become an important tool for maintaining compliance and reducing the risk of unauthorized access.
Recently, we faced a situation where one of our database servers needed urgent troubleshooting from a senior admin. Instead of sharing credentials or giving permanent access, we used One Identity Safeguard to grant temporary privileged access. The admin requested access through the system, it got approved, and One Identity Safeguard automatically provided the credentials without exposing the actual password. The entire session was recorded, which gave us confidence from a security and audit perspective. What made a difference was that once the task was completed, the access was automatically revoked and the password was rotated or changed, alleviating concerns about lingering access or manual cleanup. This made the entire process much more secure and streamlined compared to previous methods.
What is most valuable?
The best features of One Identity Safeguard include several standout capabilities we rely on heavily. The biggest feature for us is privileged session monitoring and recording, which gives full visibility into what admins are doing, and the ability to replay sessions later is particularly useful for audits or troubleshooting. It enhances security since everything is tracked and traceable. Another key feature is secure password management with automatic rotation, eliminating the need for manual credential management. The system handles password changes regularly, significantly reducing risk. We also find the access request and approval workflow very valuable. Instead of informal access sharing, everything goes through a structured process that maintains control and compliance. We would also highlight real-time monitoring and alerting; if any suspicious activity occurs during a session, it can be flagged or halted immediately, adding an extra layer of protection. Overall, the combination of visibility, control, and automation makes it very useful, focusing on securing access while making the process manageable and auditable.
Beyond the main use case, One Identity Safeguard has integrated into our daily operations for access control, not just for high-risk situations. We use it routinely for managing privileged sessions, especially for admins who need temporary access to different systems. One standout aspect is how it enforces a structured workflow. Instead of informal access requests over email or chat, everything goes through an approval process, keeping things clean and auditable. It reduces dependency on individuals since credentials are not shared manually anymore, fostering better security habits across the team. People are more aware of access policies, and there is a clear accountability trail for every action. It is not just a tool we use occasionally; it is essential to our regular IT and security processes.
There are smaller features worth noting as well. One we find particularly useful is the ability to launch sessions directly through the platform without exposing credentials, allowing admins to connect through One Identity Safeguard without needing to see the password. Another beneficial feature is the session search and indexing; if an investigation is necessary, we can quickly identify specific sessions based on users, time, or activity rather than manually sifting through logs. This capability has been extremely helpful during audits or incident reviews. Furthermore, the policy-based access controls are quite flexible. Once set up properly, access governance operates automatically in the background, reducing manual effort. Integration with Active Directory services facilitates onboarding and management, avoiding the need to recreate everything from scratch. It is these smaller practical features that enhance usability on a daily basis, not just in audits or critical situations.
What needs improvement?
One Identity Safeguard works well for us overall, but there are several areas where improvements could be made. The initial setup and deployment can be quite complex, particularly if you are new to privileged access management tools, and understanding the architecture and configuration requires time. A more guided setup or simpler onboarding would be beneficial. The user interface could also be improved; while functional, it is not always intuitive, especially for new users. A more modern and user-friendly UI would facilitate daily operations. We have also found that reporting and customization of reports could be more flexible; although the data is available, it sometimes requires extra effort to obtain the desired format or detail level for audits or management reporting. Additionally, customer support response times could improve, particularly for non-critical issues; while the support team is knowledgeable, faster turnaround would make a difference. Overall, these are not deal breakers, but enhancing these areas would make the product more efficient and easier to adopt.
We would appreciate more automation and smarter workflows. While the approvals process functions effectively, adding more flexibility, such as conditional approvals or risk-based access, would enhance its strength. We also believe that better dashboarding and visibility would help; while data can be obtained, having customizable or real-time dashboards for aspects like active sessions, risk alerts, or access trends would allow for a quick overview without requiring in-depth report digging. Overall, these enhancements do not indicate major gaps, but they would improve usability and give the product a more modern and future-ready feel.
For how long have I used the solution?
I have been using One Identity Safeguard for a year.
What do I think about the stability of the solution?
One Identity Safeguard has proven to be stable and reliable within our environment. Once we managed to get past the initial setup and configuration, it operates consistently without major issues or downtime. Day-to-day tasks such as access requests, session monitoring, and password rotation function smoothly. It appears designed as a dependable enterprise-grade solution, reflecting well in its production performance. Similar to most complex security tools, we encountered minor issues during deployment and fine-tuning, but none that significantly impacted operations. Stability has not been a concern; it has been a reliable part of our environment.
What do I think about the scalability of the solution?
One Identity Safeguard has managed scalability effectively in our experience. As our environment grows—adding more servers, users, and privileged accounts—we have scaled its use without significant complications since we are using the virtual appliances model. Scaling primarily involves allocating additional resources or deploying more instances as needed. Platform-wise, it is designed to support enterprise-scale environments, capable of managing large numbers of sessions and users as long as it is correctly sized and configured. However, we have noticed that performance can vary based on how it is deployed; the type of workload and the number of active sessions influence capacity. Proper infrastructure planning is therefore crucial. Overall, it has adapted to our growth without necessitating major redesigns, requiring only resource tuning and scaling as demand escalated. We would say it is highly scalable, particularly for mid to large enterprise environments, provided the architecture is well planned.
How are customer service and support?
Overall, our experience with One Identity Safeguard support has been quite positive. The support team is generally knowledgeable and technically adept, particularly when addressing complex issues. Whenever we raise critical tickets, they guide us appropriately and provide workable solutions. From our observations, once we connect with the right support engineer, the quality of assistance is high. The primary area for improvement is response speed and escalation, which aligns with general user feedback, noting strong support but inconsistent response times. Overall, we would assess the support as reliable and knowledgeable, although there is scope for improvement regarding response consistency.
Which solution did I use previously and why did I switch?
Before transitioning to One Identity Safeguard, we mainly relied on a mixture of manual processes and basic access control tools, using native solutions such as Active Directory for access management along with internal processes for handling privileged credentials. We decided to switch due to scalability and security concerns; the existing approach was inadequate, leading to challenges with shared credentials, limited visibility of privileged sessions, and insufficient audit trails. It required substantial manual effort to manage and track access. After evaluating several dedicated PAM solutions, we selected One Identity Safeguard because it offered a more comprehensive and centralized approach, highlighting features such as session recording, automated password rotation, and structured access workflows. The move stemmed from our need for improved security, compliance, and operational efficiency as our environment expanded.
How was the initial setup?
The initial deployment took us around three weeks. Setting up the virtual appliances was relatively fast, but a significant amount of time went into configuration, integrating it with existing systems such as Active Directory, and defining access policies. We also allocated time to test different use cases and ensure everything operated as expected before broader rollout. While the technical setup was quick, the overall time was largely influenced by planning, integration, and fine-tuning.
Overall, the deployment was fairly smooth, though there was a slight adjustment period for our privileged users. Initially, some admins found it somewhat disruptive as they were accustomed to direct access, and now had to use an approval workflow in One Identity Safeguard to initiate sessions. There was a small learning curve and some resistance initially; however, once they became familiar with the process, things settled down quickly. Many users even began appreciating the simplified access requests and the removal of the need to manage or remember privileged credentials. We facilitated the transition by implementing a phased rollout and providing basic training, which helped minimize disruptions. While there was initial friction, it was temporary, and overall adoption progressed smoothly.
What about the implementation team?
The team managing One Identity Safeguard required a moderate level of training. We spent several days reviewing the architecture, configuration, and best practices, followed by a couple of weeks of hands-on learning during the implementation phase. While the tool is not overly complex, understanding how to design privileged access workflows and policies is essential for maximizing its use. For end users, particularly admins just needing to request and use access, the training requirements were minimal; a short session or demonstration sufficed to illustrate how to request access and launch sessions through the platform. Most people adapted quickly after one or two uses. Overall, more effort is needed on the admin side, while regular users find it quite straightforward.
What was our ROI?
We have seen a return on investment since implementing One Identity Safeguard. From a time-saving perspective, access provisioning has accelerated dramatically; what used to take twenty to thirty minutes per request can now be completed in just a few minutes, which accumulates significantly across multiple daily requests. Overall, we have likely reduced admin effort related to access management by forty percent, and from an operational efficiency standpoint, we no longer need to manage or rotate privileged credentials manually. This shift saves a considerable amount of ongoing effort and diminishes dependency on a few key individuals. We have also experienced indirect ROI by reducing security risk; quantifying it precisely is challenging, but eliminating shared credentials and enforcing session monitoring has materially lowered our exposure to potential incidents, which could be costly if they occurred. In terms of audit compliance, we have cut preparation time by approximately forty to fifty percent since most required data is readily available through logs and sessions. While headcount has not decreased, it has allowed our teams to focus more on strategic tasks instead of manual access management. Therefore, the ROI stems from a combination of time savings, enhanced security posture, and streamlined audit processes rather than direct cost reduction.
What's my experience with pricing, setup cost, and licensing?
Our pricing and licensing experience was fairly typical for an enterprise security solution. It is not the cheapest option available, but it aligns with the level of security and control it delivers. The initial setup cost was moderate; we did not incur major hardware expenses as we opted for virtual appliances, but there was still some investment needed for configuration and internal resources. Licensing is structured and scalable, which is beneficial as the environment grows, although it can seem complex initially to fully understand what is included and how to size it appropriately, requiring close collaboration with the vendor during that phase. From a value perspective, we see it as justified because it replaces many manual processes and mitigates security risks. However, organizations should plan their licensing thoughtfully to avoid over or under-provisioning. Overall, it represents a solid investment, although entering with a clear understanding of requirements is essential for maximizing value.
Which other solutions did I evaluate?
Before selecting One Identity Safeguard, we assessed a few PAM solutions, specifically CyberArk and BeyondTrust. Both are reputable solutions and widely recognized in the market. CyberArk is particularly feature-rich, but we found it somewhat complex and costly relative to our requirements. BeyondTrust was also a strong contender, especially regarding usability, but in our case, One Identity Safeguard presented a better balance between functionality, ease of use, and overall cost. We also took into account how well One Identity Safeguard integrated into our existing environment and the speed at which we could deploy it compared to alternatives. Overall, the decision was not due to shortcomings of the other tools, but rather finding the right fit for our specific needs.
What other advice do I have?
My main advice for those considering One Identity Safeguard is to carefully plan your implementation beforehand. This is not a plug-and-play tool; you will extract the most value by clearly defining your privileged access policies, workflows, and use cases in advance. We also highly recommend conducting a proof of concept in your environment to test real scenarios, particularly edge cases such as legacy systems or service accounts, as challenges often arise in these areas. This testing approach is strongly advocated by practitioners since real-world scenarios provide a clearer picture than demos. Additionally, invest time training your admins and establishing clear processes. The tool is powerful, but it works most effectively when your team understands how to use it properly. From a technical standpoint, ensure you size and secure your deployment accurately—planning for storage, access restrictions, and network setup, especially in cloud environments, is vital. Overall, it is a robust solution whose success hinges on effective planning, implementation, and alignment with your organization's processes. I would rate this product an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Centralized controls have improved privileged access security and audit visibility
What is our primary use case?
In our organization, the primary use of One Identity Safeguard is managing and securing privileged access, and we mainly use it to store and protect sensitive credentials like admin passwords, ensuring that they are not exposed or misused. It also helps in monitoring privileged sessions, allowing us to track and audit activities performed by administrators or high-level users. This adds a stronger layer of security and compliance, as all credential access is controlled, recorded, and reviewed when needed. Overall, it plays a key role in protecting sensitive systems and reducing the risk of insider or outsider threats.
A common example of how we use One Identity Safeguard to secure privileged access is when a system administrator needs access to a production server. Instead of sharing or knowing the actual admin password, they request access through One Identity Safeguard, which securely provides a temporary credential for a session without exposing the password. This system automatically records an entire session, including actions performed on the server. If anything unusual happens, such as an unauthorized change or risky commands, the session logs and recording can be viewed by a security team, ensuring that privileged access is tightly controlled, fully monitored, and auditable at all times.
One additional point about our main use case is that we use One Identity Safeguard not just for securing access but also for enforcing strict governance and accountability across teams. For example, we apply role-based access control and approval workflows, so any privileged access request must be approved before it is granted.
What is most valuable?
The best features of One Identity Safeguard mainly revolve around strong security, visibility, and control over privileged access. One of the most valuable features is its password management, where sensitive credentials are securely stored, automatically rotated, and accessed only through a controlled workflow, reducing the risk of misuse. Another standout feature is session monitoring and recording, which captures every action taken during privileged sessions.
The session monitoring and recording feature in One Identity Safeguard has been extremely valuable for our team, especially from a security and compliance perspective. We use it quite regularly whenever an administrator accesses critical systems. Every privileged session is recorded in detail, covering screen activity, commands executed, and user behavior, so we have a complete audit trail. This has helped us quickly investigate incidents, verify actions taken on sensitive systems, and ensure that all activities follow internal policies.
One Identity Safeguard has had a very positive impact on our organization, especially in terms of security, efficiency, and visibility. It has helped us centralize and control privileged access and provided a structured secure approach. As a result, we now have much better visibility into accessing credentialed systems and the actions performed, which has improved accountability and compliance.
One Identity Safeguard has significantly improved accountability and compliance by giving us complete visibility of all privileged activities. Every access requires approval, and a session is logged and recorded, which means we always have a great audit trail of who accessed what and when. This has made internal and external audits much smoother, as we can quickly provide evidence without manually tracking.
What needs improvement?
One Identity Safeguard is a strong PAM solution, but there are definitely a few areas where it could be improved based on practical experience and known limitations. One key area is performance and resource usage, especially when advanced features like session recording or OCR are enabled. These features consume significant CPU and storage, and in some cases, may slow down connections or processing time if not optimized properly. Improving efficiency here would make the platform smoother and more scalable.
One additional improvement that would be helpful in One Identity Safeguard is better integration flexibility with modern cloud and DevOps tools. While it supports many systems, connecting with newer platforms for automation workflows in dynamic environments can sometimes require extra effort or customization.
For how long have I used the solution?
I have been using One Identity Safeguard for two years.
What do I think about the stability of the solution?
One Identity Safeguard is stable.
What do I think about the scalability of the solution?
One Identity Safeguard is highly scalable, and that is a core strength in enterprise environments. It is designed for scale through clustering and a distributed architecture, allowing multiple appliances to work together as a single system. For example, organizations can add multiple One Identity Safeguard appliances to handle an increasing number of users, privileged accounts, and session traffic without impacting performance.
How are customer service and support?
Customer support for One Identity Safeguard has been generally reliable based on our experience. On the positive side, the customer team is knowledgeable and technically strong, especially when dealing with configuration issues, session monitoring, or password-related queries. For standard or well-defined issues, responses are usually helpful and resolve problems efficiently.
Which solution did I use previously and why did I switch?
We evaluated a few other privileged access management (PAM) solutions before implementing One Identity Safeguard, including CyberArk and other enterprise PAM tools in the same space.
How was the initial setup?
The deployment of One Identity Safeguard was relatively quick compared to many other IAM and PAM solutions because it is delivered as a pre-configured appliance, either physical or virtual. The initial setup can be done quite fast, which helps to reduce the time to value.
What about the implementation team?
The deployment of One Identity Safeguard was fairly smooth overall with minimal disruption for privileged users. During the initial rollout, there was a short adjustment period where users had to request access through the system instead of directly using credentials, which slightly changed their workflow. However, once they became familiar with the process, it actually improved their experience by simplifying access and removing the need to remember or manage sensitive passwords.
The training required for One Identity Safeguard was quite manageable and varied by role. For end-users and privileged users, training was minimal, and basic guidance was enough for them to understand how to request access and start sessions since the interface is fairly straightforward for daily use.
What was our ROI?
We have seen a clear return on investment with One Identity Safeguard, mainly driven by time savings, reduced manual effort, and fewer security-related incidents. One of the biggest measurable improvements has been in IT workload reduction. After implementing One Identity Safeguard, we saw a significant drop in manual tasks including password handling, privileged access approvals, and incident troubleshooting.
What other advice do I have?
My advice to others looking into using One Identity Safeguard is that we have seen a clear return on investment, mainly derived from saved operational efficiency and reduced security overhead. A simple way to explain it is time saved, faster administration, fewer security incidents, and efficiency gained.
Overall, One Identity Safeguard stands out as a strong and well-built privileged access management solution, especially for organizations that want tighter control over admin activity without slowing down operations. I would rate this product a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
