Managed Web Domains

With organizations moving towards a mobile-only workforce, securing web browsers has become an imperative requirement with respect to securing corporate data access on mobile browsers. It is also to be ensured that not all apps can access downloaded corporate documents, preventing any unauthorized data access or leakage. With Managed Web Domains, you can secure documents downloaded from certain URLs and ensure only managed apps can access these documents. Managed Web Domains is applicable only for Safari.

Advantages of Managed Web Domains

• Prevent sharing of data from managed apps to unmanaged apps, by default.
• Saving websites as PDF(available from iOS 8.0) is also completely restricted.
• Use Managed Web Domains, to containerize the corporate data on BYOD, without affecting the personal space.
• Optionally provision the URLs configured in Web Clips, through Managed Web Domains, to ensure documents downloaded from Web Clips can also be viewed securely through managed apps.
• No need for a specific browser app to be installed on the device, for implementing browser security as Managed Web Domains is applied on Safari

It is recommended to use ME MDM app as the default document viewer app, as it ensures there is no back up of the corporate data. All the corporate documents are stored and viewed within ME MDM app, thereby ensuring complete corporate containerization.

Pre-requisites

The only pre-requisite is that the devices must be running iOS 8.0 or later versions.

Policy Description

PROFILE SETTINGS	DESCRIPTION
URLs	Documents from the URLs specified here can be viewed securely only through managed apps.

Adding URLs in Managed Web Domains

The following table explains the various scenarios where Managed Web Domains can be used.

SCENARIO	EXAMPLE URL
Securing any documents downloaded from a website/domain.	Using example.com secures documents downloaded from example.com and all its sub-folders such as example.com/folder, example.com/folder/sub-folder etc., However, it doesn't secure downloads from sub-domain.example.com
Securing any documents downloaded from a sub-domain of a website.	Using sub-domain.example.com secures all documents downloaded from sub-domain.example.com and all its sub-folders such as sub-domain.example.com/folder, sub-domain.example.com/folder/sub-folder etc., However, it doesn't secure downloads from example.com or different-sub-domain.example.com
Securing any documents downloaded from all sub-domains of a website.	Using *.example.com secures all documents downloaded from any sub-domain of example.com as well as all its sub-folders such as sub-domain1.example.com/folder, sub-domain2.example.com/folder/sub-folder etc., However, it doesn't secure downloads from example.com
Securing any documents downloaded from a folder of a website.	Using example.com/folder secures all documents downloaded from example.com/folder as well as all its sub-folders such as example.com/folder/sub-folder etc., However, it doesn't secure downloads from example.com
Securing any documents downloaded from a folder of a website sub-domain.	Using sub-domain.example.com/folder secures all documents downloaded from sub-domain.example.com/folder as well as all its sub-folders such as example.com/folder/sub-folder etc., However, it doesn't secure downloads from example.com, example.com/folder, sub-domain.example.com, different-sub-domain.example.com
Securing any documents downloaded from a folder of any website sub-domain.	Using *.example.com/folder secures all documents downloaded from sub-domain1.example.com/folder, sub-domain2.example.com/folder as well as all its sub-folders such as sub-domain2.example.com/folder/sub-folder etc., However, it doesn't secure downloads from example.com, sub-domain.example.com
Securing any documents downloaded from a specific domain extension.	Using *.com secures all documents downloaded from example1.com, example2.com. However, it doesn't secure downloads from example1.gov, example2.org