What is most valuable?
User Access Review, User Access Request and SOD Policy detection. Another important feature is IdentityIQ’s provisioning broker which allows us to either use its built-in provisioning engine or easily integrate with third-party provisioning and help desk/ticketing systems (such as IBM TIM/SIM, Oracle IdM, BMC IDM, BMC Service Desk, Novell IdM, Microsoft Forefront IdM, ServiceNow etc.) The backend provisioning of IdentityIQ is lightweight and fast to implement. Generally account provisioning can be setup in days versus weeks as is the case with some of the competing products.
SailPoint’s roots began with governance and compliance in 2006. Over time the IdentityIQ compliance and governance stack (user access reviews, SOD and access request) has evolved to provide deeper and more flexible functionality than we’ve found with competitors.
How has it helped my organization?
We’ve used IdentityIQ to help customers update their ‘paper and spreadsheet’ based user access review processes. This has helped customers increase the efficiency of access reviews, reduce workload, increase oversight of access remediation as well as start to fulfill regulatory and audit compliance requirements that where previously unattainable.
We’ve seen organisations go from detecting and reviewing high-severity SOD Policy violations once or twice a year to being able to detect and remediate SOD violations in the same day. IdentityIQ provides the detection, enforcement and traceability to take the manual, paper-based policies into real automated rules.
Many of our customers have also used IdentityIQ to replace homegrown and out dated access request solutions (some even manual and paper based), as well as migrate away from expensive and difficult-to-implement provisioning systems. Implementing IdentityIQ has allowed customers to reduce the cost of on-boarding applications into enterprise access review and access request processes as well as tightly integrate access request and remediation with approval workflows and back-end provisioning.
What needs improvement?
Unlike other competing products IdentityIQ is designed with end-users in mind rather than just targeting the IAM system administrators, we would like to have a bit more flexibility in how the screens are laid-out and the content. Some of our clients prefer feature-rich UI/screens whilst other would like to have simpler interaction and presentation.
Dashboards – whilst better and more feature rich than a number of competing products, they are still nowhere near the functionality one gets from dedicated portal and analytics tools (eg. drill-downs, comparative views, etc.).
Report writing is much better in the latest versions, but it is still not comparable to what one can get out of dedicated reporting tools.
For how long have I used the solution?
I started working with IdentityIQ in 2007. Until now, I’ve been actively involved in design and configuration of a large number of IdentityIQ deployments across Australia, Asia, America and the Middle East. We (First Point Global) have been a SailPoint partner since 2007.
What was my experience with deployment of the solution?
In terms of the product itself - no. Deployment of the product is very straightforward; there are a lot of resources available to assist you in finding the answer to any deployment question you might come up with. There is a large community of people working on IdentityIQ. If you come across a problem there’s always someone around that’s done that before and has suggestions.
The main challenge has been that each client’s environment is different; from the way in which they configure their ‘managed’ systems, to constraints imposed by the client’s SOE (standard operating environment), to the client’s infrastructure topology, to change control and migration processes and tools the client wants to/has to use.
One of the main challenges is for clients to understand and accept that IdentityIQ implementations are not a systems development/coding exercise; rather IdentityIQ deployment is more about configuration than coding.
What do I think about the stability of the solution?
No, IdentityIQ is stable. It has easy, built-in redundancy to handle any unforeseen events. Also, server management is simple and easy to understand.
What do I think about the scalability of the solution?
IdentityIQ scales well both vertically (‘bigger’ servers) and horizontally. When load increases additional servers can be added to the UI or task server groups with minimal configuration effort. IdentityIQ supports the notion of having dedicated UI servers handling user interaction and task servers, which handle background activities (eg. data loading and refresh, generating reports, re-evaluating SOD policies, etc.). IdentityIQ manages its own batch server load balancing in the background. SailPoint also provide whitepapers and supporting materials on tuning your IdentityIQ deployment to meet your needs and your environment.
However, we have encountered issues using IdentityIQ on virtualized platforms. These were caused by the virtualization hosts being overloaded (i.e. several virtual machines on one overloaded host). If you are going to virtualise IdentityIQ application servers, I would recommend allocating vCPU and memory to each virtual machine. If resources are not allocated, IdentityIQ can be starved by other virtual machines running on the same hosts.
How are customer service and technical support?
Great, SailPoint offers several points of contact. You can use either the SailPoint communities, customer portal (Salesforce-based) for management of support cases and queries, or directly contact your professional services manger or engagement manager. SailPoint has staff located in most geographies and it’s easy to get hold of someone technical when you need a hand. Technical Support
Excellent, SailPoint provides both customer and partner community forums; SailPoint technical staff, partners and customers actively contribute to these forums. Often you can find the answer to a question in a forum without the need to raise a support ticket. The communities are an invaluable repository of technical knowhow as well as a source for documentation, tutorials and videos. SailPoint also holds regular webinars. These and all whitepapers are stored and made available to the community. By using the community, it’s possible to find out who has done it before, see what solutions they came up with, as well as even contact that person to ask questions. It’s a great way to get to the bottom of something quickly.
SailPoint support engineers are located in most geographies so your questions get answered quickly. The SEs are also approachable and easy to work with.
Which solution did I use previously and why did I switch?
As a company we implement identity solutions for customers. We’ve implemented a variety of product replacements and migrations, including:
Oracle Identity Analytics (OIA) replacement (formally Sun Role Manager and Vaau RBAC), OIA lacked the flexibility and functionality to meet the customers’ SOD (Segregation of Duty) Policy requirements as well as entitlement and role modeling requirements. Lack of industry resources with implementation product knowledge was also a factor in retiring OIA solutions; lack of supported application connectors (and/or complexity, eg. requiring fully functional implementation of Oracle IdM for OIA to function) was another factor.
BMC IDM / Control-SA, we’ve implemented both Control SA replacement, and more recently we worked on Control SA end-of-life migration projects. SailPoint offers a clear migration strategy to replace existing Control SA/ESS deployments. SailPoint acquired the BMCs IDM/Control-SA Connector stack people/technology to make migration much simpler exercise; replacing Control SA/ESS can be as simple as configuring the application connectors in IdentityIQ and pointing them to the existing Control SA Agents or Service Manager. Since acquiring the BMC ESS Connector stack, SailPoint has started rewriting the connectors into agentless Java connectors which are simpler to use. Some legacy connections still require agents i.e. RACF, ACF2, NIS.
Prior to compliance and governance solutions coming to the forefront of identity management, we found our customers were starting to think about and “roll their own” solutions to complement the gaps in their IdM stacks; this often involved attempting to ‘bolt on’ access reviews and SOD functionality into existing provisioning systems.We’ve worked with customers to replace several in-house developed solutions, including customer-developed Access Request, User Access Review and even a custom developed Provisioning system! In each case the customer chose to migrate off their home-rolled solution to take advantage of the savings offered from an out-of-the-box solution as well as take advance of the deep compliance and provisioning functionality that IdentityIQ offers.
How was the initial setup?
Installation requires knowledge of application servers and relational databases; a high availability environment can be setup in a matter of hours-days once infrastructure is in place. IdentityIQ requires a relational database and supports all the main flavors, Oracle, IBM, Microsoft, MySQL; IdentityIQ runs on a Java application server, again the common platforms are supported, Oracle, IBM, Apache Tomcat and Red Hat JBoss.
What about the implementation team?
We (First Point Global) are a solutions integrator specialising in identity management; a typical project implementation team involves First Point Global consultants with years of experience in deploying IdentityIQ into large organisations. We work with and train the customer team to up-skill employees to assist in transfer of the IdentityIQ solution from implementation to BAU.
Of course you will always rate yourself as high, but we are the largest team of IdentityIQ implementers in APAC. Also, we won the SailPoint Amarda Award in both 2013 and 2014 for SailPoint’s top partner in the Asia Pacific region.
What was our ROI?
Through our implementations we’ve seen the existing manual access review processes shrink from a team of people used to gather, send and review certification results down to one or two administrators. Gathering of account data, sending of access review notifications, escalation of incomplete access reviews and detection of remediation is all automated. Administrators can focus on reviewing the results not doing the heavy lifting, results can be easily summarised for the people that need it.
IdentityIQ is still a relatively new comer to identity management, but its implementation is modern and it has built on the lessons learnt from the older, harder to use and often cryptically complex provisioning systems. Workflows and connections to applications do not need to be complex and take far less time to implement than heavy provisioning systems.
IdentityIQ is quicker to implement than its pure provisioning counterparts, implementing IdentityIQ for compliance and governance means you can later reuse the existing on-boarded application connections to implement provisioning.
What's my experience with pricing, setup cost, and licensing?
The cost associated with setup depends on the scope of work, and largely the extent of integration with the applications to be on boarded as well as the functionality applied to those applications (i.e. access review, access request, provisioning, roles, SOD, etc.).
IdentityIQ is a very flexible product. We’ve found the key to using it well and getting the best value for money is to determine how to model your access review, access request or provisioning processes in IdentityIQ, then apply that to a majority of applications. If applications require unique processes for each department, there can be additional configuration overhead, aim for economies of scale where possible.
Some examples of projects:
-30 day IdentityIQ ‘quickstart’ project, on-boarding of 7 high-risk enterprise applications + HR feeds. User access reviews configured and kicked-off in production.
-90 day Control SA migration project, migration of hundreds of provisioned applications into IdentityIQ. And replacement of Control SA Password Management and Access Request functionality with IdentityIQ
-100-200 days IdentityIQ governance project, on-boarding of all enterprise applications into IdentityIQ to perform regular access reviews and detect SOD violations as they occur.
For day to day running of IdentityIQ post implementation we generally advise a small administration team of 2-3 people; some of our clients are supporting IdentityIQ deployment with a 0.5 FTE. Administrators are responsible for performing general house keeping as well as fielding queries on access reviews and scheduling access reviews, new application on-boarding and patching.
Which other solutions did I evaluate?
We’ve reviewed Oracle Identity Analytics (OIA) and RSA as well as the Dell offerings. Of the three we found RSA Aveska the closest competitor to SailPoint; the Oracle and Dell offerings do not have the same depth of functionality. When doing feature-by-feature comparison as is in a typical RFP/RFQ the majority of IdM products look the same. There are two areas where IdentityIQ often proved to be better than competing products were ‘time to market’ (i.e. how long it takes and how much effort is required to start addressing real issues and delivering value to the business) and complex user access review scenarios.
What other advice do I have?
Listen to the vendor and other clients who have successfully implemented the product; lots of, problems with hardware and implementation process can be avoided by taking the advice of those who have been there before.
Ensure the project has strong leadership. You’ll need this to ensure cooperation of system administrators that are often protective of access to their applications. You need to configure provisioning, but administrators will only give you a read-only account until it is proven it works and will not cause problems. Or enterprise architects may insist that all integration has to be done through corporate middleware, requiring lots of custom development, rather than using OTB connectors.
Make sure your hardware meets the SailPoint requirements (see the ‘IdentityIQ Performance Optimization Checklist’ on SailPoint’s forum - this details the required hardware and network requirements at a glance). IdentityIQ supports virtualisation nicely, but you do need to make sure your virtualisation hosts have enough resources to meet IdentityIQ processing requirements. We suggest allocating CPUs and memory to IdentityIQ application hosts to ensure dedicated usage of required resources.
Make sure your database and application servers have a low latency round trip. We recommend putting the two in the same data centre. IdentityIQ is a big user of data - lower the time it takes to retrieve the data and the UI and batch tasks perform snappier.
Install your development environment to get started with IdentityIQ, then read the ‘IdentityIQ Performance Management Guide’ to ensure that all non-development environments are installed and tuned correctly for your infrastructure. A tuned environment is a fast environment; and fast environment means happy end-user. Also, make sure your administrators do regular health checks.
Deploying IdentityIQ is an integration task, use agile development to on-board applications quickly, have a simple to document application template to capture integration details, but remember you are not designing a system from the ground up. This is not a Java/VB/C++/you-name-it coding exercise.
Using OOTB means fast implementation times and lower cost to you. IdentityIQ is flexible but customizing everything will add to your costs now and your maintenance later. Keep it simple and keep the process standardised.
How often do you need to refresh the data? The hardware required to run IdentityIQ is largely dependent on how often you configure IdentityIQ to reload the data. How often the data is really required to be reloaded is largely dependent on the features you are using,. For example, SOD policy violation detect might require daily updates, but reviewing user access quarterly does not require daily data refreshing!
If you do want to keep all data up to date, then be smart and take advantage of IdentityIQ’s delta aggregation and partitioning functionality. Build application on-boarding tuning into your application on-boarding process and have database administrators review queries for performance.
Always utilise the direct connectors. Although IdentityIQ supports a variety of file feed connectors using the direct connectors now means you can take advantage of provisioning later without reconfiguring. Remember file feeds are unlikely to match the data the direct connector will pull back, reuse the investment SailPoint have made in the OOTB connectors and save time and money!
Standardise the compliance processes applied to applications. IdentityIQ is flexible but a unique access review process for each application will require more configuration and maintenance. Keep it simple and easy to maintain.
IdentityIQ has been the market leader according to the Gartner IGA Magic Quadrant for the past two years. We deploy and support several identity and access management products, and have reviewed numerous other vendors’ offerings.On balance we find IdentityIQ to have the best mix of functionality and ease of use, as well as being the easiest and most flexible to deploy.Quite a few of our engineers prefer to use and deploy IdentityIQ over other compliance, governance and provisioning solutions.