Developing Custom Automated Workflows with Idira Identity Flows

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Idira Success Blogs
14 min read
L4 Transporter
Organizations often struggle to get time and resources from their internal development teams to create custom automation for internal processes, or those in administrator or operator roles lack the background to develop it themselves. This lack of automation leads to disjointed and manual processes that are “MacGyvered” together with duct table and bubble gum. This doesn’t have to be the case for your identity-related workflows when using Idira Identity Flows. In this article we’ll describe how organizations can design and implement custom automated workflows using Idira Identity Flows with no coding or development background required.

Introduction
The number of identities that need access and the number of applications required to keep the business humming have exploded in recent years. With this explosion of access and applications, comes a corresponding increase in process – joiner, mover and lever functions required to propel the business forward. Every organization can benefit from automating workflows and business processes, providing them with improved efficiency and security posture.


The Challenge
To address and remediate the security risks associated with a lack of automated workflows, we must better understand why organizations often leave manual processes in place and what it means from a security perspective.


Organizations often struggle to get time and resources from their internal development teams to create custom automation for internal processes, as development resources are often prioritized for revenue generating applications and services. This leads to disjointed and manual tasks that are “MacGyvered”  or “jerry-rigged” together with duct table and bubble gum.

There are many applications and services integrated into the identity-pipeline, which means the scope and scale of places to integrate automation is vast. Manually collecting data and using external applications without automation allows for security threats to creep into the process. There are more insecure points along the way in the process that a malicious actor could compromise, and the longer it takes to execute identity-related workflows, the longer the window of opportunity for malicious actors to compromise them.

When data exist in multiple repositories and data sources, using a manual process can lead to decreased productivity through inefficient use of time and resources, increased risk, and vulnerability to cyber-attacks when security threats go undetected. Process automation is becoming less of a “nice-to-have” and more of a “must-have” with each passing day.

The Solution
Idira addresses these challenges using a low-code, visual editing drag-and-drop interface that includes pre-built and customizable connectors, allowing you to connect to a plethora of external applications. By following the guidance below, you’ll be able to automate your identity-centric workflows without the need to be solely reliant on other resources. We can achieve this through identity management controls from Idira Identity Flows.


Identity Flows is an orchestration tool that eliminates manual tasks and processes with the creation of automated workflows. Automating these workflows can lead to improved IT efficiency while allowing resources to focus on strategic tasks, eliminating the security risks posed by privilege creep, orphaned accounts and provisioning mishaps, and enablement of security controls for user access, strengthening the response to potential attacks.

Workflows can be created that integrate with applications, users and devices, and can collect data for those flows through user-input forms or APIs integration with other services. The result is highly customizable workflows that perform complex tasks against a variety of systems in one fowl swoop.
ka3Ht0000000q9mIAA__eid=ka3Ht0000000q9m&feoid=00N2J00000APFDu&refid=0EMHt0000061Fuv.png
Figure 1: Solution Overview Example Diagram

Common Use Cases for Automated Workflows
Below you’ll find two examples of common use cases for automating identity-related workflows.


Example 1: Identity and Lifecycle Management
Onboarding and offboarding users can be time-consuming, daunting tasks that sap resources. Identity Flows can simplify complex business processes throughout the entire employee lifecycle. One popular use case is HR-driven identity, where an HRIS system API is integrated into Flows to create and update end-users in a directory service such as Microsoft Azure Entra ID or AD, then granting permissions and assigning specific resources utilizing SCIM provisioning through an IdP such as Idira Identity. The result is a role-based IAM lifecycle process that’s fully automated based on HR-driven events.


Example 2: Security Orchestration Automation Response (SOAR)
Another common use case for automated workflows includes automating identity-responses to security events. In the event a threat occurs, and that insight is feed to Flows, a workflow response can trigger downstream events like incident ticket creations or access revocation. Let’s say a third-party security tool detects anomalous user behavior, we may want to create an incident ticket to the SoC or security team to investigate, send an email or Slack message to the user about the incident and potentially revoke access to the application the incident occurred on (if egregious enough an event).


Example Walkthrough

Figure 2: Idira Identity Flows Example Walkthrough

The Art of the Possible
It would be nearly impossible to provide an exhaustive list of every automated outcome that Identity Flows might provide. Equally as difficult would be listing every application Identity Flows integrates with, since virtually any app with an API is eligible. Flows’ flexibility is truly only limited by your imagination. But in the interest of creativity, let’s explore the art of the possible and showcase other frequently automated workflows:
  • Use Flows to allow complex criteria for safe access through Idira PAM such as membership in groups from multiple AD domains
  • HR solutions like ADP, Namely, and Workday be used to automate onboarding and offboarding in an IdP or directly into your Active Directory
  • Ticketing solutions like ServiceNow can be integrated directly with a chat app like Slack for notifications
  • Moving users into various roles and organizations inside of Idira Identity (or any other IdP) for access and privilege automation
  • Create triggers from other applications and turn them into Slack messages as a notifications to end-users
  • Integrate with Salesforce to generate email or message notifications upon opportunity status change
Understanding the Functions and Parts of a Flow
In order for you to build your first flow, it’s important to understand the various functions at your disposal and the parts of a flow. Below you’ll find explanations for each core component or function within Flows, along with resources to learn more about them.


Triggering a Flow
There are three methods to trigger a Flow to kickoff and run: user events, calling an endpoint and via a scheduler. User events include actions like clicking on a microapp or completing a web form. Endpoint calls are invoked by other applications or scripts reaching out to a dedicated API endpoint for your Flow. The last method is via the native scheduler, where you can define whether you want the Flow to run on a predefined internal or custom dates (e.g., every X minutes, daily, weekly, on ABC date and at what time).
Learn more about triggering a flow.


Connectors and Custom Endpoints
Connectors and custom endpoints essentially perform the same function; they define operations that can be performed against APIs. Connectors typically reference the out-of-the-box catalog of third-party applications, such as Slack, Google or Microsoft. You can find these OOTB connectors under "Connectors > Templates". Custom endpoints allow you to easily connect to anything and build any type of connection to applications and systems with APIs. Think about using custom endpoints when an OOTB connector doesn’t exist for your API of choice. You can create new custom endpoints via "Connectors > Templates > Create".
Learn more about connectors and creating custom connectors.


Authentication
As any user or workload does, your Flow is going to need to authenticate to these various API endpoints that you’re including. On each connector (or custom endpoint), you’ll need to configure your authentication and authorizations for the application or endpoint. This will allow your connectors to authenticate to the API and perform whatever functions you’ve defined.
Learn more about connector authentication.


Mapping Data
Since the intent of Flows is to automate complex processes between distributed systems, we’re going to need to manipulate and move data around. Mapping data allows you take information you’ve collected via an API call and use it in another API call or function. In Flows, you can map collected values, and transformed values into any app. When configuring actions, you are defining how data is transformed and mapped for every action.
Learn more about mapping data.


Components
Components are the various decision-making logic and actions that you can include into your flows. You can use the components to evaluate expressions, add delays, and have concurrent operations running, combined with the mapping engine and data transformation/formula engine. There are four types of components: conditions, utility, data and forms.
  • Conditions
    Conditions are logic actions that allow you to design how you want your flow to perform. These include actions like branching, split decision, join delay, delay concurrent, loop, loop break, loop continue and transform data.
  • Utility
    Utility components are additional helpful actions, such as sending an email from an SMTP server, that can be used throughout your flow.
  • Data
    Data components allow you to perform data store related actions in your flow, such as create temporary data stores in your flow, read, update and delete data, and manage the databases in your flow.
  • Forms
    Forms components allow you to add your own form with custom fields into your flow. Forms can be created as templates that can be saved and re-used later, or immediately create a form on the fly and add it into your flow. Forms allow you to collect data from an end-users or map existing data to a form field and utilize it for additional actions and connectors.
Learn more about adding components to your flow.

Implementation
Before you begin building your first flow, start by identifying two items in your company: which process is the most painful in your organization and which process would be the simplest to solve. These may be identity-related processes or completely unrelated to access management and identity security. Think about the things that you have control over or the ability to influence.


For a quick win and to get your feet wet with Flows, implement a simple one first. This might be as easy as setting up a Slack notification after a certain event in Salesforce or sending an email to HR when a user completes a series of tasks. You’ll want to outline each if/then scenario in a plan to identify the triggers and actions for a particular outcome.

Step 1: Build the Plan
At the heart of any successful project is a great plan. Start by deciding what the desired outcome is. It is helpful to put the steps needed in order “on paper” or by using diagram software.  Identify the triggers needed for each step including the software, action, or event necessary. In some cases, a step might be an if/then statement, causing your diagram to fork. Note all the variables in your plan.
ka3Ht0000000q9mIAA__eid=ka3Ht0000000q9m&feoid=00N2J00000APFDu&refid=0EMHt0000061Fuw.png
Figure 3: Using Diagram Software Can Help Visualize the Plan

Step 2: Identify the Stakeholders and Admins
In order to complete the authentication process for each connector in Flows, you’ll have certain access to that piece of software. In most cases, Flows will need permission to access the API of each application included in your automation.  What operations can be executed in the third-party apps are defined by connectors. You’ll need to identify who in your organization will have access to the permission level needed to integrate each application into Flows. For example, often HR applications have a process for accessing their APIs, so getting started early in the process will save time later.


Similarly, if you need the buy-in of stakeholders or executive leadership, now is the time. Communicating about the upcoming changes and sharing the value of added efficiency, saved resources, and automation can help overcome the natural human nature’s fear of change. Lean on our Change is Hard guidance for tips on overcoming pushback driving the success of your security initiatives.

Step 3: Build your Draft Flow
You’re finally ready to create a Flow! 
  1. Whether you start with a template or drag an endpoint into the flow, Flows will read the connector for desired authentication types. You’ll need to authenticate through an Authorization before running or testing the flow. Configuring your Authorization is as easy as giving it a name, picking your auth type and providing the authentication details. Once your Authorization is configured, you can continue to re-use it throughout your Flows.
  2. Add your components as necessary to create the logic in your Flow. It’s here where you’ll add things like conditions, utilities, data and forms to perform the various actions you’ve defined on your “paper” flow diagram.
  3. It is common for your automation to use information retrieved in an earlier step. Use the fields under the Map column to map relevant data within your APIs and components.
ka3Ht0000000q9mIAA__eid=ka3Ht0000000q9m&feoid=00N2J00000APFDu&refid=0EMHt0000061Fv7.png
Figure 4: Example Showing a Mapping from an Email Field to Input from an Earlier Form

Step 4: Test Your Flow
If possible, test using non-production data or make changes that do not re-enter production. You may have taken care of this in your previous step by creating an Authorization with UAT or test credentials. You may be able to do this by inputting production data but applying the transformations or outputs to a sandbox. How you test will depend on your flow and your apps, but it’s important to plan accordingly and run iterations outside of your production environment first. 


Flows easily allows tweaks and changes in the GUI for quick updates. After any changes or updates, you can run the flow using the Play button and then check for failure or success in the notification dropdown.  Each dropdown can be opened and drilled into for more information as needed during your test.
ka3Ht0000000q9mIAA__eid=ka3Ht0000000q9m&feoid=00N2J00000APFDu&refid=0EMHt0000061Fv8.png
Figure 5: Drill down into a notification to see more information after running the Flow

Step 5: Roll Out Your Flow
Now that you’ve got your automation tested and ready for production, it’s time to communicate the rollout with your end-users. But what do they need to know? It’s best practice to communicate these changes in advance of their go-live, providing users ample time to become accustomed to the process and ask questions.

Generally speaking, most rollout communications include some messaging around “the what, the who, the why, and the when.” In the case of adding automation, the hope is you’ll be making users’ lives much simpler, so there should be less pushback than for some other changes you might implement. For an HR-driven identity automation scenario, consider communications like:
 
“We’re rolling out a new automated onboarding process starting the first day of the next quarter. Once fully deployed, the process will trigger from a new employee’s creation in our HR system and then automatically create a corresponding account in our directory, give them an email, and provision them in our main apps such as Salesforce.  Downstream manual operations such as laptop deployment and badge creation will receive notifications automatically, decreasing delay and confusion over when these steps need to happen.

More information on training will be forthcoming shortly from your manager.  Our hope is this automation will streamline processes across multiple teams and free you up to focus on less repetitive items that demand human interaction.”

The communication you choose will depend on the flow you build, but focusing on how it will make the end user’s life easier will assist in lending a positive light to the change. Think back to your planning step and the problem that you’re trying to solve – your communication should be highlighting that problem and how this automation provides value and benefits to your user community.
 
Going With The Flow
The move to SaaS and cloud-hosted applications has revolutionized the way organizations manage identities and their related workflows, making automation not just a luxury but a necessity. Leveraging Idira Identity Flows offers a path to efficient, streamlined, and secure automated processes without the complexities traditionally associated with traditional development. We hope that this article has provided you with the foundation knowledge and guidance to start developing your own custom automated workflows with Identity flow.

You can find a series of walkthrough videos on how to use functions like conditions, the email utility, arrays, datastores and more in the Idira Identity Reels Field Tutorials YouTube Playlist.  If you have additional questions regarding Flows, we suggest reviewing the online docs, start a discussion with the Identity Flows topic or reach out to the community in the Identity Admin Resource Center.
  • 4066 Views
  • 0 comments
  • 0 Likes
Top Liked Authors