Now Chrome\FireFox can receive data\send data from\to any other managed application in the device.Make Chrome\FireFox a managed application.The experience is similar for both Firefox and Chrome once the relevant Applocker file is in place. Use Applocker to Manage Chrome Firefox in Windows from Intune After the Applocker is pushed via the WIP policy.This approach is basically used for protecting and limiting data within an un-enlightened application which has now been made managed (which otherwise without the usage of applocker cannot be done) However If the user opens 2 tabs in chrome- first Gmail(personal) and second owa (corporate)- he would be able to move data between the two as the data is staying within the managed application. Now the data leakage from Chrome\Firefox to any unmanaged application is going to be protected. Rest of the settings in the WIP policy would be as applicable. ![]() xml format in the WIP policy in the below location. The file can be generated form any Windows 10 machine wherein Google Chrome\Firefox has been installed.Īn applocker for chrome would look like below- Use Applocker to Manage Chrome Firefox in Windows from Intune We will have to create an Applocker file and then deploy it to a user via WIP policy. (Note- The application becomes “Managed” and not “Enlightened” via the use of app locker file) Since Google Chrome is NOT an enlightened application by default, we can make use of an Applocker file to achieve a similar purpose which makes google chrome a managed application. if we want it to behave almost the same way any enlightened application behaves- can be used to restrict leakage of data to an unmanaged application. We would traditionally use this approach if we want to make Chrome\Firefox as a managed application from Intune(i.e. Using an Applocker XML for Chrome
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |