<\/p>\n\n\n\n
According to some recent research by our friends at One Identity, only 8% of companies have fully automated provisioning processes and 70% rely upon manual operations for joiner \/ mover \/ leaver events. Yet, despite many downstream manual processes, many organizations feel they\u2019ve ticked the IGA checkbox.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Let\u2019s start with critical systems: these are well covered by IGA\u2019s and usually fully automated. Next comes the legacy and specialized systems: these generally aren\u2019t automated by the IGA – these get sent to the service desk for fulfillment. Finally, there\u2019s the operational, non-account management workflows that are generally manual: creating a badge, provisioning a phone, ordering business cards, etc. <\/p>\n\n\n\n
From the IGA team\u2019s perspective, it\u2019s completely automated. An HR event occurs, which creates a downstream sequence of events. The IGA team has done well. It\u2019s all integrated and flowing.<\/p>\n\n\n\n
From the business perspective, the picture is very different. It is not automated, nor is it fully orchestrated. People are manually processing tickets at a huge cost. The business doesn\u2019t have visibility into the process, its state and\/or exceptions until problems arise. It\u2019s difficult to direct staff to address problems that are not visible. HR often has some visibility into the challenges but they don\u2019t own the processes. This disconnect is costing the business in many ways. <\/p>\n\n\n\n
Let\u2019s look at some of the challenges.<\/strong><\/p>\n\n\n\n Specialized systems are typically very costly to integrate into IGA. Custom connectors have to be built and the cost is often seen as excessive, so the org lives with manual processes. The IGA calls for provisioning and a ticket gets created where a system owner gets flagged to create the account through a legacy interface. There\u2019s no off-the-shelf connector and the cost to create one is prohibitive – especially when considering the number of these systems that linger. Some orgs will rationalize that these systems are going away soon, but they often continue to linger for years.<\/p>\n\n\n\n If the org has chosen a latest-greatest IGA, then many mainstream cloud apps will be covered. Most cloud vendors support SSO, but not always with the org\u2019s SSO provider. The business will often demand access to specialized cloud apps where connectors don\u2019t exist. These apps are especially problematic as SSO is your best line of defense for cloud apps during terminations. Without SSO, a user may access the cloud app for days until a ticket is manually processed. Many of the older IGA\u2019s lack cloud app connectors leaving the business in a difficult position. Live with manual operations or rip and replace the in-place IGA. <\/p>\n\n\n\n IGA\u2019s are getting better in this department but there\u2019s still quite a gap for many organizations that requires a lot of custom scripting in their ITSM. This is costly development. ITSM vendors charge dearly for these automations and ongoing maintenance is problematic.<\/p>\n\n\n\n Then there\u2019s the business processes (business cards, phone, badge, etc) which are just accepted as being manual operations – nothing that can be done. So the org just accepts it and lives with the inefficiencies, often without realizing just how much it\u2019s costing and compromising the agility of the organization.<\/p>\n\n\n\n So, what\u2019s the cost?<\/strong><\/p>\n\n\n\n Onboarding is slower than it should be and it\u2019s not completely reliable. Ever had an employee start and on day one they don\u2019t have a phone, badge or worse, a computer? HR people will attest to this problem. Human beings are fallible and that means the processes are likewise subject to exceptions. <\/p>\n\n\n\n With manual processes the key stakeholders like hiring managers don\u2019t have visibility into process exceptions. With insight, they could have rectified an exception without business impact but instead suffer embarrassing process failures. <\/p>\n\n\n\n This one is a security issue. When there\u2019s an emergency departure, IGA systems often can\u2019t respond in a timely manner. Further, the downstream processes are all manual. Orgs have relied upon the perimeter and SSO to ensure that an account is disabled, but most experts agree that many back-doors remain open for days, or longer after a termination. With emergency terminations, significant damage can be done during this gap.<\/p>\n\n\n\n An organization is nothing without its people. These are the people that drive it forward, make it competitive, they innovate, they invent, they are loyal. Yet, these are the people that an org has processing thousands of tickets each month; grunt work – a perceived necessity. By automating the massive backlog of tedious repetitive tickets, employee retention and satisfaction give an organization a competitive edge.<\/p>\n\n\n\n That new star sales executive starts and can\u2019t login. A customer list is stolen because an account didn\u2019t get shutdown. A new engineer starts and doesn\u2019t have a computer. A manager can\u2019t access her Microsoft Teams resources because the assignment failed and wasn\u2019t detected. There are countless cases that most organizations have suffered. They collectively create a state of disruption at a huge cost to the business.<\/p>\n\n\n\n The READI Identity Automation platform enables an organization to easily integrate all of their systems into their IGA workflows. Based on a low-code automation platform, universal connector technology, and seamless REST integration, organizations can quickly and easily extend their IGA reach into all systems – closing the gap for all joiner \/ mover \/ leaver events. It\u2019s never been faster or easier to achieve and manage full automation.<\/p>\n\n\n\n Identity Automation brings orchestration and exception alerting to the manual processes. While warm bodies and tickets and may still be required, Identity Automation can orchestrate, track and ensure that things get done so that exceptions are caught and resolved, avoiding business impact. The hiring manager always retains visibility into the state of their hire. When things go off the rails, as they sometimes do, the key stakeholders immediately get alerted.<\/p>\n\n\n\n There\u2019s no better proof than real-world results. One of our enterprise customers with over 100K employees eliminated the manual labour of 13 IT staff and reduced their onboarding SLA from 72 hours to just 4 hours. The process which involves over 40,000 weekly operations is visible in a dashboard that allows them to monitor all operations (automated and manual) along with SLA metrics and obtain early warning of any problems. In only 9 months, a calculated direct ROI of approximately $1,000,000. The 13 staff have been re-provisioned into strategic digital transformation projects; not previously possible. By closing the identity gap, the organization avoided additional hiring. With one initiative, they retained and repurposed valuable staff and improved overall employee satisfaction with both the IT technical staff and the business stakeholders. <\/p>\n\n\n\n Getting started is easier than you think. The Readibots team and our trusted partners are here to help. The Readibots advisory service is designed to assist with as much of the workload as an organization would like. From onboarding and training to full implementations, the READI team will provide a professionally managed experience. For more information about Identity Automation, visit: www.readibots.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" According to some recent research by our friends at One Identity, only 8% of companies have fully automated provisioning processes and 70% rely upon manual operations for joiner \/ mover \/ leaver events. Yet, despite many downstream manual processes, many organizations feel they\u2019ve ticked the IGA checkbox. So, where\u2019s the disconnect? Let\u2019s start with critical<\/p>\n","protected":false},"author":6,"featured_media":532,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"none","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","footnotes":""},"categories":[12,14],"tags":[98],"class_list":["post-528","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-featured","tag-identity"],"acf":[],"_links":{"self":[{"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/posts\/528","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/comments?post=528"}],"version-history":[{"count":1,"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/posts\/528\/revisions"}],"predecessor-version":[{"id":531,"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/posts\/528\/revisions\/531"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/media\/532"}],"wp:attachment":[{"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/media?parent=528"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/categories?post=528"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/readibots.com\/staging\/wp-json\/wp\/v2\/tags?post=528"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Legacy Apps<\/strong><\/h3>\n\n\n\n
The Cloud and SaaS apps. <\/strong><\/h3>\n\n\n\n
Custom business rules and conditions. <\/strong><\/h3>\n\n\n\n
Non-Account Processes<\/strong> <\/h3>\n\n\n\n
Inability to \u201chit the ground running\u201d – slow and unreliable onboarding<\/strong><\/h3>\n\n\n\n
Stakeholders in the dark<\/strong><\/h3>\n\n\n\n
Business Impacts<\/strong><\/h2>\n\n\n\n
Inability to rapidly terminate<\/strong><\/h3>\n\n\n\n
Innovation and corporate wellness is compromised<\/strong><\/h3>\n\n\n\n
Embarrassing business hiccups<\/strong><\/h3>\n\n\n\n
Is there a better way? Yes! Identity Automation!<\/strong><\/h2>\n\n\n\n
What about manual business processes?<\/strong><\/h3>\n\n\n\n
The Business Impact of Automation?<\/strong><\/h3>\n\n\n\n
Getting started?<\/strong><\/h2>\n\n\n\n