One Identity Safeguard is easy to use with a good partner to support you, and it can be up and running within a few days.

We did not face any significant challenges because the vendor team helped us with the integration, so the ease of integration was quite simple. We only had basic use cases like creating tickets for access requests, which are relatively straightforward, and there were not many complex integrations done. It was easy to integrate and the vendor team helped us with a step-by-step checklist for the integration with our existing SIEM and ITSM tools.

The integration with my cloud environment and infrastructure systems was moderately easy. Core cloud and infrastructure integrations were straightforward with proper documentation, while fine-tuning policies and access workflows required some initial effort. Once configured, the integrations have been stable and reliable.

For integrating One Identity Safeguard, figuring out how password rotation works is a bit difficult because we have to make custom integrations. After that, it was no problem really.

One Identity Safeguard is flexible and provides out-of-the-box integrations that have been very helpful for me, and the installation process was quite easy and smooth, which I would also rate as a feature.

The integration with Active Directory was straightforward.

The integration with Active Directory was complex during the initial setup, but later we found it to be very smooth, requiring proper planning in advance.

The integration process for One Identity Safeguard was moderate. Basic integrations, such as Active Directory and standard systems, were relatively straightforward and well-documented. However, the more advanced integrations required some custom setup, additional configuration, and some troubleshooting. Overall, it is not very difficult, but it does require some technical knowledge and planning to implement smoothly.

Integrating One Identity Safeguard with systems such as Active Directory, Microsoft Azure, and SIEM tools was fairly straightforward with some learning curve in the initial phase. Active Directory integration is the easiest. It was the most seamless part. One Identity Safeguard has native support for AD, so user import, authentication, and role mapping were quick to configure. We were able to set it up with minimal effort, and it works reliably from day one. Azure integration required moderate effort. Integration with Azure was smooth but required proper configuration of roles, permissions, and connectors. Once configured, it works well for managing privileged access to cloud workloads. From a SIEM perspective, sending logs to SIEM tools such as Splunk and other tools required more fine-tuning. We had to configure log forwarding, normalize data formats, and set up correlation rules on the SIEM side. The initial setup took some time, but once done, it provided strong visibility and alerting capabilities.

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.

The integration of One Identity Safeguard with my DevOps environment and cloud applications was generally smooth, especially with standard systems, but it required some initial configuration and fine-tuning to align with my DevOps workflow and core cloud applications.

The integration of One Identity Safeguard with systems such as Microsoft Azure and Active Directory was generally manageable but required some planning and technical understanding. The core integrations were fairly straightforward with available connectors and documentation. However, certain configurations, especially around secure credential handling, session policies, and aligning with existing workflows, took additional effort and testing. In some cases, we faced minor challenges with fine-tuning permissions and ensuring seamless automation in DevOps processes.

The integration process was balanced because of moderate challenges but manageable overall.

The integrations were manageable overall, especially with Active Directory and standard Windows and Linux environments. Cloud integration with AWS and Azure required additional planning and configuration, but the documentation and available connectors helped. Some advanced integration and custom workflows were more complex and required careful testing and coordination with security and infrastructure teams.

The integration part seems a bit challenging because some tools cannot be integrated properly with it.

The integration with the cloud targets was somewhat complex initially, but it became easier after understanding the entire process of integration. After acquiring an integration specialist, everything became very easy and user-friendly.