Print Download PDF Send Feedback

Previous

Next

Mobile Access for Smartphones and Tablets

In This Section:

Overview of Mobile Access for Smartphones and Tablets

Certificate Authentication for Handheld Devices

Managing Client Certificates

Remote Wipe

Managing Mobile Settings

Push Notifications

ESOD Bypass for Mobile Apps

MDM Cooperative Enforcement

System Specific Configuration

Instructions for End Users

Advanced Gateway Configuration for Handheld Devices

Overview of Mobile Access for Smartphones and Tablets

To manage your users and their access to resources, make sure to:

Certificate Authentication for Handheld Devices

For handheld devices to connect to the gateway, these certificates must be properly configured:

Managing Client Certificates

Check Point Mobile Apps for mobile devices can use certificate-only authentication or two-factor authentication with client certificates and username/password. The certificate is signed by the internal CA of the Security Management Server that manages the Mobile Access Security Gateway.

Manage client certificates in Security Policies > Access Control > Access Tools > Client Certificates..

The page has two panes.

Creating Client Certificates

Note - If you use LDAP or AD, creation of client certificates does not change the LDAP or AD server. If you get an error message regarding LDAP/AD write access, ignore it and close the window to continue.

To create and distribute certificates with the client certificate wizard:

  1. In SmartConsole, select Security Policies > Access Control > Access Tools > Client Certificates.
  2. In the Client Certificates pane, click New.

    The Certificate Creation and Distribution wizard opens.

  3. In the Certificate Distribution page, select how to distribute the enrollment keys to users. You can select one or both options.
    1. Send an email containing the enrollment keys using the selected email template - Each user gets an email, based on the template you choose, that contains an enrollment key.
      • Template - Select the email template that is used.
      • Site - Select the gateway that users connect to.
      • Mail Server - Select the mail server that sends the emails.

      You can click Edit to view and change its details.

    2. Generate a file that contains all of the enrollment keys - Generate a file for your records that contains a list of all users and their enrollment keys.
  4. Optional: To change the expiration date of the enrollment key, edit the number of days in Users must enroll within x days.
  5. Optional: Add a comment that will show next to the certificate in the certificate list on the Client Certificates page.
  6. Click Next.

    The Users page opens.

  7. Click Add to add the users or groups that require certificates.
    • Type text in the search field to search for a user or group.
    • Select a type of group to narrow your search.
  8. When all included users or groups show in the list, click Generate to create the certificates and send the emails.
  9. If more than 10 certificates are being generated, click Yes to confirm that you want to continue.

    A progress window shows. If errors occur, an error report opens.

  10. Click Finish.
  11. Click Save.
  12. From SmartConsole, install the Policy.

Revoking Certificates

If the status of a certificate is Pending Enrollment, after you revoke it, the certificate does not show in the Client Certificate list.

To revoke one or more certificates:

  1. Select the certificate or certificates from the Client Certificate list.
  2. Click Revoke.
  3. Click OK.

After you revoke a certificate, it does not show in the Client Certificate list.

Creating Templates for Certificate Distribution

To create or edit an email template:

  1. In SmartConsole, select Security Policies > Access Control > Access Tools > Client Certificates.
  2. To create a new template: In the Email Templates for Certificate Distribution pane, select New.

    To edit a template: In the Email Templates for Certificate Distribution pane, double-click a template.

    The Email Template opens.

  3. Enter a Name for the template.
  4. Optional: Enter a Comment. Comments show in the Mail Template list on the Client Certificates page.
  5. Optional: Click Languages to change the language of the email.
  6. Enter a Subject for the email. Click Insert Field to add a predefined field, such as a Username.
  7. In the message body add and format text. Click Insert Field to add a predefined field, such as Username, Registration Key, or Expiration Date.
  8. Click Insert Link to add a link or QR code and select the type of link to add.

    For each link type, you select which elements will be added to the mail template:

    • QR Code - Users scan the code with their mobile devices.
    • HTML Link - Users tap the link on their mobile devices.

      You can select both QR Code and HTML link to include both in the email.

      The text in Display Text is the text that shows on the link.

    a. Certificate and Site Creation - For users who already have a Check Point app installed. When users scan the CR code or go to the link, it creates the site and registers the certificate.

    • Select the client type that will connect to the site- Select one client type that users will have installed.
      • Capsule Workspace - An app that creates a secure container on the mobile device to give users access to internal websites, file shares, and Exchange servers.
      • Capsule Connect/VPN - A full L3 tunnel app that gives users network access to all mobile applications.

    b. Download Application - Direct users to download a Check Point App for their mobile devices.

    • Select the client device operating system:
      • iOS
      • Android
    • Select the client type to download:
      • Capsule Workspace - An app that creates a secure container on the mobile device to give users access to internal websites, file shares, and Exchange servers.
      • Capsule Connect/VPN - A full L3 tunnel app that gives users network access to all mobile applications.
    • Select which elements will be added to the mail template:
      • QR Code - Users scan the code with their mobile devices
      • HTML Link - Users tap the link on their mobile devices.
      • Display Text - Enter the text to show on the HTML link.
  9. Click OK.
  10. Optional: Click Preview in Browser to see a preview of how the email will look.
  11. Click OK.
  12. Publish the changes

Cloning a Template

Clone an email template to create a template that is similar to one that already exists.

To create a clone of an email template:

  1. Select a template from the template list in the Client Certificates page.
  2. Click Clone.
  3. A new copy of the selected template opens for you to edit.

Remote Wipe

Remote Wipe removes the offline data cached on the user's mobile device.

When the administrator revokes the internal CA certificate, a Remote Wipe push notification is sent, if the Remote Wipe configuration for the client enables Remote Wipe by Push Notification. Remote Wipe is triggered when the device gets the push notification.

Note: Remote Wipe by Push Notification works by best effort. There is no guarantee that the gateway will send the notification, or that the client will get it successfully.

If the device does not get the Remote Wipe push notification, Remote Wipe is triggered when the client does an activity that requires connection to the gateway while using a revoked internal CA certificate.

Remote Wipe send logs:

This feature is supported in R77.10 and higher.

To configure Remote Wipe:

  1. Run the command on the gateway.

    Syntax: cvpnd_settings <conf_file_path> {set|listAdd|listRemove} <name> <value>

    • To enable or disable Remote Wipe:
      [expert@hostname:0]# cvpnd_settings $CVPNDIR/conf/cvpnd.C set RemoteWipeEnabled {true|false}

      Remote Wipe is enabled by default.

    • To enable or disable Remote Wipe by Push Notification (wipe is done if client gets notification):
      [expert@hostname:0]# cvpnd_settings $CVPNDIR/conf/cvpnd.C set RemoteWipePushEnabled {true|false}

      The Remote Wipe Push Notifications feature is enabled by default. For supported clients, see sk95587.

    • To set supported devices for Remote Wipe Push Notifications, based on operating system:
      [expert@hostname:0]# cvpnd_settings $CVPNDIR/conf/cvpnd.C listAdd RemoteWipePushSupportedClientOS {iOS | Android}
  2. Run: [expert@hostname:0]# cvpnrestart

    You must restart the cvpn service to apply the changes.

To see that your changes are applied, open the $CVPNDIR/conf/cvpnd.C file in Read-Only mode.

To trigger Remote Wipe on a device:

  1. Make sure that cvpnd.C is configured for Remote Wipe and, if you want, for Push Notifications.

    If you change the file, run: [expert@hostname:0]# cvpnrestart

  2. Revoke the client certificate:
    1. Open Mobile Access tab > Client Certificates.
    2. Select certificates.
    3. Click Revoke.
    4. Click OK.

To see Remote Wipe logs:

  1. Open SmartLog.
  2. Query for: "Remote Wipe" AND blade:"Mobile Access" action:"Failed Log In"

    You can filter these results for user DN, device ID, or certificate serial number.

Managing Mobile Settings

For Capsule Workspace, many settings that affect the user experience on mobile devices come from the Mobile Profile. Each Mobile Access user group has an assigned Mobile Profile. By default, all users get the Default Profile.

The settings in the Mobile Profile include:

Manage the Mobile Profiles in Mobile Access tab > Capsule Workspace Settings.

Creating and Editing Mobile Profiles

To create or edit a Mobile Profile:

  1. In SmartConsole, select Security Policies > Shared Policies > Mobile Access and click Open Mobile Access Policy in SmartDashboard.

    SmartDashboard opens and shows the Mobile Access tab.

  2. From the navigation tree, click Capsule Workspace.
  3. Optional: Create a new Mobile Profile, click New.
  4. In the Mobile Profiles pane select the profile and click Edit.

    The Mobile Profile opens.

  5. Change settings. See Capsule Workspace Settings in the Mobile Profile.
  6. Click Save and then close SmartDashboard.
  7. From SmartConsole, install the policy.

Capsule Workspace Settings in the Mobile Profile

  1. In the Access Settings area, configure:
    • Session timeout - After users authenticate with the authentication method configured in Gateway Properties > Mobile Access > Authentication, configure how long they stay authenticated to the gateway.
    • Activate Passcode lock - Select to protect the Business Secure Container area of the mobile device with a passcode.
      • Passcode profile - Select a passcode profile to use. The profile includes the passcode complexity, length, expiration, and number of failed attempts allowed.
      • Allow storing user credentials on the device for single-sign on - If username and password authentication is used, store the authentication credentials on the device. Then users are only prompted for their passcode not also for their username and password.
    • Report jail-broken devices - Create a log if a jail-broken device connects to the gateway.
      • Block access from jail-broken devices - Block devices that are jail-broken from connecting to the gateway.
    • Track user's GPS location (upon user's approval) - Tracks devices connecting to the gateway.
  2. In the Allowed Items area, select which Exchange features are available on devices:
    • Mail
    • Calendar
    • Contacts
    • Notes (iOS only)
  3. In the Offline Content area, configure what data is saved and for how long when the Check Point App cannot reach the gateway.
    • Mail from the last x days - Select the length of time from which emails are saved.
      • Cache Mail - Select which parts of the email are saved in the offline cache.
    • Calendar from the last x months and the following x months - Select which parts of the calendar are saved: the length of time in the past and length of time in the future.
      • Cache Calendar - Select which parts of the calendar entry are saved in the offline cache.
    • Synchronize contacts - Synchronize contacts so they are available offline.
  4. In the Push Notifications area, select if you allow push notifications on devices and which notification templates to use. See Push Notifications for details. To use this, push notifications must be enabled for Capsule Workspace on the gateway that users connect to.
  5. In the Mail area, select Allow copy paste of mail content if you allow contents of emails to be pasted into other apps.
  6. In the Calendar area, select Allow business calendar to sync to the device's native calendar if you want to sync both calendars on the device. Events from Capsule Workspace will show in the device's calendar, outside of Capsule Workspace.
  7. In the Contacts area, select which additional contacts to show on the device:
    • Global Address List
    • Local Phone
  8. In the Check Point Capsule Docs area, select the Capsule Docs information that is stored in Capsule Workspace:
    • Allow caching Check Point Capsule Docs credentials - The credentials are required to open Capsule Docs protected documents are cached on the device. If they are not cached, users must enter their credentials each time they open a document for the first time.
    • Allow caching Check Point Capsule Docs keys - The Capsule Docs keys are cached on the device. If they are cached users can open a previously opened document with no need to enter credentials.

Managing Passcode Profiles

A passcode lock protects Capsule Workspace in mobile devices. In each Mobile Profile, configure which Passcode Profile it uses. The profile includes the passcode requirements, expiration, and number of failed attempts allowed. The default passcode profiles are Normal, Permissive, and Restrictive. You can edit the default profiles and create new profiles.

To manage Passcode Profiles:

  1. In SmartConsole, select Security Policies > Shared Policies > Mobile Access and click Open Mobile Access Policy in SmartDashboard.

    SmartDashboard opens and shows the Mobile Access tab.

  2. From the navigation tree, click Additional Settings > Passcode Profile.
  3. To create a new Passcode Profile, click New.
  4. Configure the settings for the profile.
  5. Click Save and then close SmartDashboard.
  6. From SmartConsole, publish the changes.

Passcode Profile Settings

A Passcode Profile includes these settings:

Push Notifications

This feature sends push notifications for incoming emails and meeting requests on handheld devices, while the Mobile Mail app is in the background. The app icon shows the number of new, unhandled notifications. One user can get notifications for multiple devices.

Push notifications are disabled by default, but enabled when you run the Mobile Access First Time Wizard.

To use push notifications, the gateway must have connectivity to these URLs on ports 443 and 80:

Configuring Push Notifications

To enable push notifications:

Enable push notifications from the Mobile Access Wizard or from the Gateway Properties of each gateway.

Customizing Push Notifications

Customize push notifications from the mobile profile in the Mobile Access tab > Capsule Workspace Settings.

You can customize templates for Mail and Meeting notifications.

To see the default notifications or change the notifications:

  1. From SmartDashboard > Mobile Access tab > Capsule Workspace Settings, open a Mobile Profile.
  2. Under Push Notifications, click Manage.

Exchange Server and Gateway Communication

Make sure that the Exchange server can access the Mobile Access Portal.

On R77.20 and higher gateways, all confidential information between the Exchange server and the gateway uses encrypted SSL tunnels. Non-confidential information can use unencrypted HTTP connections.

You can configure all push notification communication to use SSL tunnels.

By default, Kerberos authentication is not enabled for Push Notification registration to the Exchange server. To enable it, follow the instructions in sk110629.

To force all push notification communication to go through SSL tunnels:

  1. Install a trusted server certificate on the Mobile Access gateway. See sk98203.
  2. Open GuiDBedit Tool (sk13009).
  3. Search for the field main_url (Ctrl +F).
  4. Press F3 to see next main_url until you find main_url that contains the value ExchangeRegistration.
  5. Double-click the ExchangeRegistration main_url field and edit the value to be https:// and not http://.
  6. Save.
  7. Open SmartDashboard.
  8. Open the Mobile Access gateway object.
  9. Click OK.
  10. Install policy.

On R77.10 gateways, if the certificate on the Security Gateway is not trusted, import the certificate to the Exchange Server. This is not necessary on R77.20 and higher gateways. For details about how to get the gateway certificate, see sk98203.

To import a certificate to the Exchange server:

  1. Download the certificate to the Exchange server.
  2. Run the Windows certificate installation wizard: double-click the certificate file, and follow the wizard steps.
  3. Run Microsoft Management Console.
  4. In the window that opens, click File > Add/Remove Snap-in.

    Add or Remove Snap-ins window opens.

  5. Select Certificates from the Available snap-ins, and click Add.
  6. Select My user account and click Finish.
  7. Select Certificates and click Add again.
  8. Select Computer account and click Next.
  9. Click Finish.
  10. Click OK.

    The certificate is stored in Local computer and in Current user stores.

Push Notification Status Utility

Use the Push Notification Status Utility to understand if your environment is configured correctly for push notifications.

Run $CVPNDIR/bin/PushReport to generate a report that contains this data:

  1. License - Shows if the license is valid or if you have an evaluation license.
  2. Configuration - Shows if push notifications are configured and enabled in the database.
  3. Connectivity - Shows if you have a connection to the Check Point Cloud and CRLs list.
  4. Callback URL - Shows the configured callback URL. If it is an https URL, the utility shows that a certificate is needed.

Output Example

[admin@gw-105 bin]# PushReport

This is your configuration status:

==================================

Topic               Status              Description

-----------------------------------------------------------------------------

License             OK                  You are not using an evaluation license

Configuration       OK                  Push is enabled in configuation

Connectivity        OK                  You have connectivity to cloud

Callback URL        OK                  Your callback push url is: http://198.51.100.2/ExchangeRegistration. Make sure you have internal connectivity to this URL.

Monitoring Push Notification Usage

Use the fwpush commands to monitor, debug, and troubleshoot push notification activity.

Note - Users must first install the latest version of the Capsule Workspace app from the app store and connect to the site created on the gateway.

To see failed batches, expired push notifications, and delayed push notifications, see: $FWDIR/log/pushd_failed_posts

Legal disclaimer on product functionality

Check Point uses Apple and Google services to deliver push notifications to iOS and Android devices. This is consistent with industry practice and similar to other applications vendors. Accordingly, Check Point assumes no liability in the event a notification is not sent or is not successfully pushed.

Information which is sent as a push notification passes through Check Point’s push service and the Apple or Google push service (according to the user’s device). Check Point does not keep, filter, or read any information that passes through. Check Point may review basic information to determine if a push notification reached its destination.

Check Point provides configuration options for the information sent as a push notification. The administrator can choose whether to set the subject, the sender, or the importance of any email, and can send the meeting location for meeting invitations.

Check Point will not be held liable for any loss of information that may result during the push notification process.

ESOD Bypass for Mobile Apps

Hand-held devices cannot run Endpoint Security on Demand (ESOD) components. By default, ESOD is disabled for smartphones and tablets.

If your organization has ESOD enabled, mobile apps cannot access ESOD enforced applications.

Note - Mobile apps are not recognized by their HTTP User-Agent header.

To change the ESOD setting on the Security Gateway:

  1. On the Security Gateway run:
    cvpnd_settings $CVPNDIR/conf/cvpnd.C set MobileAppBypassESODforApps "true" or "false"
    • true - Bypasses ESOD for mobile apps (default).
    • false - Does not bypass ESOD.
  2. Restart the Mobile Access services: cvpnrestart
  3. If you use a cluster, copy the $CVPNDIR/conf/cvpnd.C file to all cluster members and restart the services on each.

MDM Cooperative Enforcement

Support for Mobile Device Management (MDM) through third-party vendors enforces a unified security policy for devices that access internal resources. Only managed devices that comply with the organizational security policy can successfully connect and access your business resources.

This feature is supported in R77.10 and higher.

Check Point Apps establish a secure VPN connection to the corporate network through a Check Point Security Gateway. The Security Gateway queries the policy of the MDM server. The MDM server verifies the compliance level of employees' mobile devices when the VPN connection is established. The Security Gateway uses the MDM results to allow or block access, according to the device security and the user's permissions.

This feature is supported by Check Point Capsule Connect and Capsule Workspace clients.

For the most updated vendor information see sk98201.

To configure MDM Cooperative Enforcement with iOS 7, see sk98447.

Overview of the MDM Enforcement workflow:

  1. Before you start you must have:
    • An MDM account set up with required vendor license, if necessary
    • Necessary licenses for Capsule Connect or Capsule Workspace
    • Users with supported iOS or Android devices
  2. Configure MDM on the Mobile Access Security Gateway. Edit the global options and vendor options.
  3. For iOS 7 only: Configure settings and policy for your MDM vendor. See sk98447.
  4. Make sure that the MDM functionality works - from a mobile device or Security Gateway console.

Configuring MDM on the Security Gateway

Enable MDM Enforcement in a configuration file on the gateway. Then define global options and vendor-specific options.

To configure Mobile Device Management on a Security Gateway:

  1. Open the Gaia shell on the Security Gateway.
  2. Log in to expert mode.
  3. Open this file to edit: $FWDIR/conf/mdm.conf
  4. Edit the global options.

    MDM is disabled by default. You must change enabled to 1.

  5. Edit the vendor options.
  6. Save the file.
  7. Test the configuration.
  8. Install policy.

Global Options

mdm.conf Options

Description

enabled

0 - MDM disabled

1 - MDM enabled

monitor_only

0 - Full enforcement: non-compliant mobile devices cannot log in.

1 - Monitor only: non-compliant devices can log in and attempts are logged.

fail_open

Defines behavior for cases of uncertainty, when an error occurs while checking MDM status.

0 - Drop VPN connections when an error occurs while checking MDM compliance status.

1 - Allow VPN connections when an error occurs while checking MDM compliance status.

session_timeout_in_sec

Maximum seconds allowed to determine device compliance status between the gateway and the MDM cloud service. Starts at device login. If passed, the action of fail_open starts. Recommended: keep default.

active_vendor

Name of active third-party vendor, to test MDM compliance. You can configure multiple MDM vendors, but only one can be active.

password_is_obscured

0 - password parameters in mdm.conf show in clear text.

1 - password parameters in mdm.conf show strings. See Obscuring Passwords. Recommended: keep default (1).

verify_ssl_cert

0 - SSL certificates not verified when gateway accesses MDM cloud services.

1 - SSL certificates verified. Prevents some DNS poisoning, spoofing, man-in-the-middle attacks against gateway. Recommended: keep default (1). If the MDM server is in a cloud, this parameter must be 1. If you change it, the devices will be vulnerable to MITM attacks. (This risk is lower if the MDM server is local.)

ssl_ca_bundle_path

Local path on gateway of known CA certificate files. You can add more certificates to those that come with installation. Recommended: keep default.

ssl_cipher_list

Allowed ciphers for HTTPS between gateway and MDM cloud services. Recommended: keep default.

ssl_use_tls_v1

To use TLSv1 or SSL for HTTPS between gateway and MDM cloud services. Recommended: keep default.

Vendor Options

In mdm.conf, there is a block of options for each vendor. You can add more, if you have an understanding of the vendor's API and expertise with PHP programming. See Advanced Vendor Support.

For the most updated vendor information see sk98201.

Obscuring Passwords in mdm.conf

If the global property password_is_obscured is enabled, obscure all parameters named password in the Vendor Configuration blocks.

To get an obscured password string from your password:

  1. Run: [expert@hostname:0]# obfuscate_password <password>

    The output is a string. For example: 33542b323a3528343640

  2. Copy the string to the mdm.conf file, as the password value.
  3. Save the file.
  4. Install policy.

Advanced Vendor Support

You can add more vendors. This requires PHP programming skills and an understanding of the third-party MDM vendor's cloud API.

In these steps, we use "BestMDM" as the name of a fictional MDM vendor. BestMDM's API requires an XML request to be sent to their URL that includes credentials and the ID of the device. It returns an XML response with the device status and reason.

Example Request:

<request>

<username>api_username</username>

<password>api_password</password>

<device>device_id</device>

</request >

Example Response:

<response>

<status>compliance_status_code</status>

<reason>reason</reason>

</response >

Example URL: https://bestmdm.com/api

We use these examples in the steps.

To add support for a new third-party vendor:

  1. Open to edit: $CVPNDIR/phpincs/MDMVendors.php
  2. Search for the text: to add another vendor
  3. Remove the comment for a case branch.
  4. Enter your MDM vendor name.

    For example:

    case "BestMDM":

    BestMDM($mdm_data);

    break;
  5. At the end of the file, add a new PHP function. It must access the vendor's cloud API, and return a status and reason array.

    For example:

    function BestMDM($mdm_data) {

    // Build the request XML

    $request_xml = new

    SimpleXMLElement("<request><username/><password/><device/></request>");

    // Fill its fields with data from $mdm_data.

    // Note that "username", "password" and "device_id" always in $mdm_data.

    $request_xml ->username = $mdm_data["username"];

    $request_xml->password = $mdm_data["password"];

    $request_xml->device = $mdm_data["device_id"];

    // Make POST request using the supplied class URLRequest

    // (The class URLRequest is defined in the same .php file).

    $url = "https://bestmdm.com/api";

    $conn = new URLRequest(); // open HTTP/HTTPS request session

    $resp_data = $conn->Request( $url, $post_body = $xml->asXML() );

    // Handle possible network error.

    If ($resp_data === FALSE)

    return array("status"=>MDM_ERROR, "reason"=> $conn->get_error_message());

    // Now $resp_data is raw string returned by the cloud API. Parse it as XML:

    $resp_xml = new SimpleXMLElement($resp_data);

    // Check the status codes returned by the vendor’s API.

    $status = MDM_ERROR;

    switch ($resp_xml->status) {

    case "not_managed":

    return array("status"=>MDM_NOT_MANAGED, "reason"=>"");

    case "compliant":

    return array("status"=>MDM_COMPLIANT, "reason"=>"");

    case "not_compliant":

    return array("status"=>MDM_NOT_COMPLIANT, "reason"=>$resp_xml->reason);

    default:

    return array("status"=>MDM_ERROR, "reason"=>"unknown status");

    } // end switch

    } // end BestMDM compliance protocol handler

    Status Codes:

    • MDM_ERROR - Error occurred while accessing the MDM vendor’s Cloud API.
    • MDM_NOT_MANAGED - The device is not registered in the vendor’s database.
    • MDM_NOT_COMPLIANT - The device is known to the vendor as "not compliant with its policy".
    • MDM_COMPLIANT - The device is known to the vendor as "compliant with its policy".

  6. Define $mdm_data as an array of data from mdm.conf and the device ID.

    Array(

    "device_id"=><MAC address of device, or other ID known by the vendor>,

    "username"=><username to access the API of the MDM vendor>,

    "password"=><password to access the API of the MDM vendor>

    )

    Important Notes:

    • Global parameters and vendor parameters are merged in one list.
    • If a vendor parameter is the same name as a global parameter, the vendor parameter overrides the global parameter.
    • If $mdm_data includes a password parameter, and password_is_obscured=1, the password is decrypted automatically. The function gets the clear text password.

    Example of $mdm_data:

    With mdm.conf:

    $mdm_data value:

    (

    :enabled (1)

    :monitor_only (0)

    :fail_open (0)

    :active_vendor (BestVendor)

    :BestVendor (

    :username (MyUser)

    :auth_key (12345)

    )

    )

    Array(

    "enabled"=>1,

    "monitor_only"=>0,

    "fail_open"=>0,

    "active_vendor"=>"BestVendor",

    "username"=>"MyUser",

    "auth_key"=>"12345",

    "device_id"=>"12:34:56:78:9A:BC:DE:F0"

    )
  7. Save MDMVendors.php.
  8. Open $FWDIR/conf/mdm.conf.
  9. Add a section after the last block for the new vendor.

    For example:

    :BestMDM (

    :username (MyUserName)

    :password (123456)

    )
  10. Change the value of active_vendor to be the name of the new vendor.

    For example: :active_vendor (BestMDM)

  11. Save the file.
  12. Install policy.

Testing MDM

To make sure that MDM functionality is configured correctly:

  1. On a mobile device, launch the Check Point Mobile app.
  2. Connect to the Security Gateway.
  3. Look for Mobile Access login logs in SmartLog.

    The Compliance Check, Information, and Reason values in the details of the device login, show data about MDM compliance status and requirements.

Advanced Testing

You can make sure the MDM configuration works without a device in hand, but it requires expert knowledge. You log in to a test web page and enter the WiFi MAC address of a real device. For security, the MDM test page is disabled by default.

To enable the test page:

  1. Log in to the Security Gateway console in expert mode.
  2. Save a backup of $CVPNDIR/conf/includes/Login.location.conf.
  3. Open Login.location.conf to edit.
  4. Search for test your integration, and carefully follow the instructions there.
  5. After you make required changes, save the file and run: [expert@hostname:0]# cvpnrestart
  6. Open the Mobile Access Portal with the /Login/MDMProxy path.

    For example: https://<gateway_hostname>/sslvpn/Login/MDMProxy

  7. Enter the device MAC address.
  8. Click Submit.

    If there are issues for that device to access the third-party MDM vendor, the page shows diagnostics.

  9. Revert Login.location.conf to the backup file.
  10. Run: [expert@hostname:0]# cvpnrestart

To prevent security risks, always revert and close the test page.

Example Diagnostics:

System Specific Configuration

This section describes system specific configuration required for iPhones, iPads, and Android devices. In some instances, end-user configuration is also required.

iPhone and iPad Configuration

Connecting iPhone/iPad Clients to ActiveSync Applications

When you allow access to an ActiveSync application, users see the ActiveSync Setup item and can install the ActiveSync profile. This gives users access to their corporate email.

Note - If your ActiveSync application requires a client certificate to connect, the ActiveSync profile will work only if a client certificate is also required for Capsule Workspace.

The next procedure is for end users to configure on their devices. For all end user configuration procedures, see Instructions for End Users.

To connect to corporate email:

  1. Sign in to the Mobile Access site.
  2. Tap Mail Setup.
  3. Do the on-screen instructions.

Getting Logs from iPhones or iPads

To resolve issues with client devices, tell the users to send you the logs. The iPhone or iPad must have an email account set up.

The next procedure is for end users to configure on their devices. For all end user configuration procedures, see Instructions for End Users.

To configure logs:

  1. Tap the i icon.

    Before login, this is on the top right. After login, this is on the bottom right.

  2. Tap Report a Problem on the navigation bar.

    If you do not have an email account configured on the iPhone, a message shows that one must be configured. After this is done, you must open Check Point Mobile Access again.

    When an email account is configured, the email page opens. The logs are attached.

Note - The email account that the iPhone uses to send the email is the default account. This might not be your organization's ActiveSync account.

If the iPhone is not configured for a destination email address for logs, the email that opens has an empty To field. You can enter the destination address now, or set up a default destination address for Check Point Mobile logs.

Disabling Client SSO

Single Sign On (SSO) lets users in a session connect to the Mobile Access gateway, without authenticating when the client starts. If a user cannot access the gateway while SSO is enabled, disable it.

The next procedure is for end users to configure on their devices. For all end user configuration procedures, see Instructions for End Users.

To disable SSO on a client:

  1. Tap Settings.
  2. Scroll down to the Check Point Mobile icon and tap it.
  3. In the Mobile global settings, tap the Single Sign On > Enabled switch.

Android Configurations

Browsing to Servers with Untrusted Server Certificates

When browsing from the Android app to a server with an untrusted server certificate, you are denied access and you get this message:

"Some resources on this page reside on an untrusted host."

In some cases, such as in a staging or demo environment, you can enable browsing to servers with untrusted certificates.

Important - Disabling the server certificate validation in the client app is forbidden for production setups since it allows any 3rd-party to intercept the SSL traffic.

Session Timeout for Android Devices

For Androids, idle timeout cannot be modified or enforced by the device or the gateway.

The only timeout setting that applies to the device is the active session timeout. It is configured in SmartDashboard: Mobile Access Software Blade > Additional Settings > Session > Re-authenticate users every x minutes option. This setting indicates the maximum session length. When this period is reached, the user must log in again. For example, if re-authentication is set to 120 minutes, a user will need to log in again after 2 hours in an active session.

Getting Logs from Android Clients

To resolve issues with client devices, tell the users to send you the logs.

The next procedure is for end users to configure on their devices. For all end user configuration procedures, see Instructions for End Users.

To send logs:

  1. Open the Check Point application.
  2. Tap About.
  3. Press the Menu button on the device.
  4. Tap Send Logs.
  5. Select a way to send the logs.

Instructions for End Users

Give these instructions to end users to configure their mobile devices to work with Mobile Access.

iPhone/iPad End User Configuration

Do these procedures on your iPhone/iPad so you can work with Mobile Access.

Before you start, make sure that your administrator gives you:

Important - Do only the procedures that your network administrator has instructed you to do.

To connect to the corporate site:

  1. Get Check Point Capsule Workspace from the App Store.
  2. When prompted, enter the:
    • Site Name
    • Registration key

To connect to corporate email:

  1. Sign in to the Mobile Access site.
  2. Tap Mail Setup.
  3. Do the on-screen instructions.
  4. When asked for the password, enter the Exchange password.

To configure logs:

  1. Tap Information.

    Before login, this is on the top right. After login, this is on the bottom right.

  2. Tap Report a Problem on the navigation bar.

    If you do not have an email account configured on the iPhone, a message shows that one must be configured. After this is done, you must open Check Point Mobile Access again.

    When an email account is configured, the email page opens. The logs are attached.

Note - The email account that the iPhone uses to send the email is the default account. This might not be your organization's ActiveSync account.

If the iPhone is not configured for a destination email address for logs, the email that opens has an empty To field. You can enter the destination address now, or set up a default destination address for Check Point Mobile logs.

To disable SSO on a client:

  1. Tap Settings.
  2. Scroll down to the Capsule Workspace icon and tap it.
  3. In the Mobile global settings, tap the Single Sign On > Enabled switch.

Android End User Configuration

To disable the server certificate validation for Web applications:

  1. Launch the Check Point Mobile app.
  2. Log in to the site.
  3. Press the menu button and tap Settings.
  4. Enable Allow connection to untrusted servers.

To disable the server certificate validation for Web applications:

  1. Launch the Check Point Mobile app.
  2. Log in to the site.
  3. Press the menu button and tap Settings.
  4. Enable Allow connection to untrusted servers.

Do these procedures on your Android device so you can work with Mobile Access.

Before you start, make sure that your administrator gives you:

Important - Do only the procedures that your network administrator has instructed you to do.

To connect to the corporate site:

  1. Get the Check Point Mobile app from the Android Market.
  2. When prompted, enter the:
    • Site Name
    • Registration key

To send logs:

  1. Open the Check Point application.
  2. Tap About.
  3. Press the Menu button on the device.
  4. Tap Send Logs.
  5. Select a way to send the logs.

To transfer the client certificate to the 3rd party mail client:

  1. Launch the Check Point Mobile app.
  2. Log in to the site.
  3. Press the menu button and tap Settings.
  4. From the Export Certificate option, tap Export. The Export Certificate window opens.

    If the Export Certificate option is disabled, contact the system administrator.

  5. Select the certificate format appropriate for your mail client: P12 or PFX.
  6. Select the location to save the certificate.
    The default path is /sdcard (for devices that have an SD card) or an external resource folder (for devices that do not have an SD card).
  7. Tap OK to save the certificate to the selected location.

    A window shows: Export succeeded. Certificate password is: _______

  8. You can copy the password to the clipboard. You will need the password when you import the certificate to the third party mail app.

Advanced Gateway Configuration for Handheld Devices

You can customize client authentication, device requirements, certificate details, and ActiveSync behavior. Use the CLI commands explained here to change the configuration file:
$CVPNDIR/conf/cvpnd.C

Note - Disable Link Translation Domain on Mobile Access gateways before you connect to them with the Android client.

To apply changes:

Restart the Mobile Access services: cvpnrestart

If you use a cluster, copy the $CVPNDIR/conf/cvpnd.C file to all cluster members and restart the services on each.

To set Mobile Access attributes:

cvpnd_settings set <attribute_name> "<value>"

To get the current value of an attribute:

cvpnd_settings get <attribute_name>

Attribute

Description

ActiveSyncAllowed (true)

If access to ActiveSync applications is allowed.

ActiveSyncExchangeServerAuthentication
Method (basic)

Method of forwarding authentication from the Mobile Access gateway to the internal Exchange server.

Valid values: basic, digest, ntlm

MobileAppAllowActiveSyncProfileConfig (true)

Make the automatic ActiveSync Profile configuration for iPhones and iPads available to users.
If true, only users with authorization to access ActiveSync applications see this feature.
If false, no user sees this feature.

MobileAppMinRequiredClientOSVersion (3.1)

Minimum operating system version for iPhones and iPads. If a client fails this requirement, user sees
Your OS version must be upgraded

MobileAppAndroidMinRequiredClient
OSVersion (2.1)

Minimum operating system version for Android. If a client fails this requirement, user sees
Your OS version must be upgraded

MobileAppMinRecommendedClient
OSVersion (3.1)

Recommended operating system version for iPhones and iPads. If a client fails this recommendation, user sees a message but usage continues.
Note: value must be equal to or greater than Required value, or Mobile Access will not start.

MobileAppAndroidMinRecommendedClient
OSVersion (2.1)

Recommended operating system version for Android. If a client fails this recommendation, user sees a message but usage continues.
Note: value must be equal to or greater than Required value, or Mobile Access will not start.

MobileAppMinRequiredClientAppVersion (1.3)

Minimum App version required for iPhones and iPads.
If a client fails this requirement, user sees
Application Update Required

MobileAppAndroidMinRequiredClient
AppVersion (1.0)

Minimum App version required for Android.
If a client fails this requirement, user sees
Application Update Required

MobileAppMinRecommendedClient
AppVersion (1.3)

Recommended App version for iPhones and iPads.
If a client fails this recommendation, user sees a message but usage continues.
Note: value must be equal to or greater than Required value, or Mobile Access will not start.

MobileAppAndroidMinRecommendedClient
AppVersion (1.0)

Recommended App version for Android.
If a client fails this recommendation, user sees a message but usage continues.
Note: value must be equal to or greater than Required value, or Mobile Access will not start.

MobileAppMinClientOSVersionForProfile
Config (3.1)

Minimum operating system version for iPhone and iPad to configure ActiveSync with the app.

If you want data encryption, change this value from the default to 4.0. Make sure the ActiveSync policy (configured on the Exchange server) enforces data encryption.

MobileAppAndroidMinClientOSVersionFor
ProfileConfig (2.1)

Minimum operating system version for Android to configure ActiveSync with the app.
If you want data encryption, change this value from the default to 3.0. Make sure the ActiveSync policy (configured on the Exchange server) enforces data encryption.

MobileAppBypassESODforApps (false)

When true, mobile apps are allowed access to MAB applications whose protection level requires ESOD compliance.

Mobile apps can always access the MAB portal.

MobileAppAllowClientCertExport (false)

When true, allows mobile app clients to export their client certificates to other apps and devices. See Using 3rd Party Android Mail Clients.

24 April 2018 © 2018 Check Point Software Technologies Ltd. All rights reserved.