My main use case for One Identity Safeguard has been managing and securing privileged access across critical systems. I primarily use it for password vaulting and automated credential rotation, which helps eliminate manual password handling and improve security. In addition, I work with access request workflows where users request privileged access and approvals are enforced before granting time-bound access. I have been involved in monitoring and reviewing privileged sessions for audit and compliance purposes. Overall, I use One Identity Safeguard to ensure secure, controlled, and traceable access to sensitive systems.
In addition to the core use cases, I also use One Identity Safeguard for day-to-day operational tasks such as onboarding new assets and accounts into the vault, maintaining access policies, and troubleshooting access-related issues. I regularly review audit logs and session recordings to ensure compliance and investigate any unusual activity. I have also worked on integrating One Identity Safeguard with directory services such as Active Directory to streamline user authentication and access control. Overall, my day-to-day usage is focused not just on securing privileged access but also on improving efficiency, enforcing security policies, and ensuring complete visibility and accountability across all privileged activities.
View full review »
My main use case for One Identity Safeguard is managing and securing privileged access across the organization. On a day-to-day basis, I use it for password vaulting, session management, and controlling access to critical systems. It helps ensure that credentials are not shared directly and are accessed securely through the platform. For example, when an admin needs access to a server, they request it through One Identity Safeguard, and access is granted with proper approvals, while the session can be monitored or recorded for security and compliance.
Session monitoring and recording have really improved both security and accountability for our team. For example, when an admin accesses a critical server, the entire session is recorded. If there is ever an issue, such as a misconfiguration or an unexpected change, we can go back and review exactly what actions were taken and by whom. It also acts as a deterrent because users know their sessions are being monitored, so they follow best practices more carefully. Overall, it makes audits much easier and helps us quickly investigate and resolve any incidents.
Apart from access control and session monitoring, I also use One Identity Safeguard for automated password rotation, which reduces the risk of credential misuse. Day-to-day, I handle access requests, review audit logs, and ensure compliance policies are being followed. It also helps in managing third-party or vendor access securely, giving them controlled and time-bound access without exposing actual credentials.
View full review »
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.
View full review »
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.
View full review »
One Identity Safeguard is used primarily in our day-to-day operations to manage and secure privileged access across our IT environment by controlling, monitoring, and auditing all administrative sessions. Instead of sharing static credentials, users request access through One Identity Safeguard, which grants time-bound privileged sessions with proper approval workflows. It automatically records and monitors these sessions for security and compliance purposes, while also securely storing and rotating passwords for critical systems, reducing the risk of credential misuse. Overall, it helps us to enforce strong governance, maintain accountability, and ensure that all sensitive access is controlled, traceable, and aligned with our security policies on a daily basis.
A recent example of using One Identity Safeguard was when a team member needed temporary administrative access to a production server for troubleshooting. Instead of sharing credentials directly, they raised a request through One Identity Safeguard that went through an approval workflow. Once approved, they were granted a time-limited session without ever seeing the actual password. The entire session was recorded and monitored in real-time. After the task was completed, access was automatically revoked and the password was rotated. This ensures security, accountability, and compliance without any manual intervention or risk of credential misuse.
In addition to the core use case, One Identity Safeguard fits seamlessly into our workflow by acting as a central control point for all privileged activities. This means every sensitive access request, whether for servers, databases, or network devices, follows a standardized and secure process with approvals, session monitoring, and automatic credential management. It has significantly reduced the need for manual password sharing and tracking, while also improving coordination between teams because everyone follows the same access process, making our operations more structured, secure, and audit-ready without slowing down productivity.
View full review »My use case mainly involves privileged access and access to privileged accounts and privileged systems.
View full review »
We have been using One Identity Safeguard for more than a year now, approximately 14 to 15 months to be precise.
We primarily use One Identity Safeguard to secure our passwords, our sessions, and also use the Safeguard analytics as well. Primarily, we use it to safeguard our privileged passwords as this automates and controls and majorly secures the process of granting privileged credentials or privileged passwords. It is also role-based access management, which is very helpful for us.
Primarily what we do is whenever any new user or any new role-based access is generated in our company, we use Safeguard to generate the password. As it automates, and also we track and we control most of what the password is going to be so that it is completely authenticated and completely safe. Hourly or even daily password changes are recommended through Safeguard, which helps in safeguarding the password as password stealing or password theft is a major issue for us. So through this Safeguard, we are able to control all that.
View full review »
I primarily use One Identity Safeguard for Privileged Access Management, mainly to control, monitor, and secure administrative access to critical systems. I also used it for session monitoring and audit visibility for sensitive administrative activities. Having centralized logging and session tracking was important from both a security and compliance perspective. The practical use case involved temporary privilege access. Instead of giving permanent elevated permissions, teams could get controlled access for specific tasks or durations, which supported least privilege practices better.
One practical example was during a production support activity where a vendor team needed temporary administrative access to troubleshoot an application issue on a critical server. Instead of sharing privileged credentials directly, access was provided through One Identity Safeguard with time-based control. The session was monitored, and the access automatically expired after the approved maintenance window.
One additional area where One Identity Safeguard was useful was improving accountability around privileged operations. In many environments, multiple teams need elevated access for infrastructure, database, or application support, and without proper PAM controls, it becomes difficult to track who actually performed what action.
View full review »I mainly use One Identity Safeguard to secure and control privileged access by managing admin credentials, granting time-based access, and monitoring sessions to ensure security and compliance.
For example, when an admin needs access to a production server, they request it through One Identity Safeguard, which grants time-limited access after approval. The system automatically injects the credentials, so the password is never exposed, and the entire session is monitored and recorded. This helps my team maintain security and quickly review activity during an audit.
View full review »In my daily operations, I rely on One Identity Safeguard for administrator requests for access through One Identity Safeguard, which are approved via workflows. Once approved, sessions are launched, ensuring security without revealing passwords, and all activities are recorded for auditing purposes.
In our environment, there were multiple administrators using shared privilege accounts, which created accountability and security risks. With One Identity Safeguard, we implemented password vaulting where passwords are automatically rotated and never exposed to users, ensuring secure access and eliminating shared credential risks.
In our daily operations, One Identity Safeguard is primarily used to manage and control privilege access to critical systems such as servers, network devices, and databases. Administrators and users request access through One Identity Safeguard, which follows an approval-based workflow. Once access is approved, users can securely connect to the target system without directly viewing or knowing the privilege credentials. All sessions are proxied through One Identity Safeguard, ensuring that passwords are never exposed. Additionally, every session is monitored and recorded, allowing security teams to review activities when required. We also use One Identity Safeguard for automated password rotation, ensuring that privileged account passwords are regularly updated without manual intervention. Overall, it acts as a centralized platform for security, secure access management, auditing, and compliance in our environment.
View full review »
My primary use case for One Identity Safeguard is privileged password vaulting and real-time session monitoring, which has been a game changer for managing sensitive access. I mainly use it to securely store, manage, and rotate privileged credentials across multiple environments. In my day-to-day work, I frequently need to provide temporary, controlled access to different users, including third-party vendors. In a recent project, we granted time-bound access through the privileged password vault and monitored vendor activity using session recording rather than direct password exposure. Another major advantage is One Identity Safeguard’s ability to integrate with existing systems, particularly for centralized privileged password management.
View full review »In day-to-day work, I use One Identity Safeguard to manage centralized login for Linux and UNIX servers, troubleshoot login access issues, enforce security policies, manage AD-based permissions, monitor authentication logs, and ensure secure and compliant access across the systems.
Additionally, I use One Identity Safeguard for operational tasks like on-boarding and off-boarding users, reducing dependency on local accounts, improving audit and visibility, and simplifying administration through centralized access control and policy management.
View full review »
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.
View full review »My main use case for One Identity Safeguard is to manage and control privileged accounts and store passwords. For example, if an IT admin needs access to a server, I use One Identity Safeguard to manage and control privileged accounts. One Identity Safeguard helps companies avoid data breaches regarding my main use case, influencing other teams and types of users who interact with it.
View full review »
My main use case for One Identity Safeguard is managing and securing privileged access on a day-to-day basis. It is used for password vaulting, controlled admin access to servers, and monitoring privileged sessions to ensure security and compliance.
Recently, I used One Identity Safeguard to retrieve a privileged account password from the vault for server access during troubleshooting. The access was time-bound and automatically logged. I also checked session activity logs to verify the actions performed, ensuring everything was secure and compliant.
View full review »My main use case for One Identity Safeguard is for strong security, and it also helps me to store my information, to protect my data, and focus on data protection compliance.
One specific example of how I use it for security is to protect my data from external access. Regarding security compliance, I am able to set the metrics and also set the guidelines and the regulations about how my software should be stored and kept.
View full review »
One Identity Safeguard is used to secure privileged access management, credential vaulting, and session monitoring because we are an IT-based company that handles the IT infrastructure of our clients, making it very important to keep everything secure.
One Identity Safeguard vaults privileged service accounts and provides time-bound access, ensuring that all administrative actions are tracked, reviewed, and easily monitored. We also use One Identity Safeguard to securely check admin credentials for customer servers. All access is automatically recorded and monitored through session auditing, which helps us comply with our customers' requirements.
We centrally manage privileged credentials, enforce secure access workflows, and record privileged sessions to maintain compliance and strengthen the IT security we deliver to our customers.
View full review »
With our privileged accounts, the main issue we face is doing any sort of integration through API, as that becomes very susceptible to threat attacks. We are using PAM tools during our API integration to ensure security.
View full review »My main use case for One Identity Safeguard is that it serves as a secure, strong PAM solution, and we are using it for PAM authentication.
In daily work, we use One Identity Safeguard for privilege access management, including secure PAM authentication, password vaulting, access request approval, session monitoring, and automatic password rotation for privileged accounts and service servers.
Apart from PAM authentication, we also use One Identity Safeguard for secure privileged session management, auditing, compliance, tracking, and centralized control for critical administrative accounts. It helps to improve security, accountability, and operational efficiency in daily infrastructure management.
View full review »My main use case for One Identity Safeguard is for privileged access management to control, monitor, and secure access to critical systems, servers, and applications used by administrators and IT teams.
A quick specific example of how I use it for privileged access management in my environment is that when an administrator needs access to a critical server, they request access through One Identity Safeguard instead of using shared credentials. The system grants time-bound, approved access, rotates the password automatically after the session, and records the entire activity.
View full review »
My main use case for One Identity Safeguard is to store our IDs and passwords so that they can be used later for logging in. It also helps us when our employees are working from home by managing IDs, passwords, and other login credentials safely, without any worry of password theft or identity theft.
A specific example of how I use One Identity Safeguard with employees working from home is when they are using their personal Wi-Fi connection, where the chance of personal theft increases. One Identity Safeguard helps us manage the chances of theft, reducing the instances of password theft and identity theft, which has been very useful for us and has also reduced the cases we experience.
View full review »
One Identity Safeguard has been used by our organization for more than three years. The primary use case for One Identity Safeguard is to secure admin access to the servers and the network devices, which helps us to ensure only authorized users can access our critical systems and devices, and it also monitors all the privileged sessions.
View full review »
My main use case of One Identity Safeguard is to manage and secure privileged access in our IT environment. We use it for password vaulting, automatic credential rotation, and monitoring administrator sessions on servers, network devices, and critical systems.
View full review »
I use One Identity Safeguard mainly for managing and securing privileged access like controlling admin accounts and monitoring sensitive sessions.
For example, I use One Identity Safeguard to grant temporary admin access to users and track their sessions to make sure everything is secure.
One Identity Safeguard also helps with password vaulting and automatic rotation.
This means we don't have to share or manually manage sensitive credentials.
We are using One Identity Safeguard in a hybrid setup, partly on-premises for sensitive access control and partly integrated with cloud services.
We have integrated One Identity Safeguard with our cloud environment on Microsoft Azure and also with some internal DevOps workflows so privileged access can be controlled during the deployments and automation tasks.
It was moderately easy overall to integrate One Identity Safeguard with our DevOps workflows and Microsoft Azure environment.
Microsoft Azure integration was pretty smooth, but the DevOps workflow setup took a bit more effort to configure and test properly.
View full review »One Identity Safeguard's main use case in our environment is authentication services. It serves as a centralized authentication solution for Linux and Unix servers, including the use of Active Directory credentials. This helps us simplify user access management, reduce local account dependency, improve security, and provide centralized authentication and auditing across servers.
A specific example of using One Identity Safeguard is for Linux and Unix server access management. Instead of maintaining separate local accounts on servers, users can log in using their Active Directory credentials. This simplifies access management, reduces password-related issues, and improves audit visibility.
View full review »My main use case for One Identity Safeguard is to safeguard my password as well as my login IDs when I'm working from home, as it provides better safety for my passwords and for my login IDs.
When we log in, we get two-factor authentication, which I use for safeguarding my passwords or login IDs while working from home, and that makes it safer compared to other software.
One Identity Safeguard helps in keeping my login IDs and passwords safe, and that is very important to me.
View full review »
My main use case for One Identity Safeguard is securing administrator access to critical infrastructure, like firewall servers, switches, databases, as well as the VMware environments. Earlier, multiple engineers used shared admin passwords for devices and servers, which made it difficult to track who performed what activity. This also increased the risk of password misuse and unauthorized access. We have used One Identity Safeguard to secure all of these resources.
A specific example of how I use One Identity Safeguard to secure access or track activities is when an engineer wanted to log in to a firewall for some configuration changes. One Identity Safeguard provides secure access without exposing the actual password. Once the task was completed, the password could be automatically changed, ensuring better security. This use case helps the organization improve privileged access security, maintain accountability, and reduce insider threats for auditing and compliance purposes.
One Identity Safeguard is deployed in my organization on physical appliances, which are dedicated hardware appliances provided by One Identity.
View full review »My main use case for One Identity Safeguard is to use it as a PAM tool for managing and monitoring privileged accounts. In every organization, there are special accounts such as admin or root accounts that have a very high level of access, and if these accounts are missed or compromised, it can create problems or damage. One Identity Safeguard helps us to control who uses these accounts and when they can use them.
A quick, specific example of how I use One Identity Safeguard to manage those privileged accounts involves a database administrator needing to make an urgent change to our production database. In the past, we would just use a shared admin password that everyone in the team knows, but now with One Identity Safeguard, the admin logs into the Safeguard portal and raises an access request for the production database. The request automatically goes to his manager, and based on the review, it gets approval. One Identity Safeguard connects the admin to the database without showing him the actual password, so he never knows about the credentials.
View full review »Our main use case for One Identity Safeguard is to integrate it to clients that need the SPP functionality, which stands for Safeguard for Privileged Passwords. They do say that we could utilize One Identity Safeguard to its full extent for now, but we're getting there.
A quick specific example of how we use One Identity Safeguard with a client is that our latest client needed a password vault, so at first, we integrated One Identity Safeguard for Privileged Passwords, and then they asked for a personal vault so they could store their passwords and secrets, much like KeePass, so we integrated One Identity Safeguard Personal Vault as well. Lastly, they figured at some point down the line that they needed SPS as well, but only the primitive version of it, so we just decided to integrate SPS as well and form it into a cluster with SPP, but they don't use any third-party plugins as of now.
View full review »
My main use case for One Identity Safeguard includes privilege access, session recording, and real-time monitoring.
In daily work, I use session recording and real-time monitoring as part of my workflow.
My main use case is privilege access.
View full review »
One Identity Safeguard is used for managing privileged passwords and monitoring sessions, which helps track admin activities and enforce secure access policies for the accounts. This is important for protecting critical resources like systems or applications, thereby improving both security and accountability.
Whenever an admin needs server access, they must request it through One Identity Safeguard. Once approval is granted based on the request, they can access the server, and the session is recorded, keeping everything monitored and controlled.
Whenever an admin accesses a server through One Identity Safeguard, they do not need to know the actual password. The system provides temporary access through the vault, ensuring secure and controlled usage of the applications.
View full review »
I have hands-on experience with One Identity Safeguard and attended the foundation course in the end of last year. My primary goal is to make use of the cross-product capabilities joining IGA (Identity Manager) and Safeguard (PAM) to achieve Privilege Access Governance (PAG) since lots of customers are asking for this. The trend show consolidation within the IAM market and cross-product solutions is becoming the new standard.
View full review »
My main use case for One Identity Safeguard in day-to-day work is to provide identity across all user accounts and domains, and it improves security across the enterprise by providing enhanced features with respect to this identity solution.
I primarily use One Identity Safeguard for protecting security across all user accounts, enterprise data accounts, assets, as well as privileged access, domain user, and admin accounts, giving SSO features and providing security across all user accounts.
View full review »Our main use case for One Identity Safeguard is for business development activities by understanding and communicating platform security features to clients.
We generally use One Identity Safeguard for managing privileged accounts and session monitoring because we have mass emailing, which requires privilege IDs and sensitive data management. The HR department focuses on this, along with the main manager, to utilize platform controls and limit data access for security and compliance. Session monitoring ensures that all our work in the mail marketing system is detected, and if any suspicious activity is identified, it is reported to management.
One Identity Safeguard is also used for audit logs and reporting features, helping to reduce the time and efforts needed for audits.
View full review »
My main use case for One Identity Safeguard is using only one module for privileged session, which we use for admins and contractors.
A quick specific example of how my team uses One Identity Safeguard day-to-day is that we use only the second part for our contractors, not for admins in our company, but for companies that help us perform admin work and support our system.
View full review »We are using it internally because I work in a consultancy company. I use it both for our internal privileged accounts. We have different systems like Google Cloud, some internal servers, data centers, etc. To secure those privileged accounts, like the administrator accounts and root accounts, I use One Identity Safeguard to rotate passwords, authorize sessions, and more. The second use case is that we also implement One Identity Safeguard for different customers.
Our main use case for One Identity Safeguard is to manage and secure privileged accounts, session monitoring, and recording for audit purposes while also providing controlled access to vendors or our internal team, and enforcing least privilege access.
View full review »
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.
View full review »The purpose is to ensure that privileged users do not know their own passwords.
We use it to handle secure access to our Windows and Linux servers and also to manage some of our user accounts. This includes password rotation, JIT, and disabling accounts when they are not in use.
We use their physical appliance.
View full review »
One Identity Safeguard serves as our Privileged Access Management solution to enforce session management for administrators and allow them to access our systems in recorded sessions, which secures our environment.
In our daily operations, One Identity Safeguard acts as a centralized privileged credentials manager for our systems including Windows, Linux, network devices, and our database, allowing administrators to access our database systems in critical environments while recorded sessions ensure security and accountability.
We have just-in-time access with approvals, allowing administrative access to our users based on request and approvals, which helps us monitor requests for access to critical systems.
View full review »
We are a One Identity partner, and our clients use One Identity Safeguard for password vaults, session management for Linux and Windows servers, and network appliances.
View full review »
Our customer is a public service organization with about 800 privileged accounts and 8,000 functional accounts. The client already has a relatively unadvanced identity management implementation. It's a request-based identity management solution. What we're doing now is getting better control of the privileged accounts and getting rid of the old technology.
The end users don't know of an alternative. They are still subject to identity management through what is quite a large, manual process instead of process automation. For instance, the users do not have a self-service port where they can automatically get privileges they don't have today. Everything goes via the ITSM manual control workflow.
It's the manual processing our client currently has that is what we are thinking of improving. The installation was not set up by my team, but our job is to focus on the most sensitive information assets and secure insights into how service and other infrastructure are managed through privileged accounts. After that, we will work on simplifying the everyday user experience.
We work with just the physical appliances. It wasn't my decision. It was what the client already had. Regarding the form factor, just put it in a rack and it works. It's not an issue.
View full review »I am an independent consultant who assists end users in deploying One Identity Safeguard correctly and creating all necessary workflows within the product. I then ensure its effective utilization in the production environment. I have been working with Safeguard since the beginning and continue to use it presently. Based on my experience, the majority of projects, around ninety-nine percent, involve virtual appliances. While I have performed some hardware appliance installations, I lack extensive experience with them. Therefore, I cannot definitively state whether they are good or bad. However, I can affirm that they function properly.
When we discuss the situation at the beginning of my journey, it serves as a safeguard. So, seven years ago, it primarily revolved around RDP and SSH session control. However, nowadays, I observe that customers are shifting their focus primarily toward password rotation and password management functionality. Moreover, they are increasingly utilizing the permanent analytics capabilities of Safeguard, such as user entity and behavioral analytics. Currently, we utilize all the functionality offered by One Identity Safeguard, including password rotation, password management, session management, and possibly session harmonics as well.
In most cases, we are referring to active directory environments and the safeguards implemented in such environments. This implies a close integration with the domain controllers, which serve as a source of identity information. However, the customers I work with as an independent consultant often utilize password management solutions. This indicates their desire to replace passwords, which may already be in use on certain devices. Sometimes, it involves scheduled password rotation. Additionally, session management has evolved. Nowadays, some customers are not only using RDP and SSH control but also MSS. Furthermore, I have worked on several projects involving HTTPS special control.
View full review »
Our administrators mainly use it to protect their different packages and access secrets through Safeguard, either by checking out credentials, using encrypted sessions, or utilizing the product's API.
We are using a virtual appliance deployed in the cloud and on-premises.
View full review »My main use cases include LDAP, SSH, and some utilization of HTTPS. My primary uses are LDAP and SSH.
View full review »We are using One Identity Safeguard for our data protection.
We are utilizing the virtual appliance solution because it is slightly more cost-effective and allows us to manage it remotely.
View full review »We mainly use the Privileged Session Management (PSM) features.
View full review »
We use the virtual appliance of One Identity Safeguard to enhance security when external support is logged into our internal network. This is because it is the riskiest situation when an external company logs into servers to provide support. We want to increase security and monitoring to minimize risk. We have better monitoring tools to help us achieve this.
View full review »
We primarily use the solution to manage identities.
View full review »We use One Identity Safeguard to manage our privileged accounts.
We use One Identity Safeguard on both physical and virtual appliances.
View full review »I work for a bank, and we use Safeguard to manage access to our Internet banking services. We use Safeguard for two things: identity and access management and detection recording. We have our services onboarded on SysTrack doing RDP directly to the servers or station, and we use virtual appliances for collection. The solution covers around 150 users at this organization.
View full review »We use the on-demand version. We use the solution for monitoring and connection to the customer's server for Windows and Linux.
View full review »We use it to link our virtual systems. We have Windows and Linux, and we have some applications. We use One Identity Safeguard to connect to them. We also use Password Vault, and we do session monitoring.
I am one version behind the latest version. I usually wait before doing an update to make sure that there are no problems with the new release.
We have more than 1,000 servers or application servers, and we have several layers of teams. We have super admins, system admins, and operations staff, and we also have application vendors using the system. In such a large environment, it was really difficult for us to do identity management on a daily basis. We had new people joining the team, and we also had people leaving. We had to put in additional manpower to monitor these activities and comply with the regulations. That was the main reason we moved to automation with the One Identity solution. We are using their Privileged Account Management solution.
We have virtual appliances. We don't have physical ones.
View full review »The first time I used One Identity Safeguard was when I was the manager of the infrastructure of Ayendeh Bank, and we are currently using it now at my present company.
Our main use case is in security reviews for all of the change management and incident management services, and we also use it for the VPN connection for PAM. It allows us to review everything that goes on over the working day.
For example, our third-parties who support all of our services, including network services (e.g. Cisco) and our Linux servers, are eligible to connect via the VPN, and through One Identity Safeguard, they are able to make contact with and use the various services.
Our company works alongside various PSPs (Payment Service Providers),
and our work here is mainly to prepare the software switch for them, and
to handle the SLA for infrastructure maintenance services. Due to the nature of our work, we also use One Identity Safeguard for on-call and direct administrators whether they are in-house or external to our company. It is, in fact, the main tool for managing access for all the services. And because of that, I'm available for these companies 24/7 all year long.
At present, we have around 17 direct users of One Identity who use it on a daily basis, which includes 10 people from my own department.
We introduce One Identity Safeguard to customers, primarily Italian customers who need to partner with solutions that protect their target resources.
View full review »We use Safeguard for managing privileged passwords only, using physical appliances.
View full review »We primarily use the solution to manage passwords and use for the RDP access.
Our infrastructure is three SPPs and two SPSs. This is across 1,000 users and approximately 500 targets.
View full review »Our company is regulated by the central bank in our country. There are about 4,000 employees in our organization.
Our main need was to reduce the operational cost of our department by increasing the window of operations to 24-hour rather than have office unemployment.
We are now digitizing the access control function through One Identity. Whoever forgets their password can reset it on their own rather than reaching out to the security desk. Whenever we have a new employee, we found that it was taking at least two days to get them a username or access to the system. Now, once they are logged into the organization and are registered on our ERP system, their complete access will be ready within five seconds. They will receive an SMS with their username and password so they can start working. This has increased efficiency and effectiveness of the access control function. It has reduced operational costs as well as providing services 24/7 with a platform that can be used anytime and anywhere for investigation in case we have a requirement.
We use the physical appliances, as they are more reliable. Around the world, dedicated appliances are more reliable than having a virtual version/copy. We went with the physical appliances because they are dedicated and closed like a black box. However, we haven't reported any misses with the virtual version.
View full review »With Safeguard, there are two virtual appliances. There is one that helps you manage passwords and then there is another one that helps you record the sessions. You can configure it to record whatever you do when you make the remote calls.
We use this solution for a bank. My current project is to onboard all the bank's security assets onto Safeguard. It will be used for admins to have secure access to the server.
We use this solution to control the access of privileged users, such as application administrators, to the internal network. This solution allows us to record and log user sessions.
We use virtual appliances on the VMware platform. The virtualization of such services allows us to flexibly scale our hardware configuration and gives significantly more opportunities for building a stable structure.
There are two parts to Safeguard: the sessions recording part and the password management appliance. With the password management appliance, we have been using version 2.10. For the sessions recording, we started off with version 6.2. It has new additions and updates which have come out, thus we've upgraded. Currently, we are up to version 6.5.
We are doing a sessions recording for all of our UAT and production servers. Therefore, if something breaks/happens or there's a change during the day without the proper change control mechanisms, we can determine the session by pulling the last session on the box and finding out who did what. Then, for the password part, it is used to consolidate enterprise-wide all our passwords for our 2000-plus server accounts.
We have five physical alliances for the password part. Then, for the sessions recording, there are three virtual appliances. We went with these particular versions because they were the latest and greatest. I like to keep things updated instead of dragging stuff out, which is how people get stuck with legacy devices unable to upgrade or with no upgrade path available.
View full review »We started with administrative use cases and we were able to take control of all the local administrator accounts for endpoints and servers. We then started controlling privileged accounts for our domain administrators as well as for any kind of privileged account that had access to our switches, routers, and the like.
This year we're looking at taking control of all of the servers and application accounts. But that's going to be a longer journey for us because there are a lot more of those accounts, and there is a lot more testing that needs to be done because of the nature of the accounts.
Another use case this year is integrating Safeguard into the SQL database, so we can start taking control of the SA accounts within SQL.
Furthermore, we have a use case where we are using Safeguard to manage the account for our IIGA solution, which is our identity governance solution. When it creates new users or transfers or terminates users, it's using a privileged account that is being handled by Safeguard.
We have a lot more use cases but these are enough to give you an idea of how we use it.
View full review »The three main use cases that we have are:
These drive our first goal to take all our privileged users on the help desk, our local accounts on our desktops, our servers (web servers, app servers, or database servers), and individuals in our network group who do our firewalls, then migrate all these human accounts into Safeguard Password Vault. Last Fall, we went group by group and revised their accounts. We took away any type of privilege account that they had, ensuring that all of these accounts were then migrated to the Vault. They could then check out passwords to facilitate any type of privilege activities they needed to do on behalf of the bank.
We use virtual appliances for this solution, which made sense for us, especially if we will plan to perhaps migrate to the cloud. Right now, it's all virtualized on-premise.
View full review »We are using the virtual appliance. We are a cloud company working widely with virtualization. We provide virtual machine to our customers. When we deploy a new solution, we try to use our system to show our customers that it works for them. That is why we are using a virtual appliance which validates the usage.
For now, we are using it for traceability of access inside the platform because we are a certified company: ISO 27001, SecNumCloud, HDS... We use this solution to monitor the session of our administrator and also to capitalize on incidents. When you have an incident in the night and our Level 3 people are working on it, they don't have the time to document all they do on the platform. The main goal is to have the service up as fast as possible. We are now recording the session, and the morning after the incident, we can see the session and understand what has been done to resolve the incident.
We are using the latest version of Safeguard.
View full review »
We use Safeguard to manage users when the client wants to record all discussions on an LDAP. The solution is deployed on a VMware ESXI because all our clients don't want a physical appliance. We average about 300 to 500 connections to Safeguard.
View full review »
We use it for controlling the client sessions into our data center.
View full review »
One Identity Safeguard is used by administrators to access their devices. They will log in using identity management in order to secure the administrator's login.
View full review »We use this solution to separate the office environment from the production environment with a secure network zone. All user sessions go through One Identity Safeguard before they can reach the production environment. All sessions are audited and they are indexed/searchable through the GUI. Some of the data are transferred to our SIEM solution. For the moment we use the product for RDP and SSH sessions. We are going to use it for Citrix farms also in transparent mode.
View full review »We use it primarily for our IT team, so they can access our production and pre-production environments, to have better accountability. They have to create a ticket, check it out, and then they have to get approval from our approvers group. So there's accountability from beginning to end, and we also record the sessions.
View full review »We primarily use the solution for managing and monitoring privileged users, both internal and external.
View full review »The primary use case for our One Identity Safeguard solution is to optimize security across private accounts, accounts which can be secured upstream and downstream. The solution enables us to implement encryption protocols across channels. It is designed so that depending on the cryptographic case, different policies can be applied in correlation.
View full review »The primary use case for our customers is to monitor and audit external vendors, as well as keep track of internal actions when privileged user accounts are being used to access systems internally.
View full review »We primarily use One Identity Safeguard for Privileged Sessions (SPS) for managing our customers' access to their critical systems.
View full review »We use Safeguard for privileged sessions. It's primarily used as a solution for accessing our production environments.
View full review »Privileged management.
View full review »
One Identity Safeguard is used primarily to secure privileged credentials, enforce control over administrative access, and provide visibility into privileged activities.
Whenever a network or server administrator requires access to a production system, access is granted through One Identity Safeguard's approval workflow and credential vault rather than exposing privileged account passwords directly.
View full review »
