Security Technical Overview
Local Navigation
- Overview
- New in this release
-
Keys on a device
- Enforcing the FIPS mode of operation on a device
-
Device transport keys
- States for device transport keys
- Where the BlackBerry Enterprise Solution stores device transport keys
- Generating device transport keys
- Process flow: Generating a device transport key using BlackBerry Desktop Software version 4.0 or later
- Message keys
- Content protection keys
- Principal encryption keys
- PIN encryption keys
-
Encrypting data that the BlackBerry Enterprise Server and a device send to each other
-
Algorithms that the BlackBerry Enterprise Solution uses to encrypt data
-
How the BlackBerry Enterprise Solution uses AES to encrypt data
-
How a device uses the AES algorithm to help protect user data and keys
- Process flow: Running a masking operation during the first AES calculation when content protection is turned on
- Process flow: Running a masking operation during subsequent AES calculations when content protection is turned on
- Process flow: Running a masking operation when a device does not use content protection
- How the AES algorithm creates S-Box tables and uses round keys and masks
-
How a device uses the AES algorithm to help protect user data and keys
- How the BlackBerry Enterprise Solution uses Triple DES to encrypt data
-
How the BlackBerry Enterprise Solution uses AES to encrypt data
- Process flow: Sending an email message to a device using BlackBerry transport layer encryption
- Process flow: Sending an email message from a device using BlackBerry transport layer encryption
-
Algorithms that the BlackBerry Enterprise Solution uses to encrypt data
-
Managing BlackBerry Enterprise Solution security
- Using an IT policy to manage BlackBerry Enterprise Solution security
- Best practice: Controlling which applications can use the GPS feature on a device
- Using IT administration commands to protect a lost or stolen device
- Managing device access to the BlackBerry Enterprise Server
- Using a segmented network to prevent the spread of malware
- Moving a device to a BlackBerry Enterprise Server that uses a different BlackBerry Configuration Database
- Configuring the IT Policy Viewer icon on a device
- Device storage space
- Securing devices in your organization’s environment for personal use and work use
- How a device classifies what data and applications are for work use or personal use
- Preventing a user from compromising work data on a device
- Preventing a user from pasting work data into a personal application
- Preventing a user from forwarding work data using personal channels
- Prevent a user from using the work contact list in personal email accounts and personal calendars
- Controlling the browsing traffic in the BlackBerry Browser
- Preventing a user from backing up work data that is stored on a device
- Protecting work data on a media card
- Deleting only work data from a device
- Managing third-party applications on a device that a user uses for personal purposes
- Managing add-on applications on a device that a user uses for personal purposes
- IT policy rules that apply to devices that users use for personal purposes
-
Protecting data on a device
- Encrypting user data on a locked device
- Encrypting the device transport key on a locked device
- Resetting a device password when content protection is turned on
- Protecting passwords that a device stores
- Protecting data that a device stores on a media card
- How the BlackBerry Attachment Service protects data on a device
- How a device protects its operating system and the BlackBerry Device Software
- How a device authenticates the boot ROM code and binds the device processor when the device turns on
- Protecting the data that the BlackBerry Enterprise Server stores in your organization's environment
-
Protecting communication with a device
-
Opening a direct connection between a device and a BlackBerry Router
- Advantages of using the BlackBerry Router protocol
- Process flow: Authenticating a device with the BlackBerry Enterprise Server using the BlackBerry Router protocol
- Closing a direct connection between a device and BlackBerry Router
- Impersonation attacks that the BlackBerry Router protocol is designed to prevent
- How the BlackBerry Router protocol uses the Schnorr identification scheme to open an authenticated connection
- Process flow: Using the BlackBerry Router protocol to open an authenticated connection
- Process flow: Using the BlackBerry Router protocol to close an authenticated connection
- Cryptosystem parameters that the BlackBerry Router protocol uses
- Best practice: Protecting plain text messages that a device sends over the wireless network
- How the BlackBerry Enterprise Server protects connections between a device and the Internet or intranet
- Protecting HTTP connections from a device to content servers and application servers using HTTPS
- Warning messages for invalid certificates
- Permitting TLS connections to websites that use invalid certificates
- How a device protects a connection to a WAP gateway
- What happens to data that is not delivered to a device
-
Opening a direct connection between a device and a BlackBerry Router
-
Protecting communications in your organization's environment
-
How a BlackBerry Enterprise Server and the BlackBerry Infrastructure authenticate with each other
- What happens when a BlackBerry Enterprise Server and the BlackBerry Infrastructure open an initial connection
- How the BlackBerry Enterprise Solution protects a TCP/IP connection between a BlackBerry Enterprise Server and the BlackBerry Infrastructure
- Process flow: Authenticating a BlackBerry Enterprise Server with the BlackBerry Infrastructure
- How a BlackBerry Enterprise Server and messaging server protect a connection to each other
- How the BlackBerry Enterprise Server components and the BlackBerry MVS protect communication
- How the BlackBerry Desktop Manager protects communication using the BlackBerry inter-process protocol
- How the BlackBerry Collaboration Service connects to an instant messaging server and collaboration clients on devices
-
Protecting your organization’s resources when using BlackBerry MDS Connection Service integrated authentication
- Architecture: BlackBerry MDS Connection Service integrated authentication
- How the BlackBerry MDS Connection Service uses Kerberos to help protect your organization's resources
- Identifying the resources that users can access using BlackBerry MDS Connection Service integrated authentication
- Process flow: Retrieving a resource when using BlackBerry MDS Connection Service integrated authentication
-
Protecting your organization’s resources when you configure BlackBerry Administration Service single sign-on
- Architecture: BlackBerry Administration Service single sign-on
- How BlackBerry Administration Service single sign-on uses Kerberos to help protect your organization’s resources
- How the BlackBerry Administration Service completes Kerberos authentication
- Process flow: Accessing the BlackBerry Administration Service console and BlackBerry Web Desktop Manager when you configure BlackBerry Administration Service single sign-on
-
How a BlackBerry Enterprise Server and the BlackBerry Infrastructure authenticate with each other
- Activating a device
- Managing certificates on a device
- Purpose of certificates on a device
- Importing certificates onto a device
- Configuring BlackBerry devices to enroll certificates over the wireless network
- Managing an enrolled certificate
- Determining the status of certificates using a CRL or OCSP
- Process flow: Enrolling a certificate when the certification authority approves certificate requests automatically
- Process flow: Enrolling a certificate when a certification authority administrator approves certificate requests
- Process flow: Enrolling a certificate using an RSA certification authority
-
Protecting BlackBerry Device Software updates
-
Protecting BlackBerry Device Software updates over the wireless network
- How the BlackBerry Enterprise Solution protects BlackBerry Device Software updates over the wireless network using encryption
- How the BlackBerry Enterprise Solution protects BlackBerry Device Software updates over the wireless network using IT policies and content protection
- Battery power requirements for BlackBerry Device Software updates over the wireless network
- Process flow: Preparing to send a BlackBerry Device Software update over the wireless network
- How a device validates a BlackBerry Device Software update over the wireless network
-
Updating the BlackBerry Device Software from an update web site
- Protecting cryptographic services data when updating the BlackBerry Device Software from an update web site
- Process flow: Generating a BlackBerry services key that protects cryptographic services data
- Process flow: Backing up cryptographic services data using the BlackBerry Desktop Manager
- Process flow: Restoring cryptographic services data using the BlackBerry Desktop Manager or BlackBerry Application Web Loader
-
Protecting BlackBerry Device Software updates over the wireless network
-
Extending messaging security to a device
- Extending messaging security using PGP encryption
- Extending messaging security using S/MIME encryption
- Extending messaging security using IBM Lotus Notes encryption
-
Extending messaging security for attachments
- Process flow: Viewing an attachment in a PGP encrypted message or S/MIME-encrypted message
- Process flow: Viewing an attachment that is encrypted using S/MIME encryption, PGP/MIME encryption, or OpenPGP encryption
- Process flow: Sending an S/MIME-protected email message that contains attachments that are located on a device
- Process flow: Forwarding an S/MIME-protected email message that contains attachments that are not located on a device
- Configuring two-factor authentication and protecting Bluetooth connections
- Wi-Fi
enabled devices
- Types of Wi-Fi networks
- Security features of a Wi-Fi enabled device
- Protecting a connection between a Wi-Fi enabled device and an enterprise Wi-Fi network
-
How a Wi-Fi enabled device can connect to the BlackBerry Infrastructure
- How an SSL connection between a Wi-Fi enabled device and the BlackBerry Infrastructure protects data
- Process flow: Opening an SSL connection between the BlackBerry Infrastructure and a Wi-Fi enabled device
- Cipher suites that a Wi-Fi enabled device supports for opening SSL connections and TLS connections
- Managing how a device connects to an enterprise Wi-Fi network
- How the BlackBerry Enterprise Solution protects sensitive Wi-Fi information
- Using a VPN with a Wi-Fi enabled device
- Using a captive portal to connect to an enterprise Wi-Fi network or Wi-Fi hotspot
- Protecting a connection between a Wi-Fi enabled device and an enterprise Wi-Fi network using RSA authentication
-
Layer 2 security methods that a Wi-Fi enabled device supports
- WEP encryption
- PSK protocol
- IEEE 802.1X standard
- EAP authentication methods that a Wi-Fi enabled device supports
- Encryption keys that a Wi-Fi enabled device supports for use with layer 2 security methods
- EAP authentication methods that a device supports the use of CCKM with
- Using certificates with PEAP authentication, EAP-TLS authentication, or EAP-TTLS authentication
-
Controlling applications on a device
- Creating a third-party application for a device
- Specifying the resources that third-party applications can access on a device
- Permitting a third-party application to encode data on a device
- Removing third-party applications when a user deletes all device data
- Controlling which applications can access NFC features on a device
- Controlling which applications can access the secure element on a device
- RIM Cryptographic API
-
Cryptographic algorithms and cryptographic codes that the RIM Cryptographic API
supports
- Symmetric block algorithms that the RIM Cryptographic API supports
- Stream encryption algorithms that the RIM Cryptographic API supports
- Asymmetric encryption algorithms that the RIM Cryptographic API supports
- Key agreement scheme algorithms that the RIM Cryptographic API supports
- Signature scheme algorithms that the RIM Cryptographic API supports
- Key generation algorithms that the RIM Cryptographic API supports
- Message authentication codes that the RIM Cryptographic API supports
- Message digest codes that the RIM Cryptographic API supports
- TLS and WTLS protocols that the RIM Cryptographic API supports
- Limitations of RIM Cryptographic API support for cipher suites for the key establishment algorithm
-
Cryptographic algorithms and cryptographic codes that the RIM Cryptographic API
supports
- Related resources
- Glossary
- Provide feedback
- Legal notice
BlackBerry Manuals & Help
>
Administrator Documentation
>
BlackBerry Device Software Security
>
Security Technical Overview
BlackBerry Enterprise Server 5.0 SP3 and BlackBerry 7 - 6.0
BlackBerry Enterprise Server 5.0 SP3 and BlackBerry 7
Security Technical Overview
5.0.3
To view a complete list of topics, expand the topics in the left pane.