In this post, I will show you how you can integrate Azure AD’s Authentication Context with Defender for Cloud Apps to require step-up authentication for specific scenarios. Step-up authentication allows you to re-evaluate Azure AD Conditional Access policies when users take sensitive actions during a session.
To demonstrate this feature, we need to do the following steps:
- Create a (new) Authentication Context, aka “the tag”.
- Forward (all) traffic to Defender for Cloud Apps using Conditional Access App Control.
- Create a session policy in Defender for Cloud apps, and assign the Authentication Context (tag) to the policy.
- Create a Conditional Access policy to define what controls need to be in place for this Authentication Context.
1. Create Authentication Context (tag)
First, we’ll need to define the Authentication Context̀. This will be used to ‘tag’ resources or actions. Go to the Authentication Context blade in the Azure Portal, and create a new one.
2. Forward the traffic to Defender for Cloud Apps
Before we can control the session, we need to ‘proxy’ the specific application to Defender for Cloud Apps. In this demo, we use SharePoint Online. Let’s create a new policy to forward the traffic.
Create a new policy, and select your test user and application. For me, I selected Nestor Wilke and SharePoint.
Since session policies only apply to browser sessions, there is no need to forward desktop and mobile sessions.
On the session blade, select “Use Conditional Access App Control” and “Use custom policy“.
3. Create the session policy in Defender for Cloud Apps.
Now that the browser traffic is sent to Defender for Cloud Apps and the Authentication Context is in place, we can create the session policy in MDfCA. Head over to the Microsoft 365 Defender portal, and scroll down to Cloud Apps. Create a new session policy.
Don’t use a template for now, and pick the “Block activities” control type. Then, select OneDrive and SharePoint and the activity types of your choice, and make sure the policy will only apply to Nestor, our test user.
If your app is not listed, please ensure it is onboarded first. Deploy Conditional Access App Control for catalog apps with Azure AD – Microsoft Defender for Cloud Apps | Microsoft Learn
We don’t configure content inspection for now, but this can also be applied if needed. In the action section, select “Require step-up authentication” and pick the Authentication Context ‘tag’ that’s been created earlier.
4. Create a Conditional Access policy
In the last step, we will define what controls apply to the session when the specific action is executed and the authentication context is triggered. This will be configured in a conditional access policy. Create a new policy, and select the Authentication context on the Cloud apps or actions pane.
Now, let’s see how this looks for Nestor. When Nestor wants to access a file on OneDrive or SharePoint, the sessions is being redirected to Defender for Cloud apps. Also, the session policy kicks in.
Now, Nestor wants to copy, paste, or print the file, and is prompted to do a security check, basically the step-up authentication.
Nestor is now redirected, and the corresponding conditional access policies are re-assessed. First, Nestor is prompted for Azure MFA.
Next, the term of use is prompted.
After both actions are performed, Nestor is now redirected back to the file where he can continue to work.
Wrap things up
Defender for Cloups apps is a great tool for many use cases. In most cases, MDfA is a good starting point for BYOD access, guest access, or session control for high-risk or privileged sessions. Now with the step-up authentication feature, this brings in another layer of security. This example was just to show what you can do, but since it will use Conditional Access (Authentication Context) the sky is the limit.