BlackBerry 10.3 - Work and Personal - Corporate
Published 19 June 2015
This guidance is applicable to devices running BlackBerry OS 10.3.x in Work and Personal - Corporate (formerly known as EMM-Corporate) mode and is an update of the previous guidance for BlackBerry OS 10.2. The guidance was developed following testing performed on a Classic device running BlackBerry OS 10.3.1 and managed with BlackBerry Enterprise Service (BES) 12.
Licensing requirements changed between BES 10.2 and BES 12. Using Work and Personal - Corporate mode requires either a Silver SIM license (purchased from your wireless service provider) or a Silver BES license (purchased from BlackBerry or a BlackBerry partner). Gold licenses can also be used.
1. Usage scenario
BlackBerry devices will be used remotely over 3G, 4G and non-captive Wi-Fi networks to enable a variety of remote working approaches such as:
- accessing OFFICIAL email
- reviewing and commenting on OFFICIAL documents
- accessing the OFFICIAL intranet resources, the Internet and other web resources
To support these scenarios, the following architectural choices are recommended:
- All data from the work space should be routed over a secure enterprise VPN to ensure the confidentiality and integrity of the traffic, and to allow the devices and data on them to be protected by enterprise protective monitoring solutions.
- An enterprise application catalogue should be used to distribute in-house applications and trusted third-party applications to run in the work space.
- Procedural controls are put in place to effectively risk manage the end user’s use of the personal space. This may include restrictions on which applications users are permitted to install from BlackBerry World into the personal space.
2. Summary of platform security
This platform has been assessed against each of the 12 security recommendations, and that assessment is shown in the table below. Explanatory text indicates that there is something related to that recommendation that the risk owners should be aware of. Rows marked [!] represent a more significant risk. See How the platform can best satisfy the security recommendations for more details about how each of the security recommendations is met.
Recommendation | Rationale |
---|---|
1. Assured data-in-transit protection |
There are two types of VPN: - BlackBerry VPN - IPsec VPN Neither of the VPNs have been independently assured to Foundation Grade. Traffic from the personal space is not protected by the enterprise VPN. There is currently no assurance scheme to assess the strength and robustness of the proprietary BlackBerry VPN. |
2. Assured data-at-rest protection | The device's data encryption has not been independently assured to Foundation Grade. The device's Advanced Data At Rest Protection (ADARP) is not available in 'Work and personal - Corporate' mode, so encryption keys protecting sensitive data in the corporate space remain in device memory when the device is locked. |
3. Authentication | |
4. Secure boot | |
5. Platform integrity and application sandboxing | |
6. Application whitelisting | BlackBerry World app installation cannot be configured or monitored within the personal space and Android apps from any source can be installed.* |
7. Malicious code detection and prevention | |
8. Security policy enforcement | Security policies primarily only apply to the corporate space and the boundary between the two spaces. Security policies do not allow enterprise control of personal applications, interface usage, mail or browsing within the personal space.* |
9. External interface protection | Radio interfaces such as Wi-Fi and Bluetooth cannot be controlled by policy, as these are required for the personal space.* |
10. Device update policy | The enterprise cannot force the user to update their device operating system or personal space application software. * |
11. Event collection for enterprise analysis | [!] Although system logs can be retrieved remotely from a device, these logs are encrypted and only intended for decryption by the vendor. In 'Work and personal - Corporate' mode, system logs can only be retrieved remotely if the user has enabled Remote Log Collection. Collecting forensic log information from a device is very difficult. . |
12. Incident response |
*If either Workspace Only or Work and personal - Regulated mode is used, the risks marked with an asterisk associated with requirements 2, 6, 8, 9 and 10 can be effectively mitigated.
2.1 Significant risks
The following key risks should be read and understood before the platform is deployed.
- The VPNs have not been independently assured to Foundation Grade, and do not support some of the mandatory requirements expected from assured VPNs. There is currently no assurance scheme for the proprietary BlackBerry VPN, though it is based on technology which was previously assessed under the CESG Assisted Product Service (CAPS). Without assurance in the VPN there is a risk that data transiting from the device could be compromised
- The device’s native data encryption has not been independently assured to Foundation Grade, and does not support some of the mandatory requirements expected from assured full disk encryption products. Without assurance there is a risk that data stored on the device could be compromised.
- BlackBerry 10.3 does not use any dedicated hardware to protect its password hashes. If an attacker can get physical access to the device, they can extract password hashes and perform an offline brute-force attack to recover the device password.
- The personal space of the device cannot be fully managed by the enterprise, meaning that the attack surface cannot be minimised by disabling external interfaces such as Bluetooth and NFC.
- Traffic from the personal space will also bypass the enterprise VPN, negating any protections granted by corporate monitoring and filtering solutions. To avoid this for non-Wi-Fi communications, a private Access Point Name (APN) could be procured from a chosen cellular carrier and assigned to accounts that are using BlackBerry Balance.
- Arbitrary native applications can be installed from BlackBerry World and the Amazon App Store. Whilst the BlackBerry Guardian service is in place which attempt to identify and remove malicious code from these stores, it could be defeated by a skilled attacker. The operating system is required to protect enterprise data from personal applications. A vulnerability giving elevation of privilege to root, or a flaw in the code handling this separation could compromise this protection.
- Arbitrary Android applications can be installed from any source and the BlackBerry Guardian mechanisms to identify potentially hostile applications can be disabled by the user. Although Android applications run in a sandboxed environment, it is possible that implementation flaws in the Android runtime might give an Android application the same access to the device as a native BlackBerry application within the personal space.
3. How the platform can best satisfy the security recommendations
This section details what is required to meet the security recommendations for this platform.
3.1 Assured data-in-transit protection
Use either the native BlackBerry VPN client or the IPsec VPN client as neither has been independently assured. If a Foundation Grade assured VPN client for this platform becomes available, then this assured client should be used instead.
3.2 Assured data-at-rest protection
The device’s Advanced Data At Rest Protection (ADARP) is not available in Work and personal - Corporate mode, so use the device’s native data encryption. The work space is protected when powered off, but is not protected when the device is locked.
The key is not available until the user’s password has been entered for the first time after boot.
3.3 Authentication
Use a password to authenticate the user to the device and a different, strong 9-character password to authenticate the user to the work space. On first use after boot, the work space password unlocks a key which encrypts certificates and other credentials, giving access to enterprise services.
3.4 Secure boot
This requirement is met by the platform without additional configuration.
3.5 Platform integrity and application sandboxing
This requirement is met by the platform without additional configuration.
3.6 Application whitelisting
An enterprise application catalogue can be established to permit users access to an approved list of applications in the work space. The enterprise cannot whitelist applications users can install in the personal space. This could be procedurally managed via user security procedures.
3.7 Malicious code detection and prevention
Use an enterprise application catalogue which should only contain approved in-house applications which have been checked for malicious code. For the personal space, the device supports two application stores; namely BlackBerry World and the Amazon App Store. Applications from both are checked for malware by the BlackBerry Guardian system. Disable side-loading of applications by disabling Developer Mode via policy and use procedural controls to ensure BlackBerry Guardian is enabled on users’ devices.
3.8 Security policy enforcement
Settings applied through BES cannot be changed by the user. On devices with BlackBerry Balance enabled, these settings only apply to the work space.
3.9 External interface protection
In Work and personal - Corporate mode, no technical controls exist to prevent users from enabling Wi-Fi, NFC and Bluetooth, or using USB. If BlackBerry Blend is enabled, it should be configured through BES IT policy to not allow access to work data, work files or the work browser.
3.10 Device update policy
On devices with BlackBerry Balance, the enterprise cannot control when applications in the personal space are updated. The enterprise can update applications in the corporate space remotely using the BES, and can check which device software versions are in use.
3.11 Event collection for enterprise analysis
BlackBerry 10 does not support remote or local historic event collection for enterprise analysis of security incidents in Work and personal - Corporate mode. More information on logging is given at http://www.blackberry.com/btsc/KB26038.
3.12 Incident response
BlackBerry 10 devices can be locked, wiped, and configured remotely by their BES.
4. Network architecture
BES 12 is managed through a web-based interface and no longer requires a dedicated management workstation.
As the personal space cannot be controlled by policy, network routing will bypass the corporate VPN. This means that the personal side of the device will not be subject to any corporate enterprise monitoring or auditing measures.
5. Deployment process
To prepare the enterprise infrastructure:
- Procure and set up a BES Server which is compatible with BlackBerry 10.3 devices.
- Obtain SIM cards with Silver or Gold SIM Licenses from the carrier or a Silver or Gold BlackBerry Server license.
- Deploy and configure the requisite network components as described previously.
- If required, procure and configure a private Access Point Name (APN) for the devices.
- Create configuration profiles for the end user devices in line with the guidance given in this document.
- Any Certificate Authority certificates that are not registered externally will need to be added to a CA certificate profile on the BES. Client certificates can be provisioned either by using a SCEP profile, or by adding certificates to an individual user account or user group.
6. Provisioning steps
To provision each device to the enterprise infrastructure:
- Assign the IT policies to the user or user group using the BES management interface.
- If required, provision the device with a SIM card connected exclusively to the private APN.
- Use the BES to send an activation email with password to the user’s desktop email account, or supply the activation information directly.
- Supply the device to the user. When the user follows the activation steps, the work space will be created on the device and both the new workspace and existing personal space will be encrypted.
Alternatively, the Wired Activation Tool for BES 12.1 can be used to activate devices locally over USB.
7. Policy recommendations
The following IT Policy settings should be applied to BlackBerry 10 devices by creating configurations on the BES. Other settings are either not applicable to this mode, or should be chosen according to organisational policy and requirements.
Password Section | |
---|---|
Minimum password length | 9 |
Minimum password complexity | At least 1 letter, 1 number, and 1 special character |
Security timeout | 10 (minutes) |
Maximum password attempts | 5 |
Maximum password history | 8 |
Maximum password age | 90 |
Require full device password | Selected |
Define work space and device password behaviour | User Choice |
Device functionality section | |
Allow BlackBerry Assistant when locked | Not selected |
Allow voice dictation in work apps | Not selected |
Allow transfer of work data using NFC | Not selected |
Allow transfer of work contacts Using Bluetooth PBAP or HFP | Not selected |
Allow transfer of work messages using Bluetooth MAP | Not selected |
Allow transfer of work files using Bluetooth OPP or a Wi-Fi Direct connection | Not selected |
Allow Mobile Hotspot mode and tethering | Not selected |
Apps section | |
Allow Find More Contact Details | Not selected |
Allow unified view for work and personal accounts and messages | Not selected |
Allow opening links in work email messages in the personal browser | Not selected |
Allow forwarding or adding recipients to private messages | Not selected |
Display warning message for external email addresses | Selected |
External email domain allowed List | Appropriate list of domains |
Allow BBM Video over work networks | Not selected |
Allow sharing work data during BBM Video screen sharing | Not selected |
Security and privacy section | |
Force personal space data encryption | Selected |
Force media card encryption | Selected |
Allow lock screen preview of work content | Not selected |
Allow app security timer reset | Not selected |
Allow personal apps to use work networks | Not selected |
Allow personal apps access to work contacts | None |
Allow work apps to access shared files or content in the personal space | Not selected |
Restrict development mode | Selected |
Allow BlackBerry Bridge to access the work space | Not selected |
Submit logs to BlackBerry | Not selected |
Allow CCL data collection | Not selected |
8. Enterprise considerations
8.1 Organisation notice
Organisations can create their own notice to be displayed during device activation, which can be used to display security policy information to the user. Work and personal - Corporate mode does not offer the facility to display a notice on device restart.
8.2 Automatic wipe
Organisations might wish to use the ‘Wipe the work space without network connectivity’ IT policy to delete work data from devices that fail to contact the work network for a defined period of time.
8.3 Proprietary VPN
The BlackBerry VPN is a proprietary set of technologies which operate differently to the remote access functions of other platforms. As such, organisations wishing to deploy BlackBerry 10 in conjunction with other remote access solutions may need to consider how to integrate the two disparate solutions into the same network architecture.
8.4 BlackBerry Balance
Whilst applications in the work space can be whitelisted by the organisation, applications in the personal space cannot. Consequently, users should pay due care and attention to what applications they download and install to the personal workspace, as applications may be able access personal data stored there.
Users must not store sensitive work data in the personal space on the device, as this space is not protected to the same level as the work space. Should a user’s device be lost, the administrator can choose to remotely wipe the entire device or just the work space. Whilst wiping the whole device may be preferential from a security perspective, there may be other policy or legal considerations to take into account before erasing the entire device.