Building a Repeatable Model for Workforce SSO Access

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
19 min read
L4 Transporter
The end of a Idira Workforce Identity implementation is just the beginning. Organizations implement technologies to solve business problems, and simply having a workforce access solution deployed is only one step of your journey. We’re constantly going to have changes to our workforce, whether it be people joining, leaving, or moving roles, and we’re constantly going to have changes to the applications and services our workforce consumes.

Maturing your identity services to ensure consistent access and security across a distributed workforce is an important part of any organization’s modern identity security strategy. This is often achieved through the designing of effective and repeatable processes that enable your organization to achieve that state of mature workforce access. By the end of this article, we want you to have a strong understanding of how you can design your own repeatable model for workforce access, what information you need to know and why it’s beneficial to multiple stakeholders in your organization.

The Benefits of a Repeatable Model
Why should we even care about implementing an automated, repeatable model? There are many benefits, each impacting different stakeholders. It provides scalability, which enables your organization to deliver more requests to more users, faster and with less human interaction. It allows you to expand your service delivery to growth with the needs of the business without requiring additional overhead. It can streamline operations and compliance, reducing the complexity and burden on IT while improving the speed of delivery. It allows you to shift your teams focus and effort to more strategic initiatives instead of performing the basics and helps satisfy basic compliance needs in a cost-effective manner. A repeatable model like this enables the workforce and allows them to get access to the resources they need fast, so they can keep the business running. It’s enabling your user community to deliver the work that moves your business forward. Last but certainly not least, it delivers faster security. With automatic application of security policies and controls when access is granted, you’re ensuring your user access is secured from the start, leaving less time for vulnerabilities to be exploited.


Identity Lifecycle Management for SSO
When we think about identity lifecycle management we typically think about the cradle-to-grave process, how do we go from someone needing to exist, access resources, and eventually leave. There’s also other processes and considerations that sit adjacent to this process we also need to take into consideration. We start with a new employee being hired and that new digital identity needs to be created, including external agencies and contractors. That employee’s access will need to be provisioned, and eventually that user will need submit an ad-hoc access request or we’ll need to onboard a new web application entirely into the organization. From there, our user is going to authenticate to an SSO portal and access resources, with security policy being enforced on that access. At some point in the journey, we’ll get to a point where their access needs to be recertified and eventually an employee will need to be offboarded.


In the sub-sections below, you’ll go into the details for each of these steps and propose the questions you need to ask yourself in order to build a repeatable model that fits your organization’s needs best.

ka3Ht0000000q7nIAA__eid=ka3Ht0000000q7n&feoid=00N2J00000APFDu&refid=0EM2J000003Yjl0.png
Figure 1: IAM Lifecycle Process

New Employee Hired
We start at the beginning; a new employee gets hired. HR and the hiring manager have decided that we want to extend an offer to a candidate, and they accepted. Now what? What information do we need to know about that new employee? It’s actually pretty simple, we need to know standard employee information in order to feed our directory and identity services, information like name, department, email, and role.


External Agencies and Contractors
We need to know the same information about any external resources we plan on bringing into our organization too. Consider integrating Workforce Identity with that external agency or contractor’s identity provider via B2B federation. This is most valuable when you have external partners at scale as it provides a reduction in overhead managing external identities and ease of access. But you’ll need to do some sort of efficiency benefit analysis – is it worth the effort to setup B2B federation for this organization?


Remember to maintain tight controls on access for external users, just because we’ve shifted the directory service off to that organization doesn’t mean we give up provisioning access to apps or the security controls applied to those apps!

Employee Identity Created
Moving onto our next major step, creating that new employee’s digital identity. Ask yourself, what’s going to create this identity? The first thing you need to do is identify your system of record. Do you have an HR System with integration capabilities? Do you use alternate source of truth for identities and access? What’s your backend directory service? Who or what is going to create the user in Idira Identity? Does your source of truth map department or role to RBAC in your directory system? Do you even have roles defined internally for different teams?


The answers to all of these questions determine how your user’s digital identity gets created and what roles get assigned at time of hire. Role definition specifically is critical to be able to deliver birthright access model specifically for your employee’s role.

We also need to think about how we’re going to welcome a new user. How are your new employees told where to go and how to access things? How are they going to access Identity? How do they set an initial password? Access the knowledge base? Download the Idira Identity Mobile app? Put yourself in their shoes and ask yourself, if you were brand new, what information would you want to know about accessing the applications you need to do your job.

Employee Access Provisioned
Now that we have a new employee hired, and they exist within Idira Identity, now we need to ask ourselves, how are we going to grant our employees access, and what are we going to grant them? In this section we’ll cover four topics related to provisioning access, common applications, role-specific applications, permissions, and provisioning.

We should always start with common applications, what does every single employee need access to? This is typically resources like your HR system, productivity suite, expense software, training and LMS, and JIRA/planning tools. From there, we can think about role-specific apps. What does my employees specific job function require? Cloud Engineers need access to Cloud Providers, Software Developers need DevOps Tools, Account Executives need CRM tools, Marketing require Social Media access, and IT staff often use Idira Privileged Access Manager. Understanding which applications each role requires is only discovered by working with HR and the Line of Business hiring manager.


When we’re granting access to applications that are job function specific, we need to think about least privilege (not in the sense of privileges in an app, but rather who we’re granting access to). You need to understand if all the members of this role/group require access to this application, or if only a specific individual from the group. Does the applications licensing model or license cost impact your decision-making process for provisioning access?

The final part here is the actual provisioning of access in the web application, which is split between policy and technical. On the policy side, do you have pre-requirements for access, like completing certain HR or training courses before we can give someone access to a specific application? On the technical side, does the application require user provisioning or does it support role assumption, and if it is provisioning, how does that user get created, SCIM or manually? Not all web apps provision access the same way, so it’s important to understand each web apps intricacies as you plan to grant access.

User Access Requests
Another important adjacent process to plan is handling ad-hoc requests from your end-users. Before you can even process an ad-hoc request, you need a few things, an application inventory, a request system, and an approval process.


Do you have an application Inventory (CMDB) for all your enterprise deployed web apps? How will you get the details needed to provision access to the web application? An application inventory system is critical to delivering automated ad-hoc access requests. It should contain all the details required for an end-user to request access and for automation to provision access.

Next up is the request system. We highly recommend using your existing request systems for request and approval process. Integrate via APIs to grant users access to web applications automatically upon approval. You’ll need to ask yourself what groups/roles are relevant to grant access, are you granting access directly to a single user and how will your end-users know where to go and how to submit a request?

Last but not least is the Approval process. Who needs to approve the access request in your request system? There isn’t a one-size fits all approach here, it depends on the type of application. Is just the user’s manager sufficient? Do we need the application owner to approve the license allocation? Do we need the data owner to approve if the app contains sensitive data?

Onboarding New Web Apps
Another adjacent process we need to think about is how you handle the onboarding of a brand-new web application into Idira Identity. There are two major components here, the configuration of the web application itself and the security policy/controls we apply to the app and its users. For every new web application that you want to bring into Identity, you’ll need to identify the individual or team who is responsible for administering that application, as you’ll need their help to configure SSO. You’ll need to know what the apps authentication mechanism is, whether it be SAML, OIDC, O-Auth or User/Pass. SAML is ideal for enterprise apps, and for the most part should be supported. Does that service provider (the app) support IdP initiated sessions? Can it only do SP initiated? The answers to these questions impact the user experience. On the flip side, what information do you need to provide that web application admin to configure SSO on their side of the app?


The other big part of onboarding a new web application is determining which security policy and controls should be applied to it. First place you should look is in what does your corporate policy says. Do you even have a policy that covers web application security controls? Organizations should have a standards and controls documented for various access scenarios, regardless if it’s privileged access on prem, cloud security or web applications. Does your organization classify applications by risk, data sensitivity, audit requirements? Do the user’s permissions influence this decision (admin vs. config changes vs. data access vs. read only)? This should tie back into your application inventory system that we mentioned earlier. If your organization doesn’t explicitly cover these scenarios, it’s best to keep your application and authentication policies simple to start and gradually build their complexity and security.

Pro Tip: Be sure to also keep track of the self-service app additions (if you’ve enabled that), and with that data you can determine if is it worthwhile to add that app to the catalog, by default or bring in the enterprise version.

Employee Authenticates to SSO Portal
The next step in our end-user’s journey is authenticating to the single sign-on portal, and it’s here where we should ask ourselves, how will their experience look? There’s a decision-making process that needs to happen prior to them accessing the portal. You need to think about your end-user's experience. How do you want people to be able to sign in? Do you want password-less experience? What does security policy state is required for risk-based authentication? What does your security policy say for analysis and alerting of risky behavior? Are you subject to NIST guidelines on Authentication Assurance Levels (AAL)? The answer to all of these questions will help determine how your end-users will actually authenticate to the portal.

Once we’ve decided upon our authentication mechanisms, it’s time to start thinking about the users’ actions and experience. Generally speaking, we want to try and simplify their experience whenever possible. Complexity can create friction, and friction creates unhappy users. If you can’t simplify the user’s experience, education on how to use and why they’re doing it is critical to combat that friction. Regardless of the approach, your end-users are going to need to know where to sign in and how. This should be addressed at the time of hire and be documented on your internal IAM webpage or knowledge base.


Employee Accesses Resources
Now that our employees can authenticate to the Identity service, we need to talk about how they are going to get to the service provider (the resource they’re trying to access)? The most common way is going to be through IdP initiated session (e.g., one-click from the web portal). It’s recommended to use IdP initiated connections whenever possible due to its easy and simple experience for the end user. However, some cases will require your end-users to access from the service provider directly. This is most common as a result of CLI-based access, but also occasionally this occurs for web pages as well. This really isn’t in your control at all, it’s dependent on the web apps configuration and what it supports.


Another convenient method to consider supporting is the Identity Browser plug-in. This provides easy access to SSO apps without needing to navigate the web portal, giving users another option to interact with their available web applications. It also supports custom username and password web applications, allowing you to deliver an SSO-like experience to non-enterprise or legacy applications that don’t support modern authentication mechanisms.

Security Policy
One additional consideration that impacts how your employees access resources is the other security controls you may have implemented. If you’ve opted to implement layer additional security controls onto certain users or applications, you’re going to force them to do things a certain way. For example, Secure Web Sessions will require them to authenticate from a device that supports the session recording and protection capabilities. Endpoint protection controls may only allow them to authenticate from a privilege protected device. Or you may enforce authentication from corporate laptops only or disable mobile device access. Whatever additional controls you add, it’s imperative that you document the who, what, where, when and why, and enable those user(s) impacted. This ties back to the “Onboarding New Web Apps” security controls considerations.


Employee’s Access Recertified
Most organizations will at some point require employees to recertify and attest that they still require access to the resources they’ve been granted. But not all organizations do this the same You’ll need to first ask yourself if periodic recertification required? And if so, what is it required for, privileged applications, regular workforce apps? Does the requirement change based on a user’s permissions within that application or the data classification of the app? These questions are generally answered by your corporate IAM policies.

Assuming it is required, how are you going to actually recertify the employees access? Well, there’s typically two common methods, manually or via integration with IGA and compliance service. If you’re doing it manually, you must first define what needs to be recertified as that defines the scope of your process. From there you need to determine how you actually revoke access, will we remove the user from the role or web app directly (depending on how that access was granted)? Who is going to be responsible for revoking that access, and how will they know when to do it? If you have an IGA service for recertification and attestation, consider integrating this for your workforce access if not already done. Going through the exercise of answering these questions for the manual process will help guide your automated process design as well.

Employee Role Change
Another adjacent process to the access recertification is when an employee changes roles. If you’ve implemented strong role-based access as discussed in the “Employee Access Provisioned” section, then this should be a relatively small lift. The idea where is to leverage the same type of automation or manual process to remove the user from their old role(s) and move them into their new ones. The transition should be seamless, but in the event it’s not, it should be caught during your periodic recertification. If you’re doing this manually, the key step is developing a process to generate a call to action for someone to revoke the access and grant the new access.


Employee Offboarding
Our last off-shoot process is employee offboarding. Here we should really be asking ourselves, how did we setup our provisioning to begin with? Was it setup with our HR system? Or with some custom automation? Or was it all manual? How are you going to be notified to take action? Whatever did the provisioning should also be responsible for the de-provisioning and offboarding. Be sure to discuss this with your HR teams, as they are a key stakeholder in this process.


Timing of offboarding is going to be based on your security policy. When are you going to know to act (or when will the automation take action)? Does that timing differ based on role, privilege, or access to sensitive information? Does that timing differ based on the reason the employee is leaving (voluntarily, layoffs or immediately termination)? Do you do any periodic audits to ensure that everyone is removed, and their access revoked?

Consider moving all employees who have left into a disabled state for a period of time. In the event they are the sole person with access to business-critical resources and you’ve moved straight to deletion, you may not be able to recover access to those resources. If you don’t already have a policy that covers disabling then deletion after a period of time, consider creating one. And for all of the mover and leaver actions, but sure to create records of these events, as they can be critical for audit.

Prioritizing Your Implementation
So far, we’ve talked a lot about designing a mature process. We recognize that this doesn’t happen overnight, and we wanted to also provide a pragmatic approach to deploying functionally of Idira Workforce Identity to help enable you to get to this state. Based on our experience (and all else being equal), we’d recommend implementing the features below in the following order (left to right). The categories (rows) indicate what type of function we’re implementing, identity management, access to web applications or security controls. Your capability maturity increases as you move left to right in each row.
 
IdentityDirectory IntegrationLifecycle Management
for Apps
SCIM Integration for AppsHR to Directory SynchronizationIntegration with Governance & Compliance
AccessMission Critical Cloud AppsCore Cloud AppsAll Cloud AppsOn-Prem Apps, VPN-lessAll Apps Everywhere
SecurityMFA for SSO PortalSWS for Select
Web Apps
MFA for ApplicationsAdaptive MFA
for Apps
Incident Investigation, SOAR
Figure 2: Capability Maturity Table

This should go without saying, but whatever is driving your initiatives and whatever is important to your organization’s goals should be your priority. Our prioritization guidance and rational is something you should take into consideration, so you understand the tradeoffs and make the most informed decision for your business.

IAM Program RACI Matrix
Operationalizing any technology and turning services into an ongoing program requires people to do things on a consistent basis. That’s literally what turns random tasks into a process. A critical part of making sure the process runs smoothly is to create a RACI matrix. A RACI matrix is a document that outlines major tasks, activities and functions that need to be performed as part of the process as rows, and outlines the teams and roles involved in the process as the roles. Where the two intersect will be one of five values: R, A, C, I or blank. “R” references the role responsible for completing the task, “A” references who’s accountable for that task, “C” references who should be consulted during the task and “I” references who should be informed. Blank values indicate there is no relationship between the task and the role.


Creating a IAM program RACI matrix for the repeatable workforce access model described above is an important step in ensuring the process flows smoothly. We’ve attached an example of an IAM program RACI matrix here that you’re welcome to use as a starting point. Every organization is a bit different in how they execute IAM processes, so its not uncommon to modify the template provided. To learn more about RACI matrices, we recommend taking a look at this article by project-management.com, it’ll do a much better job at explaining RACIs then we will.
ka3Ht0000000q7nIAA__eid=ka3Ht0000000q7n&feoid=00N2J00000APFDu&refid=0EM2J000003YjlD.png
Figure 3: IAM Program RACI Matrix Example

Maturing Your Own Workforce SSO Access Process
We covered a lot in this article, and we hope that it was insightful into the process as a whole. We encourage you to start looking at your own IAM processes and if you haven’t yet, create your own IAM program RACI matrix. In doing both of those things, you’ll likely find areas for improvement, whether that’s in processes that didn’t exist, opportunities for automation or streamlining existing steps to deliver workforce access faster, more efficiently and more securely to your users.


We would also recommend exploring the additional people are process articles on the Success Blog, topics like roles, responsibilities and staffing, organizational change management, developing a knowledgebase, and building your end-user communications strategy. All of these are important topics that provide support for the execution of your workforce SSO processes.
  • 2877 Views
  • 0 comments
  • 0 Likes
Top Liked Authors