8 hours 33 minutes
Hello, Siberians. Welcome to this lesson on Azure lady. Conditional access. This is part of the Is that 500 mikes off as your security technologies casts quick information on what will be covering in this lesson will start out by giving an overview off what conscionable accesses with a look at how it works. To protect applications,
we'll discuss some common use cases.
We'll cover how policies are applied on end with some vital information on conditional access. Best practices. Let's get into this.
Let's define what conditional access is. Here's my definition.
It is on a giant, the feature that protects applications by requiring certain criteria beyond identity authentication to be met before access is granted. We'll see what that means in more details in a few minutes. For house to use conditional access would needs toe have a minimum off azure 80 premium P one license,
you know as a stand alone
a spark off licence bundle
in other force. To understand our conditional access works, we needs to understand the normal application access process with dark, conditional access. So let's review this. If a user access is an application that uses as your 80 s identity provider. They will be redirected to Azure Haiti,
which validates the first factor authentication in this case to eat us pass. What
if I m f. A is required? MF They will also be very fight. After successful verification, the user is granted an access token for the application. This is the normal application process with doubts conditional access on. It doesn't give us flexibility on how controls applied for an application.
Let's see out. This process walks with conditional access. If a user access is an application that uses, as your Lady has his identity provider, there will also be redirected to Azure Haiti, which validates the first factor authentication. After successful verification, the request goes to conditional access for further processing
before the access is granted.
This is why I meant by conditions beyond identity verification. So what else Conditional access do with these now? Does the work conditional access is broken down into two persists conditions and controls. This is a classic if this, then that situation. If this condition is met, grant access or block access
based on the conditions,
let's look at conditions first. Conditions determines when the policy applies. This could be based on identity information like to use this role on group membership. This could be the application that the user wants to access. This could be based on device information like the operating system or even device state information that's reported
in the Microsoft in tune.
It could also be the location information like the I. P address that the request is coming from. And it could be client application information like if it is a browser in mobile application or legacy application. And finally, that could be signing risk information from majority identity protection, which requires a premium Peter license
controls. On the other hand,
the term is what the result would be if the conditions are met, that could be allowing a blocking access based on the criteria that met. That could be to require Maffei that would be to limit access using Microsoft's Cloud AB security solution. He could also be to foster password reset
once the condition access policy result is calculated,
and based on the result, these there can be granted a talking that it can use to access the application. Let's review some common use cases for control access, one of the access controls that we can use is to require McPhee on their difference in obvious that this can be implemented for, for example, because having MF A for administrators
administrators have certain privileges the Attackers may find interesting,
which makes them more of a target on requiring MFP Anders account can help to reduce the risk of them being compromised. We can also require me free Fraser managements to ensure that any access to the azure pato as your power show. Why just cli requires MFP. We can require MF A for access attempt from untrusted networks.
Why, excluding that trust that Internet
we can require? MF A for how users This is one of a row good practice in a way, as we discussed in the last month. But what you see is that we have a great amount of flexibility in our M. F. A. Is applied using conditional access. Another common use cases to block legacy authentication. Like I see authentication protocols caviar. Very high risk
off, which includes no support for MF,
which means that they are susceptible to brood falls are passed. What gets an attack? We can block off the indication the questions in this protocols using conditional access. We can also require that users be connecting from our trusted locations before they can completely Emma for registration process To limit the risk off Attackers, I jack. In this process,
we can block access by location,
and this is useful to block access to certain applications. If users are connecting from untrusted networks, we can require complainants devices on organizations that have the plate makes off interior, can use the information, return from the devices toe, identify what at the meat complaints stand. That's before the I granted access. Let's review very quickly
our conditional access policies apply.
The first point to make here is that if modern one condition is configured in the policy, are the conditions must be satisfied to tree get out policy. So if we have a policy that history conditions
and harder for the policy to apply to a user, all tree conditions must be met. So in this case, because Brenda scenario matches artery conditions, the policy will apply to bring their on access will be granted.
if modern one connection access policy apply street user all policies that apply must be satisfied.
So if we have to conditional access policies one of them allowing access and you're the blocking access.
If a user fits the conditions in both policies, access will be blog's, even if another policy that allows access applies to them. In this case, access we blood for Brenda, even though this, under the policy that applies to bring that allows access. This means that block access trumps all of the configuration settings
in the event off. Multiple policies applying
their best practices that are recommended to follow when implementing conditional axes and failure to follow them could result in locking yourselves out from access and applications. The fuzz don't
not years block access control for any policy that includes all users are whole applications this configuration blood access to your entire organization, and it is definitely not a good idea. The second thing to avoid is the use off the required domain join or require complaints Device.
If a policy applies to Harvey's, is our whole applications.
If you're yet so avid domain joined device, I complained Divisie organization. You will not be able to get access with this policy configured in terms of what's though the first thing to go is to configure to break glass emergency accounts before configuring conditional access policies.
What will DENDYS will exclude the brig less account from all conditional access policies that
acquire extra verification or the results in a block access.
We also want to exclude service, account and service principles from any policy diary choirs. MFP Since MF cannot be completed, programmatically
want to avoid policies that applies to all users or whole cloud applications, except it's absolutely necessary before ruling out any new condition access policy.
It's important to ever lose your policy using the what if two off conditional access.
And finally, the best way to Vogler conditional access is to volleyed out in faces, a pliant quality to a small set off. Users verify it behaves as expected before volleying it out. So the wide organization here is a quick question for you.
Which of the following is not a best practice for implementing conditional access
off In one
excluding burglars account from conditional access policies that block success.
Exclude service accounts and service principles from any policy that requires MFP
applying policies that applies to all users on all cloud applications.
Evaluate. Your policy is under What if to
Roll out new policies in faces.
If a selected option to be applying policies
that applies to all users are no cloud applications, you would be correct.
So that is not a good practice to follow, except absolutely necessary and with adequate testing to not apply policies that applies to all Jesus and all cloud applications.
Here are some supplemental links for for the studies on the topics covered in this lesson,
Here's a summary of what we covered in this lesson
for study about by giving another view off what conditional access is.
But I looked at how it works to protect applications, explaining the two sides off conditions and controls
well, then discuss, um, common conditional access use cases, which includes blocking legacy authentication. On requiring Emery for different scenarios,
we covered our conditional access policies, applied
and finally would discuss some vital information on conditional access best practices.
Thanks very much for watching, and I'll see you in the next lesson.