What is our primary use case?
My main use case for Idira IGA is to ensure our systems are properly secured, and we also make sure we are adhering to government policies while maintaining the standard and security of the data. When considering employee onboarding or offboarding, we manage how we provide access reviews and how permissions are leveraged when a role change happens for that particular employee.
When managing employee access during onboarding or role changes, I refer to managing the employee's access to development tools, cloud infrastructure, and enterprise applications. For instance, an engineer working on a cloud-based service needs access to GitHub repositories, Jira projects, and a couple of AWS deployments. When the engineer requests access to production environment systems, Idira IGA checks the employee's role through the approval workflow and routes the request to the appropriate manager or application owner.
The engineer receives least privilege access, which grants only the permissions needed to perform his task. Periodic access reviews are performed by a manager to determine whether the engineer still requires those permissions, and if an employee leaves the organization, unnecessary permissions are revoked to prevent any potential misuse.
One major aspect of my main use case is that we are primarily focused on keeping the data secure. The data needs to be secure, and only the privileges that are accessible and needed for a particular user are provided, instead of granting all different kinds of access to the user.
How has it helped my organization?
Idira IGA has positively impacted my organization in several significant ways. One example is faster access reviews. We have approximately 10,000 to 20,000 employees whose application permissions require quarterly review, and with AI-assisted automation, managers can now prioritize unusual or high-risk permissions instead of manually examining everything, resulting in a noticeable reduction of time allocation.
Additionally, we see faster onboarding for developers, as the automated standard access requests allow them to start working sooner and contribute to organizational growth by increasing productivity. I also see reduced security risk as an impact since engineers or employees who transition between projects may retain access that could lead to serious security concerns.
We save about 70 percent of our time now on access reviews and evidence collection due to the automation that has simplified the process. Previously, we conducted manual checks for various employees' permissions, which was a hectic task.
Automation has made a significant impact on our access reviews by reducing manual efforts, improving accuracy, and speeding up overall processes. Previously, our security team managing various projects manually assigned resources to new employees and managed roles and permissions, which was a complex task exacerbated by a large number of employees. With Idira IGA, we now streamline these processes, allowing our team to focus on enhancing productivity rather than getting bogged down in manual assignments.
I have seen improvements like saved time and increased organizational productivity since implementing Idira IGA, which automated previous manual processes.
What is most valuable?
The best features of Idira IGA include automated access provisioning, which helps automate the employee's access when they join, as well as revoke access when they leave. Role-based access governance ensures that employees receive access appropriate to their responsibilities, and identity risk visibility helps security teams identify excessive permissions and potential risks. Additionally, the audit and compliance feature provides visibility into access decisions and necessary licenses, making security management and the audit process significantly easier.
The feature that has had the biggest impact for my team is improved security, which helps us make decisions faster and assists in identifying excessive, outdated, and unnecessary permissions before they become security risks. Centralized identity governance and automated access management have been hugely beneficial for us.
The best features include automated access management, AI-assisted access reviews, and centralized identity governance.
Idira IGA's AI capabilities focus on how things can be automated, analyzing and recommending appropriate changes based on permission information. It identifies risky permissions and orphan accounts, providing a broader Idera platform that manages privileges and audits actions while delivering AI-driven access recommendations for least privilege access.
For a real-world example, if a developer moves to a different project but retains access to the previous project's environment, Idira IGA could help identify that access during a review and recommend its removal, allowing the manager or security team to validate the recommendation before executing the revocation. This results in reduced security risk, faster access reviews, and less manual effort.
Idira IGA generally meets our accuracy expectations, particularly with accurate access recommendations and effective risk identification to prioritize suspicious access. Automated governance workflows contribute to consistent access management. However, there are still areas needing improvement, such as managing false alarms when legitimate access is flagged as risky.
What needs improvement?
I perceive an area for improvement in Idira IGA, specifically in simplifying integrations with enterprise applications like AWS and Salesforce, where the complexity can increase the time and effort of implementation. Improved reporting needs focus on providing clear visibility into access risks and overdue certifications to move the business faster, alongside better automation for role changes to quickly identify outdated permissions.
I chose 9 out of 10 because the core capabilities address important enterprise security challenges. However, I would still like to see more accurate AI recommendations, fewer false positive alarms, and easier integration with existing applications to make it a perfect 10.
For how long have I used the solution?
I have been using Idira IGA for more than six years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
Idira IGA proves to be scalable across various systems, with no specific limits on the number of employees. It efficiently scans for new employees joining or being assigned to specific projects at regular intervals.
How are customer service and support?
The customer support is great. Whenever I raise a request, they take care of the situation and resolve issues quickly. I would rate the customer support as a 9 out of 10.
Which solution did I use previously and why did I switch?
We previously used Okta but found it too complex and costlier, which prompted us to switch to Idira IGA.
How was the initial setup?
Our previous IGA solution took around three months to deploy, which included around one to two weeks for initial setup and configuration, two to four weeks for integration, and two weeks for access policies and approvals, totaling six to twelve weeks based on complexity and scope.
Idira IGA took us around three weeks to deploy. Compared to past solutions, our Idira deployment was much faster. The integrations were the longest component, but task-wise, the completion occurred at a much quicker pace.
What was our ROI?
There is a definite return on investment since we cut down significantly on manual efforts. The time spent resolving issues is now faster and more efficient, allowing users to work earlier with the right permissions.
Which other solutions did I evaluate?
We primarily only evaluated Idira IGA before making our decision.
What other advice do I have?
I rate Idira IGA as 9 out of 10. Organizations looking into Idira IGA are likely to benefit significantly, especially larger enterprises that wish to streamline their processes while ensuring secure access.
However, smaller organizations might find the licensing a bit expensive.
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?
Amazon Web Services (AWS)
