Your documents are safe
Your choice between purchasing DocHawk on a yearly/quarterly subscription basis (DocHawk Platinum and an on-premise server license (DocHawk Server) may come down to concerns of confidentiality and privacy. When choosing DocHawk Platinum your potentially very confidential documents are forwarded to a third-party server, while purchasing DocHawk Server keeps the documents in-house. While we keep very tight security on the DocHawk servers used for our subscription service, your company’s privacy policy may require an on-site installation of DocHawk Server.
DocHawk 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, which is an important security consideration. The two protocols used for connectivity between the client and server are secure e-mail and HTTP, thus ensuring full compliance with the BlackBerry®'s outstanding security model.
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.
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