Forum Discussion
MDATP Integration - Unsanctioned Apps - Allow for some users?
PJR_CDF when you create a Policy in MCAS, you can apply a Filter so that the scope of the policy is limited to a Group of users
- Please note that this is applicable only for app discovery alerts, and not for the controls provided by ATP, Danny.
Thanks Dean_Gross
I can see how you can scope/filter some policy types to specific users and groups, but the exact scenario I am looking for as an example is, say I have a group of users I want to allow access to Jira for and block for all other users.
If I tag Jira as an unsanctioned app in the Cloud app catalog, I assume this blocks it for all users.
How can I create a policy to block for all users except a specific group?
If I search the cloud app catalog for atlassian Jira and choose "create policy from search" to scope the policy to Jira specifically, the criteria you can choose from to build your filter within the policy doesn't include the ability to add user or group scoping filters as shown in the attached screen grab.
I cant see that scoping sanctioned and unsanctioned apps per user/group is possible in this manner
If I create an access control policy I can scope the policy to specific users but the apps I can choose from are only the apps I have onboarded to Azure AD, not the entire list of apps from the cloud app catalog.
Thanks
Paul
shoando - That would not be a solution for us due to the limitations that a device can be a member of only one device group. Because we are also using MDATP web content filtering and we have the web content filtering policies deployed to several device groups for granularity. So you can imagine that if a user has the device in a group where a web content filtering policy is applied that for example blocks all categories but allows access to web mail, and the same user wants access to an Unsanctioned app (that's blocked via indicator on all devices) we cannot achieve this as if we do an allow indicator for that unsanctioned app and apply it to the group of devices that permits web mail access via web content filtering that would give access to the unsanctioned app to all devices in that group. And since a device can be a member of only one group we cannot do this.
And this example is just for one user. Imagine when you have 300 users that each want to access 30-40 different unsanctioned apps :). Hope the above makes sense.
- I think that a better approach would be to register Atlassian Cloud in Azure AD as an enterprise app and then use the Entitlement feature to grant the users access, see https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/atlassian-cloud-tutorial and https://docs.microsoft.com/en-us/azure/active-directory/governance/entitlement-management-overview
Hi Dean_Gross
Once an app has been onboarded/registered in Azure AD I could use a Conditional Access App Control policy to control access but I guess that would only work if the user was attempting to login to the app using their Azure AD credentials?
I think the sanction/unsanctioned function of MCAS is more applicable in scenarios where the decision of if an app allowed is more black and white, whereas the scenarios I am imagining are the ones that are more grey with some users needing access and others not (ie Twitter accessible just for users in Marketing and not visible or accessible in any way for other users). These perhaps also stray a little into more traditional firewall / access control / web filter type solutions as well.
Thanks for taking the time with your suggestions
Paul
