Latest / Talking Security: Insights from Microsoft Security Experts / #24 - Jan Bakker and Pim Jacobs about Microsoft Entra - Identity Governance
Transcript
- 0:00Welcome to the Talking Security Podcast.
- 0:08We will talk about items related to Microsoft Security.
- 0:21So there are we again, welcome back listening to a new episode of the Talking Security Podcast.
- 0:27My name is Frans Oudendorp and in this recording I will talk to some guys about Microsoft Entra
- 0:32and especially Identity Governance.
- 0:35Today we are at ExpertsLive in the Netherlands.
- 0:37On the venue we have a special podcast room so we can record stuff, we and others also.
- 0:44Because of this I have invited Pim Jacobs and Jan Bakker to talk about Identity Governance.
- 0:49There's new stuff coming up and they will talk about it later on on ExpertsLive.
- 0:54But first guys do we have a little introduction, who do I have on the table Jan?
- 0:59Hi Frans, thanks for having us.
- 1:02My name is Jan Bakker, I'm based in the Netherlands and I'm a Microsoft 365 consultant and a Microsoft
- 1:07MVP and I'm focused on identity and access management and security.
- 1:11So I guide my clients to get the best out of those products and how to implement them
- 1:16properly.
- 1:17And maybe the security staff who will hit some stuff later on.
- 1:24And on the other side of the table we have Pim, who are you?
- 1:29Pim Jacobs, Principal Consultant at InSpark, Microsoft MVP, focusing on the full Entra portfolio
- 1:35so from Azure AD, permission management, a little bit verified ID and with that of course
- 1:42Identity Governance as well.
- 1:45And I help my clients guiding them into the right direction and properly implementing
- 1:50those products as well.
- 1:52We add today the topic is Microsoft Entra, especially Identity Governance.
- 1:57Identity Governance, what is it and what can we do with it?
- 2:01The short story.
- 2:02Okay, the short story and we will show that in the presentation which we have this afternoon
- 2:08as well is that it exists of five different pillars.
- 2:12So lifecycle management with lifecycle workflows, which is brand new and which has been released
- 2:19four weeks ago, provisioning to users to third party apps and deprovisioning them.
- 2:25That's a little bit attached to lifecycle management of the accounts.
- 2:29We got access packages and access reviews, which is there within the interface today,
- 2:34privilege identity management and terms of use.
- 2:37This is the short story.
- 2:38So, yeah, maybe we will dive in on the specific topic in the next few minutes because access
- 2:46packages and access reviews, I think that is the common things that we can use within
- 2:52Identity Governance, Jan?
- 2:53Yeah, correct.
- 2:55And today we're also going to take a look to that because access packages is really
- 3:00important in the mover phase.
- 3:02If we look at the joiner, mover, lever process, access packages, that's where they come in
- 3:08in the mover phase because you want when folks get promotion or change department, their
- 3:15access changes and you want to guide that, you want to govern that especially.
- 3:19Yeah.
- 3:20And if we look at access packages, access reviews, then we have an application or a
- 3:26group where we can get access to on the short term on a yearly basis or monthly basis.
- 3:33You can do an access review to see if someone needs still access that specific group or
- 3:38application.
- 3:40If we look at lifecycle management, identity life cycles, is that related to this?
- 3:46Yeah, I think so.
- 3:48And it's funny that you say that you need to review the access, but there is a brand
- 3:53new feature where you can automatically assign policies based on attributes.
- 3:59So you can hand out those packages dynamically.
- 4:04So that there's no longer a case to review them because you manage them yourself.
- 4:09So if a user changes department, they will automatically get off boarded from one package
- 4:14and onboarded to the next one.
- 4:16Okay, nice.
- 4:18Are there any other enhancements within lifecycle workflow, Pim?
- 4:27Well lifecycle workflow is a total new feature within identity governance.
- 4:31And today that's working for the joiner and the lever scenario.
- 4:35Is that not related to identity life cycles?
- 4:38It is related to identity life cycles.
- 4:40You go account lifecycle management, which is actually why you need to work closely with
- 4:47HR and why you connect your HR as the source of your identity and let that provision to
- 4:53your AD or Azure AD, which can today from the Azure AD portal be natively done with
- 4:59SAP success factors and workday.
- 5:02That's actually the first part.
- 5:03But if you don't have those products, you could use different tools as well.
- 5:08And I'm not going to name them because that's a little bit of my allergy, to be honest.
- 5:15But there are different ways to get those accounts provisioned.
- 5:19What is really important, however, is of course that those credentials, the access, the birth
- 5:27access rights of an account are configured correctly.
- 5:32And that's something we can today do with lifecycle workflows in the joiner scenario.
- 5:37And if we look at the access packages and access reviews and that sort of thing, is
- 5:42that related to this stuff?
- 5:47Not particularly to lifecycle workflows.
- 5:50But as Jan just mentioned, it's more related to the mover process.
- 5:53So lifecycle workflows is something you can use in your joiner process.
- 5:59And you can define based on the employee hire date.
- 6:03And if the user is working in department sales, those are the tasks I'm going to execute on
- 6:09the day you start your job at the company, like adding them to the sales group, sending
- 6:15the temporary access pass to the manager of the user and doing XYZ.
- 6:22And Jan's famous topic is in the logic apps.
- 6:26So I will leave that to him to name an example.
- 6:33That's the joiner thing.
- 6:34And you can have 50 workflows per tenant.
- 6:38And each workflow can have 25 tasks.
- 6:41That's the maximum today.
- 6:43Those run each three hours.
- 6:45And when we look at the lever scenario, we can of course off board the user correctly
- 6:52in removing the licenses of the user, removing the user from all the groups, all the teams
- 6:58where it's a member of.
- 6:59And we do that based on the employee leave date time.
- 7:04So it's automatically triggered in a smart way.
- 7:08And so you don't need to do those things yourself anymore as an IT admin.
- 7:13It's managed for you.
- 7:15But it's configured by you.
- 7:16Yeah, so the workload from an IT admin perspective is lower because we can automate stuff.
- 7:23But automate, Pim already mentioned, Power Apps.
- 7:27How does it integrate, Jan, with Power Apps and that sort of stuff?
- 7:30Yeah, that's a great bridge to my favorite topic.
- 7:35It extends actually to logic apps.
- 7:38We all know that Power Automate is the little brother or the little sister from logic apps.
- 7:43But yeah, you can create extensions, for example, to do tasks that are not in the default task
- 7:51settings.
- 7:52So you can do stuff like, hey, add this user to this team or remove from this team, enable
- 7:57account.
- 7:58Those are the basic tasks.
- 7:59But you can also do extensive tasks.
- 8:02For example, you want to create a temporary access pass and not send it to the manager,
- 8:07but directly to the end user, for example.
- 8:09That's not in the default template, but you can do it.
- 8:11So the sky is the limit there.
- 8:13You can do whatever you want.
- 8:15So you can even talk to third-party applications.
- 8:20Maybe what's important to mention as well is that specifically in this case for the
- 8:25joiner scenario, because for Lever, the employee leave date time cannot be synchronized yet.
- 8:30But for the joiner scenario, you could also execute actions in the on-prem AD by using
- 8:36logic apps and Azure Automation with hybrid workers so that you can execute those scripts
- 8:41in your on-prem AD to, for example, add the user to a group, whatever you would like to
- 8:47do there.
- 8:48So we have access packages, access reviews.
- 8:51That's the old stuff that is still many years in identity governance already.
- 8:56And that is not completely your way.
- 8:59And we still need that.
- 9:00But new functionality has been added to identity governance, like identity lifecycle and lifecycle
- 9:08workflows.
- 9:09And with that, we can use access packages, for example, to automate stuff and do things
- 9:15automatically.
- 9:16Exactly.
- 9:17Automating is the key word there.
- 9:18So as Ben mentioned, joiner and Lever can be processed with lifecycle workflows.
- 9:24And we've got the gap in the middle there, the mover part, and that we can do with access
- 9:28reviews, but with the addition that we can do dynamically now.
- 9:31So a user does not have to go into the portal and request those access packages, but they
- 9:36are dynamically assigned to the user based on their attributes.
- 9:39So also automating that part now.
- 9:41Yeah.
- 9:42And that is good for, I think, 50, 75% of the groups.
- 9:46But there are still probably groups in an organization where you need to get access
- 9:51based on requests.
- 9:53So access packages can still be used afterwards.
- 9:57Correctly.
- 9:58So if there is any approval needed or a multi-stage improvement or auditing features or whatsoever,
- 10:06you can also use access packages the way it's supposed to work with also an access review
- 10:11because it's still really important.
- 10:12But for the mover part, you can do a lot of automation these days.
- 10:18Yeah.
- 10:19Temporary access parts, you already mentioned, Pim.
- 10:22But also, privilege identity management is part of identity governance.
- 10:28Is privilege identity management also part of the workflows and the lifecycle things
- 10:35that we have spoken about?
- 10:38Is that a relation with that?
- 10:40Not by default.
- 10:42Because with lifecycle workflows, you cannot, for example, add a role assignable group,
- 10:48a privilege access group.
- 10:50That's grayed out.
- 10:51But if you want so, use logic apps.
- 10:54So the sky is literally the limit here.
- 10:58So once we, I'm in this preview already for a long, long, long, long time.
- 11:04And we tried something internally because we have a labs tenant where we test stuff.
- 11:10And the problem we have is deep provisioning and deep provisioning on that end as well.
- 11:14So what we are using right now is literally a logic app, which is triggering via a web
- 11:20book, a workbook in another tenant.
- 11:22So to provision the account because you receive those account details from the lifecycle workflow.
- 11:29So literally, that's whatever you would like, you can call an API from a particular app
- 11:35to provision accounts with a logic app.
- 11:40How far your imagination goes and can go, that's what you can do right now.
- 11:45Everything can happen with the use of logic apps, a power automate and that sort of thing.
- 11:51Correct.
- 11:52So we talked about in the beginning, you mentioned security.
- 11:58What does this identity governance stuff, what does that make sense in relation to security?
- 12:04What does me as an organization, what does it help?
- 12:07Well, that's a good question.
- 12:09The typical thing that we see in organizations is that when a user goes through the period
- 12:15of working for a company, they build up privileges, access to applications, roles that they need
- 12:21for their jobs.
- 12:22But as they never get reviewed, let's say over 10 years, you get a bunch of stuff that
- 12:29shouldn't be attached to your account anymore.
- 12:31And then you're going to leave the company and your replacement comes in.
- 12:35And what's the typical thing that they say?
- 12:37Just copy his account or her account and give him all the stuff so he or she can do her
- 12:42job.
- 12:43And that's not good for security because we want lease privilege.
- 12:46So it can be that they also copied the administrator roles over.
- 12:51So, okay, you are a privileged identity administrator and the next one is also be that person.
- 12:57So that's related to security, something that you don't want.
- 13:00You want to evaluate constantly and even better, get those access dynamically and constantly
- 13:09reviewed.
- 13:10So, yeah, based on the function, based on the role that you have, you have a specific
- 13:14function role where access is given based on the role and not on a person.
- 13:20And if you look at identity governance based on security, we have also insider risk within
- 13:28Microsoft 365, for example.
- 13:32The case that you are describing is more related to insider risks because it is more or less
- 13:37an insider risk.
- 13:38So insider risk management and identity governance, they are they are strengthen each other.
- 13:45Yeah, I think that's correct.
- 13:48Insider risk is really good at stuff like, hey, this person resigned from his company
- 13:54and is doing stuff four weeks before his resumption.
- 13:57So that's really what we can do as well.
- 14:00Or we can just say, okay, this is the employee leave time.
- 14:05We're going to do some tasks so that you cannot do that stuff.
- 14:10So you're going to get read only rights or something like that.
- 14:12So you can do anything to prevent that.
- 14:15But it really fits together.
- 14:16Yeah, and if I have we talked about identity governance, lifecycle management and that
- 14:21sort of stuff.
- 14:23What is needed for me if I if I am a company and I want to start with identity governance,
- 14:27what should I do?
- 14:28I always I always advise customers to to get their the source of truth correct.
- 14:37So what is in HR is the source of truth.
- 14:41If someone changes his name, changes his is resigning is coming into the company.
- 14:48HR is the first to know.
- 14:50So get those and get that connected to your AD or your Azure AD, depending on where your
- 14:56source of authority is.
- 14:58So that that will be always my first step to advise.
- 15:01And that could be a simple thing where you receive data from HR, let a PowerShell script
- 15:08run and update and create accounts.
- 15:10It doesn't need to be complex and fully automated as long as you do it.
- 15:15And with that being said, make sure that employee hire date.
- 15:21And if you're you're today working cloud only also employee leave date time are configured.
- 15:27And then you can start with lifecycle workflows and configure.
- 15:30Yeah, well, we just mentioned sky is the limit.
- 15:32Yeah.
- 15:33So it's a process in between use access packages and access reviews and my tip would be don't
- 15:42put an access review in anything because otherwise people get literally.
- 15:46Yeah, it will.
- 15:47In the end, you will see that people are going to create a rule, move it to this folder because
- 15:52I don't care and then they lose access.
- 15:54So do it.
- 15:55You need to configure it on the things you really want to be reviewed and which cost
- 16:01money or are containing highly sensitive data.
- 16:06So that's important.
- 16:08Use auto auto dynamic access packages as well based, for example, on department.
- 16:16And then once a user leaves the company, make make the offboarding flows within lifecycle
- 16:21workflows.
- 16:22So that is important, important for me and user perspective and an idea perspective.
- 16:27And on the other end, I think, and that's what I'm mentioning today as well.
- 16:32Payment is important and the basic security stuff.
- 16:36So don't do this.
- 16:37Don't start doing this once you don't have MFA.
- 16:43Literally secure first and then make it advanced step by step in a in a logical way, because
- 16:51we can provision accounts to up to the max.
- 16:54But if they don't have MFA applied, that's a bigger risk.
- 16:58So from that angle, if you need to make an order, that's the most important thing to
- 17:04do first.
- 17:05And this would then be your next step.
- 17:07Think of defense and depth and do it on all places and not just on one.
- 17:13In addition to that, I would say if you're going to start and you got your base right,
- 17:18so the source of truth is configured and you're going to start with identity governance, start
- 17:22small and don't build castles that you can support.
- 17:28Because for example, you can start with small access packets having licenses, for example.
- 17:33So Power BI Pro, start with that or teams with sensitive data in it, you know, start
- 17:39small with less impact.
- 17:42So if someone, if it gets not good, that not everyone is infected on the things that you
- 17:50have configured.
- 17:51Exactly, and it's also good to experiment with it.
- 17:54So how does the organization react to access reviews?
- 17:58What is the big note from the field?
- 18:00One of the topics in the slide in the session you're given, what is the big fail when companies
- 18:09start with identity governance, for example, from your end, Jan?
- 18:13Well, what we already mentioned, organizations need to prioritize stuff.
- 18:18So they need to focus on the stuff that matters first.
- 18:22So you can go into identity governance and not have your MFA in order.
- 18:28So that's one big thing.
- 18:29And what I already told, they start and they want to do everything at once.
- 18:34So basically that's the…
- 18:38Start small.
- 18:39Yeah, start small.
- 18:40And maybe, and this is funny, in the preparation we discussed the things like self-review access.
- 18:46Yeah, yeah, yeah, yeah.
- 18:49And the group owner access reviews.
- 18:52In practice, you will see that if you do self-review, either the organization is not responding
- 19:01at all or everyone is responding and is keeping their access rights.
- 19:05So my personal feeling with that, and I think that differs from Jan's experience, but it
- 19:10doesn't really mind, is that I would most likely use the group owners because they are
- 19:18the owner of the group and need to determine who is in there, yes or no.
- 19:22Yeah, but how is that related to guest accounts?
- 19:25Because I've set up guest account review within my organization and on guest accounts, we
- 19:33have implemented self-review and that works quite well.
- 19:36For guest accounts, yes.
- 19:38If we're talking for guests, if we're talking for end user accounts, it's going to differ
- 19:44because nobody wants to lose their access.
- 19:48I don't have experience with that, but…
- 19:50Well, it depends.
- 19:51If your manager are fully aware of the task, that they are the guiders of their data and
- 19:57they're fully on board and have some adoption, it's fine.
- 20:01But what I see is we underestimate the power of self-service in any way.
- 20:07Yeah, absolutely, but everything stands with communication, adoption, be aware and know
- 20:15what you're doing and why you are doing stuff.
- 20:18And that's where display names and descriptions are really important because if you're going
- 20:22to get an access review, hey, we want you to review access on this group and it has
- 20:29a prefix and a suffix and some IT stuff in it, they're going to say, okay, I approve
- 20:35because I don't know what it is, but I don't want to lose access.
- 20:38I agree with Pim on that, but there's a lot of elements that come in that makes it user
- 20:44friendly that we as IT folks not always see.
- 20:47Yeah.
- 20:48Thanks guys for having you both in this recording.
- 20:52To finish up, is there one last thing about Entra or identity governance in particular
- 20:59what you want to share with the audience?
- 21:05Go to the Azure AD portal, click on identity governance and go to lifecycle workflows.
- 21:10If you don't see that there's a trial button where you can activate your P2 trial.
- 21:16And then start with identity governance.
- 21:18Of course.
- 21:19So thank you guys.
- 21:20And for now, thank you for listening to this episode.
- 21:24Stay tuned for more new content coming in the next few months.
- 21:29See you in the next time.
- 21:30Thank you.
- 21:31Bye.