Permitting Third-Party Applications To Encode Blackberry Device Data; Blackberry Wireless Messaging Security; Receiving An Email Message On The Blackberry Device - Blackberry ENTERPRISE SOLUTION SECURITY - ENTERPRISE SOLUTION - SECURITY TECHNICAL Overview

BlackBerry Enterprise Solution

Permitting third-party applications to encode BlackBerry device data

The BlackBerry Enterprise Server and the BlackBerry Device Software support a Transcoder API. This API permits
third-party application developers to create encoding schemes that encrypt, convert, or otherwise change the
format of data, and apply an encoding scheme to BlackBerry device data using transcoder application code. The
third-party encoding scheme prepends a transcoder ID to the data that it encodes. The BlackBerry Enterprise
Solution then encrypts the transcoder-encoded data using standard BlackBerry encryption.
The BlackBerry Enterprise Solution permits only third-party encoding schemes that the RIM signing authority
system has digitally signed using the RIM Cryptographic API public key to access the Transcoder API to create
the transcoder application code. To apply the third-party encoding scheme, the BlackBerry device must be
running corresponding transcoder application code.
Third-party application developers can use the Transcoder API to add cryptographic components that the RIM
Cryptographic API does not support by default to their third-party encoding schemes. The BlackBerry Enterprise
Solution applies the third-party encoding schemes to any outgoing data to which standard BlackBerry
encryption applies. The Transcoder API supports use of all the cryptography that the RIM Cryptographic API
supports.
If the BlackBerry Enterprise Server administrator allows third-party applications to use the Transcoder API on the
BlackBerry device, those applications, if not functioning correctly, might impact the security, usability and
performance of the BlackBerry Enterprise Solution, and might cause loss of BlackBerry device data. To use the
third-party encoding scheme, the BlackBerry Enterprise Server administrator must use the Security Transcoder
Cod File Hashes IT policy rule to specify the .cod file for the third-party encoding scheme that the BlackBerry
device permits to register as a transcoder. For more information about using the Security Transcoder Cod File
Hashes IT policy rule, see the Policy Reference Guide.

BlackBerry wireless messaging security

The BlackBerry Enterprise Solution is designed with advanced security features to work seamlessly with existing
networks while enabling BlackBerry device users to securely send and receive messages while away from their
computers. Email messages remain encrypted at all points between the BlackBerry devices and the BlackBerry
Enterprise Server.

Receiving an email message on the BlackBerry device

1. Alice sends a message to Bob from her computer. Alice and Bob work at the same organization.
2. The messaging server receives the email message and notifies the BlackBerry Enterprise Server that the
message has arrived.
3. The messaging server delivers the message to Bob's computer.
4. The BlackBerry Enterprise Server retrieves the message from the messaging server.
5. The BlackBerry Enterprise Server queries the messaging server for BlackBerry device user preferences to
determine whether or not to forward the message to Bob's BlackBerry device.
6. The BlackBerry Enterprise Server compresses and encrypts the message.
7. The BlackBerry Enterprise Server places the message in the outgoing queue.
www.blackberry.com
Sending a message from a computer to the BlackBerry device
18