Minimal maintenance is required because it is a virtual appliance, and everything is preconfigured.

We have a virtual appliance. We chose the virtual appliance because we were already using a virtual machine infrastructure, so it was easy for us. Our implementation is not complex. We do not have a lot of regulations. It does not matter if we lose connectivity. It is not the end of the world, so for us, a virtual appliance was good enough. It was easier to implement. We do not need to rely on physical devices.

We are using the virtual appliance because we already have a virtual environment. The only on-prem setup we have are the physical servers that run a hypervisor. We like to have everything virtual. We can also secure a virtual appliance in a different way compared to the physical appliance. With a physical appliance, if something happens, we have to get hold of the vendor and sort out how fast they can ship a replacement, whereas we can deploy a virtual appliance instantly and get it up and running if there is a problem.

We have physical SPPs and virtual SPSs in One Identity Safeguard.

We use the on-demand version of One Identity Safeguard because it provides us flexibility, which was the main reason for choosing that version.

Using the virtual appliance is quite easy. You download the hypervisor file, everything is already included. There is one appliance for the SPP and one for the SPS. SPP requires a Windows license and to activate it you must have internet access.

In our setup, we use virtual appliances for One Identity Safeguard. We chose virtual appliances mainly because of the flexibility and scalability they offer compared to physical hardware. Key reasons for this choice include the ease of deployment. Virtual appliances can be deployed quickly within our existing virtual infrastructure without waiting for hardware procurement. Regarding scalability and performance, it is much easier to scale resources (CPU, memory, storage) based on demand, especially as privileged access usage grows. Regarding cost, it avoids the upfront cost and maintenance overhead of physical appliances.

We are using One Identity Safeguard in a hybrid setup, partly on-premises for sensitive access control and partly integrated with cloud services.

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 deployment of One Identity Safeguard on virtual appliances took roughly six to eight weeks end-to-end.

The initial setup of the virtual appliances and basic configuration was completed within a few days, but the overall deployment, including integration, policy setup, access workflow, and testing, took a couple of weeks to fully stabilize.

We use virtual appliances because they are easier to operate and use compared to physical appliances. Additionally, for those of us who are located remotely, purchasing this tool is easier with the virtual appliance compared to physical appliances.

One Identity Safeguard is deployed in my organization on physical appliances, which are dedicated hardware appliances provided by One Identity.

My experience with pricing and licensing for One Identity Safeguard has been generally positive, but it depends on the scale. It is an enterprise-level solution, so it is not the cheapest, but the pricing is fair for the level of security and features it provides. Many users also consider it more cost-effective compared to some competitors such as CyberArk, especially in the long term. In terms of licensing, it can be a bit complex. It is usually based on users or devices and you need to properly plan what modules you need, such as password management or session monitoring. Also, for virtual deployments, you may need additional OS licensing, which adds to the cost. For setup cost, since we deployed it on-premises, there was some initial investment in configuration and integration, but no heavy recurring infrastructure cost beyond that.

In our environment, One Identity Safeguard authentication services was mainly deployed on-premises, so cloud dependency was minimal. Although we had some integration with Microsoft Azure for hybrid infrastructure and identity-related operations, One Identity Safeguard was mainly deployed as virtual appliances on VMware infrastructure. We use virtual deployment because it is easier for scaling, backup, disaster recovery, and maintenance compared to physical appliances.

The virtual appliance deployment was chosen because it was easier to deploy in our existing virtualized infrastructure, required less hardware management than physical appliances, and offered the flexibility to scale as our environment grows. It also simplified backup, maintenance, and software updates while providing the same core privileged access management capabilities we needed.

I do not use any physical appliances, virtual appliances, or on-demand versions with One Identity Safeguard.