Your documents are safe
Some customers have an issue with forwarding potentially very confidential documents to a third party server--an issue which relates more to privacy than security. Privacy is a separate issue from the security and encryption of the transmitted document. The privacy issue may be overriding reason for purchasing a DocHawk Server license versus outsourcing the service.
DocHawk Server is based on a communication model where the client makes a request and the server responds to the client. Traffic never goes in the opposite direction. Two protocols are used for connectivity between the client and server.
Standard Outgoing Email Delivery
Email forwarding is performed discretely and automatically, and makes full utilization of the existing and secure email delivery channel. Whether or not BES is used, email traffic from the BlackBerry® is encrypted before delivery.
HTTP Access
After a submission is made from the client to the server via the secure email channel, the client automatically connects via HTTP to the DocHawk Server to inform the server of the pending delivery.
DocHawk Server does not use any kind of push-to-device feature of MDS, which means that the firewall settings of the device will play no role in reducing security.
For the actual DocHawk Server server-side components, all requests from client applications running on BlackBerry® devices are carefully scrutinized for validity on three points: (1) the device PIN (a unique eight character identifier), (2) the device IMEI or ESN (a unique, extended value which is used by the device's service provider), and (3) the email address which is defined by the service book entries of the device.
All of these details must match with an enabled account that has been defined within DocHawk Server. The identification-matching details are encrypted twice before being transmitted from the device to travel along the already heavily secured communications channel, whether private or public MDS, regardless of whether BES is used or not.
Resources