Data separation

When using mobile devices, data of all kinds is accessed. Data protection conformity must be guaranteed. A distinction is made between company-owned devices, so-called “Corporate Owned devices” (COD) and user-owned devices, so-called “Bring Your Own Devices” (BYOD). For both types of use, Apple offers its own technologies for data separation for iOS and iPadOS. In the following, these on-board means and their implementation in Relution are described. Data separation on Android devices is described under Data separation →.


iOS – Corporate Owned Devices

Differentiation managed / unmanaged

Since iOS 12, Apple basically distinguishes between “managed” and “unmanaged” for the following apps and content:

Managed content

  1. Apps - pushed by Relution or installed via the Relution Enterprise Appstore, server configurable.
  2. Mail Accounts - configured by Relution via a policy.
  3. Contacts - loaded from managed mail account to the device (synchronized).
  4. Documents - loaded from managed mail account to the device (synchronized).

Unmanaged content

  1. Apps - installed by the user from the Apple AppStore, non-server configurable.
  2. Mail Accounts - configured on the device by user.
  3. Contacts - created by user.
  4. Documents - generated by user in unmanaged apps or received in unmanaged mail accounts.

An unmanaged app can be converted into a managed app by being pushed by Relution again. It replaces the unmanaged app of the same name on the device. However, unmanaged mail accounts, contacts and documents cannot be transferred to managed. On devices enrolled via User Enrollment, Relution does not take already installed apps under management either.


Access restrictions

In iOS, the data is separated on the system side by means of a policy that determines whether access to managed data from unmanaged apps is allowed or not. For this purpose, the configuration Restrictions → as part of a policy in Relution offers the following options:

  • Allow opening managed documents in unmanaged apps: If the option is disabled, documents from managed apps and accounts cannot be opened in unmanaged apps and accounts.
  • Allow unmanaged apps to read managed contacts and Allow managed apps to write unmanaged contacts: Both options only take effect if Allow opening managed documents in unmanaged apps is disabled.
  • Allow opening unmanaged documents in managed apps: If the option is disabled, documents from unmanaged apps and accounts cannot be opened in managed apps.
  • Also apply the “Allow opening …” settings for copy and paste: The two opening settings then also apply to pasting copied content between managed and unmanaged apps.
  • AirDrop targets considered as unmanaged: If the option is enabled, all AirDrop targets are treated as unmanaged.

Whether messages from a managed mail account may be moved to other accounts is defined per account in the configurations Exchange → (option Allow move, disabled by default) or Email (option Allow users to move messages to other accounts, enabled by default). For Exchange, the option also covers forwarding and replying from another account.

For example the following can be prevented:

  • A private app (e.g. WhatsApp) that sees business (Exchange) contacts.
  • A business mail is forwarded at will.
  • An attachment of a business mail is opened in any app (e.g. Dropbox).

Which web content iOS treats as managed, e.g. downloads from the intranet, is defined via the configuration Managed Domains →. Email domains can also be specified there so that the Mail app marks external recipients.


iCloud restrictions

In order to prevent the uncontrolled outflow of data, Relution offers the possibility to prohibit or at least restrict cloud accounts completely. The following functions can be switched off:

  • iCloud backups
  • iCloud keychain synchronization
  • Allow managed apps to store data in the iCloud
  • Saving photos in the iCloud
  • Synchronization of iCloud documents.

The restriction for managed apps also takes effect on unsupervised devices and with User Enrollment. The other iCloud restrictions are marked as deprecated on unsupervised devices (see the note under Functional restrictions).


Functional restrictions

Finally, there are some iOS system functions that are relevant from a data security perspective and can also be switched off by restriction:

  • AirDrop (can be switched off completely)
  • Share password
  • Access to Apple AppStore
  • Screenshots and recordings
  • Camera (can be switched off completely, also for in-app functions)
  • Creating and modifying accounts (Mail, Apple Accounts)
  • Bluetooth
  • Creation of VPN configurations
  • USB connections.

Many of these restrictions only take effect on supervised devices, including AirDrop, password sharing, App Store, account modification, changes to the Bluetooth settings, creation of VPN configurations and USB access. The restrictions for camera, iCloud backup, iCloud keychain, iCloud photos and iCloud documents also take effect on unsupervised devices, but are marked as deprecated there. In the portal, each option is marked with a corresponding badge.

Web URL block and allow lists (Blocked URLs, Permitted URLs) are not configured via restrictions but via the Web Content Filter → configuration. Individual apps can be blocked or allowed via the App compliance → configuration.


Per-app VPN

As an important data protection measure, iOS offers the option of permanently coupling the data connection of apps to a VPN connection, which in turn can be configured by the Relution server. This ensures that certain apps only run over the company’s own network and external access is prevented (intranet-only).

In Relution, the option Per App and Account VPN is enabled in the VPN configuration of a policy for this purpose. The apps that use this connection are defined in the App to VPN Mapping → configuration. This only works for apps that are installed and managed via Relution.


iOS – Bring Your Own Devices

Until iOS 12, it was common to use a container app on iOS BYOD devices that could be configured on the server side and thus ensured separation of business and private data.

In the meantime, however, iOS offers a built-in “container solution” to separate business from private applications and data. For this purpose, the device is added to Relution via User Enrollment → with a Managed Apple Account (Managed Apple ID in the portal). This installs an MDM profile on the device, allowing it to be managed via Relution. Technically, a distinction is then made between “managed” and “unmanaged” apps and content. This turns the iOS device into a “dual persona” device and completely separates the data. Restrictions can also be used to control whether data can be shared between “managed” and “unmanaged” apps. The restrictions that take effect with User Enrollment are also marked with a badge in the portal, including the options for opening documents, for contacts and copy and paste, for AirDrop targets, for iCloud synchronization of managed apps and for screenshots.

Different configurations can be loaded on the devices and managed via Relution:

  • Apps
  • VPN configuration
  • Notes (more system apps will follow in future iOS versions)
  • iCloud account
  • Keychain
  • Mail accounts / attachments
  • Calendar accounts / attachments.

If the MDM profile is removed, the configurations, accounts and certificates distributed via Relution are removed from the device. Managed apps are only removed as well if the Remove app on Enterprise Wipe option was enabled when they were installed (see App Installation →); on devices enrolled via User Enrollment, managed apps are always removed. The MDM profile is removed in Relution with the Delete action (see Unenroll devices →) or on the device itself.

How helpful was this article?