Mobile Access for Smartphones and Tablets

1. In SmartConsole Check Point GUI application used to manage a Check Point environment - configure Security Policies, configure devices, monitor products and events, install updates, and so on., 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 Security Gateway, to which users connect.

      • 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. In SmartConsole, install the Policy.

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.

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 inside the E-mail Template body.

9. Click Insert Link and select the type of link to add (link or QR code).

   • Site and Certificate Creation

     For users who already have a Check Point app installed.

     When users scan the QR 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 Layer 3 tunnel app that gives users network access to all mobile applications.

   • 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 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 Layer 3 tunnel app that gives users network access to all mobile applications.

   • Custom URL

     Lets you configure your own URL.

   For each link type, you can select which elements are added to the mail template

   • Link URL - Enter the full link address.

   • QR Code - When enabled, users scan the code with their mobile devices.

   • HTML Link - When enabled, users tap the link on their mobile devices.

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

   • Display Text - Enter the text for the link title.

10. Click OK.

11. Optional: Click Preview in Browser to see a preview of how the email will look.

12. Click OK.

13. Publish the changes

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.

1. Run the command on the Security 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.

1. Make sure that the cvpnd.C file 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.

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.

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

   SmartDashboard Legacy Check Point GUI client used to create and manage the security settings in versions R77.30 and lower. In versions R80.X and higher is still used to configure specific legacy settings. 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.

5. Change settings. See the Capsule Workspace Settings in the Mobile Profile section below.

6. Click Save and then close SmartDashboard.

7. In SmartConsole, install the policy.

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 Security 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 Security Gateway.

     • Block access from jail-broken devices - Block devices that are jail-broken from connecting to the Security Gateway.

   • Track user's GPS location (upon user's approval) - Tracks devices connecting to the Security 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 Security 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 the Push Notifications section below for details.

   To use this, push notifications must be enabled for Capsule Workspace on the Security 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.

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

6. Close SmartDashboard.

7. Publish the SmartConsole session.

A Passcode Profile includes these settings:

• Passcode Requirements - The complexity requirements. When you configure this, remember that users usually have a small on-screen keyboard.

  • Simple Passcode (4 digits) - Users create a simple password of 4 numbers.

  • Custom passcode strength - Select from the requirements below.

    • Minimum passcode length - Enter the minimum number of characters.

    • Require alphanumeric characters - Show an alphanumeric keyboard and require at least one character to be a letter.

    • Minimum complex characters - Enter the number of characters that must be a special character.

• Force passcode expiration - Enter the number of days after which user's passcodes expires and must be replaced.

• Allow grace period for entering passcode - Select to let users access the Business Secure Container for a specified period of time without re- entering their passcode. Enter the quantity of time in minutes.

• Exit after a few failures in passcode verification - Select to lock users out after a specified number of failed attempts. After the failed attempts, users must re-authenticate. If the authentication method includes username and password, users must enter them. If the authentication is certificate-only, users need a new certificate.

• Enforce passcode history - When selected, users cannot use a passcode that is the same as earlier passcodes. Select the number of earlier passcodes that users cannot use.

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

• From the Mobile Access Wizard:

  • If you enable Mobile Mail in the Mobile Access Wizard, push notifications are automatically enabled for the Security Gateway.

  • If you enable Mobile Mail from the Mobile Access tab, push notifications are NOT enabled.

• From the Security Gateway Properties:

  1. Open a Security Gateway object that has Mobile Access enabled.

  2. Select Mobile Access > Capsule Workspace from the tree.

  3. Select Enable Push Notifications.

  4. Click OK.

1. From SmartDashboard > Mobile Access tab > Capsule Workspace Settings, open a Mobile Profile.

2. Under Push Notifications, click Manage.

1. Install a trusted server certificate on the Mobile Access Security Gateway. See sk98203.

2. Close all SmartConsole windows connected to the Management Server Check Point Single-Domain Security Management Server or a Multi-Domain Security Management Server..

3. Connect with Database Tool (GuiDBEdit Tool) (sk13009) to the Management Server.

4. Search for the field main_url (Ctrl +F).

5. Press F3 to see next main_url until you find main_url that contains the value ExchangeRegistration.

6. Double-click the ExchangeRegistration main_url field and edit the value to be https:// and not http://.

7. Save the changes and close Database Tool (GuiDBEdit Tool).

8. Connect with SmartConsole to the Management Server.

9. Open the Mobile Access Security Gateway object.

10. Click OK.

11. Install policy.

1. Download the certificate to the Exchange server.

2. Double-click the certificate file, and follow the Windows certificate installation wizard steps.

3. Run the 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.

7. Click Finish.

8. Select Certificates and click Add again.

9. Select Computer account.

10. Click Next.

11. Click Finish.

12. Click OK.

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

Run the $CVPNDIR/bin/PushReport command 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

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.

1. On the Security Gateway run:

   cvpnd_settings $CVPNDIR/conf/cvpnd.C set MobileAppBypassESODforApps "true"

   or

   cvpnd_settings $CVPNDIR/conf/cvpnd.C set MobileAppBypassESODforApps "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 Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing., copy the $CVPNDIR/conf/cvpnd.C file to all cluster members and restart the services on each.

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.

1. Connect to the command line ine the Security Gateway.

2. Log in to the Expert mode mode.

3. Edit the $FWDIR/conf/mdm.conf file.

4. Edit the global options.

   Description

   MDM is disabled by default. You must change the value of the enabled parameter to 1.

   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 Security 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. See the Advanced Vendor Support section below.
   password_is_obscured	0 - password parameters in mdm.conf show in clear text. 1 - password parameters in mdm.conf show strings. Recommended: keep default (1). If the global property password_is_obscured is enabled, you cn obscure all parameters named password in the Vendor Configuration blocks. To get an obscured password string from your password: Run in the Expert mode: # obfuscate_password <Your Expert mode Password> The output is a string. For example: 33542b323a3528343640 Copy the string to the mdm.conf file, as the password value. Save the file. Install policy.
   verify_ssl_cert	0 - SSL certificates not verified when Security Gateway accesses MDM cloud services. 1 - SSL certificates verified. Prevents some DNS poisoning, spoofing, man-in-the-middle attacks against Security 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 Security 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 Security Gateway and MDM cloud services. Recommended: keep default.
   ssl_use_tls_v1	To use TLSv1 or SSL for HTTPS between Security Gateway and MDM cloud services. Recommended: keep default.

5. Edit the vendor options.

   Description

   You can add more, if you have an understanding of the vendor's API and expertise with PHP programming.

   See the Advanced Vendor Support section below.

   For the most updated vendor information see sk98201.

6. Save the $FWDIR/conf/mdm.conf file.

7. Install policy.

8. Test the configuration.

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:

Example Response:

Example URL:

https://bestmdm.com/api

We use these examples in the steps below.

To add support for a new third-party vendor:

1. Edit the $CVPNDIR/phpincs/MDMVendors.php file.

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 the $CVPNDIR/phpincs/MDMVendors.php file.

8. Edit the $FWDIR/conf/mdm.conf file.

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 $FWDIR/conf/mdm.conf file.

12. Install policy.

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.

1. Connect to the command line on the Security Gateway and log in the Expert mode.

2. Back up the $CVPNDIR/conf/includes/Login.location.conf file.

3. Edit the $CVPNDIR/conf/includes/Login.location.conf file.

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://<Security 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.

• Parameters for the MDM vendor's cloud service (such as Username or Password) are not configured correctly in $FWDIR/conf/mdm.conf.

• There is a network problem accessing MDM vendor's cloud service.

• There is a problem with SSL certificates, which prevents the Security Gateway from accessing the MDM vendor's cloud service.

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.

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.

Single Sign On (SSO) lets users in a session connect to the Mobile Access Security Gateway, without authenticating when the client starts. If a user cannot access the Security 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.

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.

For Androids, idle timeout cannot be modified or enforced by the device or the Security 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.

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.

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.

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.

1. Get the Check Point Mobile app from the Android Market.

2. When prompted, enter the:

   • Site Name

   • Registration key

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.

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.