Compliance control of iOS MDM devices with corporate security requirements

Expand all | Collapse all

Compliance Control allows you to monitor iOS MDM devices for compliance with corporate security requirements and take actions if non-compliance is found. Compliance Control is based on a list of rules. Each rule includes the following components:

To create a rule:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.

    Complete the following steps within 15 minutes. Otherwise, you may face an error when saving changes to the policy.

  4. In the policy Properties window, select the Compliance Control section.
  5. In the Compliance Control rules section, click Add.

    The Compliance Control Rule Wizard starts.

  6. Select the Enable rule check box if you want to activate the rule. If the check box is cleared, the rule is disabled.
  7. On the Non-compliance criteria tab, click Add criterion and select a non-compliance criterion for the rule. You can add multiple criteria. They are combined by the AND logical operator.

    The following criteria are available:

    • List of apps on device

      Checks whether the list of apps on the device contains forbidden apps or does not contain required apps.

      For this criterion, you need to select a check type (Contains or Does not contain) and specify the app's bundle ID. How to get the bundle ID of an app

    • Operating system version

      Checks the version of the operating system on the device.

      For this criterion, you need to select a comparison operator (Equal to, Not equal to, Less than, Less than or equal to, Greater than, or Greater than or equal to) and specify the iOS version.

      Note that the Equal to and Not equal to operators check for a full match of the operating system version with the specified value. For instance, if you specify 15 in the rule, but the device is running iOS 15.2, the Equal to criterion is not met. If you need to specify a range of versions, you can create two criteria and use the Less than and Greater than operators.

    • Management mode

      Checks the device's management mode.

      For this criterion, you need to select a mode (Supervised device or Non-supervised device).

    • Device type

      Checks the device type.

      For this criterion, you need to select a type (iPhone or iPad).

    • Device model

      Checks the device model.

      For this criterion, you need to select an operator (Included in the list or Not included in the list), and then specify models that will be checked or excluded from the check, respectively.

      To specify a model, type at least one character in the Identifier field, and then select the required model from the appeared list. The list contains mobile device codes and their matching product names. For example, if you want to add all iPhone 14 models, type "iPhone 14". In this case, you can select any of the available models: "iPhone 14", "iPhone 14 Plus", "iPhone 14 Pro", "iPhone 14 Pro Max".

      In some cases, the same product name may correspond to several mobile device codes (for example, the "iPhone 7" product name corresponds to two mobile device codes, "iPhone 9.1" and "iPhone 9.3"). Be sure that you select all of the mobile device codes that correspond to the required models.

      If you type a value that is not on the list, nothing will be found. However, you can click the OK button in the field to add the typed value to the criterion.

    • Device is roaming

      Checks whether the device is roaming (if you select True) or not (if you select False).

    • Device password was set

      Checks whether a password is set (if you select True) or not (if you select False).

      If you select True, select whether the device password must match (if you select Matches policy) or must not match (if you select Does not match policy) the settings specified in the Password Settings section.

    • Device free space

      Checks whether the amount of free space on the device becomes less than the threshold that you specify.

      For this criterion, specify the threshold amount of free space, and then select the measurement unit (GB or MB).

    • Device is not encrypted

      Checks whether the device is not encrypted.

      Data encryption is enabled by default on password-locked iOS devices (Settings > Touch ID / Face ID and Password > Enable Password). Also, the hardware encryption on a device must be set to At block and file level (you can check this parameter in the device properties: in the console tree, select Additional > Mobile Device Management > Mobile devices, and then double-click the required device).

    • SIM card has been changed

      Checks whether the device SIM card has been replaced or removed compared to the previous check state.

      You can also enable the check for inserting an additional SIM card.

      On eSIM compatible devices, the non-compliance detection cannot be removed by inserting the previously removed eSIM. This is because the device's operating system recognizes each added eSIM as a new one. In this case, you need to delete the compliance control rule from the policy.

    • Last sync earlier than

      Checks how long ago the device last synchronized with Administration Server.

      For this criterion, specify the maximum time after the last sync, and then select the measurement unit (Hours or Days).

      We do not recommend that you specify a value less than the value of the Updating frequency for information about devices parameter in the iOS MDM Server settings.

    If you specify criteria that contradict each other (for example, Device type is set to iPhone but the list of values of Device model, with the Included in the list operator selected, contains an iPad model), an error message is displayed. You cannot save such a rule.

  8. On the Actions tab, specify actions to be performed on the device if all specified non-compliance criteria are detected.

    Actions are performed during the compliance rule check, which happens every 40 minutes, and persist until the next synchronization with the Administration Server. To prevent repeat actions from a single instance of non-compliance, set the Updating frequency for information about devices parameter in the iOS MDM Server settings to 30 minutes.

    Add an action in one of the following ways:

    • Click the Add action button if the action should be taken on the device immediately after non-compliance is detected.
    • Click the Add postponed action button if you want to also set a time period in which the user can fix the non-compliance. If the non-compliance is not fixed within this period, the action is performed on the device.

    The following actions are available:

    • Send email message to user

      The device user is informed about the non-compliance by email.

      For this action, you need to specify the user's email address(es). If necessary, you can edit the default text of the email message.

    • Wipe corporate data

      All installed configuration profiles, provisioning profiles, the iOS MDM profile, and applications for which the Remove together with iOS MDM profile check box has been selected are removed from the device. This action is performed by sending the Wipe corporate data command.

    • Install profile

      The configuration profile is installed on the device. This action is performed by sending the Install profile command.

      For this action, you need to specify the ID of the configuration profile to be installed.

      When the non-compliance criteria selected for the rule are no longer detected on the device, you can revert the action by sending the respective command to the device.

    • Delete profile

      The configuration profile is deleted from the device. This action is performed by sending the Remove profile command.

      For this action, you need to specify the ID of the configuration profile to be removed.

      When the non-compliance criteria selected for the rule are no longer detected on the device, you can revert the action by sending the respective command to the device.

    • Delete all profiles

      All previously installed configuration profiles are deleted from the device.

      When the non-compliance criteria selected for the rule are no longer detected on the device, you can install the deleted configuration profiles one by one, by sending the respective command to the device.

    • Update operating system

      The device operating system is updated.

      For this action, you need to select the specific operation (Download and install, Download only, or Install only if you want to install a previously downloaded version) and the iOS version to be downloaded and/or installed.

    • Change Bluetooth settings (supervised only)

      For this action, you need to select whether you want to enable or disable Bluetooth on the device.

      When the non-compliance criteria selected for the rule are no longer detected on the device, you can revert the action by sending the respective command to the device.

    • Reset to factory settings

      All data is deleted from the device and the settings are rolled back to their default values.

    • Delete managed app

      For this action, you need to specify the bundle ID of the managed app that you want to delete from the device. An app is considered managed if it has been installed on a device through Kaspersky Security Center. How to get the bundle ID of an app

      When the non-compliance criteria selected for the rule are no longer detected on the device, you can revert the action by sending the respective command to the device.

    • Delete all managed apps

      All managed apps are deleted from the device. An app is considered managed if it has been installed on a device through Kaspersky Security Center.

      When the non-compliance criteria selected for the rule are no longer detected on the device, you can install the deleted apps one by one, by sending the respective command to the device.

    • Delete profile(s) of a specific type

      For this action, you need to select the type of the profile to be deleted from the device (for example, Web Clips or Calendar subscriptions).

      As soon as the non-compliance criteria selected for the rule are no longer detected on the device, the deleted profiles are automatically restored.

    • Change roaming settings

      For this action, you need to select whether you want to enable or disable data roaming on the device.

      When the non-compliance criteria selected for the rule are no longer detected on the device, you can revert the action by sending the respective command to the device.

    If you specify actions that contradict each other (for example, Enable Bluetooth and Disable Bluetooth at the same time, an error message is displayed. You cannot save such a rule.

  9. Click the OK button to save the rule and close the wizard.

    The new rule appears in the list in the Compliance Control rules section.

  10. In the Actions when user accounts are disabled in Active Directory section, you can configure the actions to perform on devices when a user account is disabled in Active Directory.

    These parameters require integration with Microsoft Active Directory.

    To enable the automatic wiping of data from devices associated with disabled accounts of Active Directory users, select the Wipe data from devices with disabled Active Directory user accounts check box and choose one of the following actions:

    • Wipe corporate data
    • Reset to factory settings

    If you use policy profiles, be sure to enable the wipe data option for the entire policy. When a user account is disabled in Active Directory, it is first removed from the Active Directory user group. As a result, the policy profile is no longer applied to this user account, so the data is not wiped from the device.

  11. Click the Apply button to save the changes you have made.

Mobile device settings are changed after the next device synchronization with Kaspersky Security Center.

Page top