MCAS comes in three subsets: Office 365 Cloud App Security, Azure Active Directory Cloud App, and Cloud App Discovery. Out of these, what you can do also depends on the MCAS edition you choose. Integrate with cloud service APIs such as AWS, Azure, Dropbox, and more.Share confidential data with a limited set of users.Here are some things you can do with this service: Classifies and protects sensitive information.Provides visibility into the access of apps and data.Freepik What is Microsoft Cloud App Security?Įssentially, Microsoft Cloud App Security works as a monitoring tool, a firewall, and an authenticator tool that protects your data and application at all times. One such tool is the Microsoft Cloud App Security (MCAS), a cloud access security broker (CASB) tool that comes with many features to protect your data, control access, and combat cyberthreats. A better solution would be to strike a balance between the cloud’s benefits and its security by leveraging technologies, tools, and streamlined security strategies. So, does this mean you must consider going back to on-prem applications? Not exactly because the benefits from cloud technologies are too huge to miss. Though moving to the cloud offers a ton of flexibility and scalability, it also comes with unique challenges, especially in terms of security, as it is accessed through the Internet. You recognize these apps from a Session control text under a column called Available controls.The last decade has seen a big push toward cloud-based applications and storage.

There are URLs that the application is using in place and you just have to turn on the session control with a policy. Session control supported applications are already ready to onboard for session control. There are three types of applications that you can onboard: When you have applications redirected towards a cloud app security, you first onboard those for a session control. Access control and session control uses the same application list. This article focuses on the session control, but the same application onboarding that is described later in this article is the same for Access Control side. Access Control controls the access to the cloud application from a native or browser client and session control provides a deeper control for actions in a browser client side. Access Control and Session ControlĬloud App Security provides two different control methods for its conditional access application control. You have to first onboard applications and create policies for it. When you redirect your authentications towards the Cloud App Security nothing happens yet. You do not have any control or monitor for anything that is happening in the session itself.Ĭonditional Access Session Control settings When accessing the application from an unmanaged device there is always a risk of data leakage when users downloads files or copies out the company data out a managed application. End users can access applications with browser from managed or unmanaged device. Traditionally we publish applications for end user with or without a multi-factor authentication. This article focuses on applications that can be used with a browser and centralized identity in Azure AD. You can find out more about Conditional access from our other articles.

When using Azure AD to publish applications for users you probably want to control their access to them with a Conditional Access that is a great tool for fine grained access control for any cloud applications integrated with Azure AD.

There is a great article of it in Bloggerz.cloud!

It’s more clever to migrate authentication services towards Azure AD. Active Directory Federation Services or something else. Centralized identity in Azure AD Application publishing typesĪpplications have been published for a long time for end users using centralized authentication e.g.

Cloudapp security