Time for a bit of b/s detection around BBM. First, the party line.
BBM lets you chat and share with a speed, control and privacy you can’t get on other instant messenger apps.
How is this privacy enabled? There are two layers of encryption:
- The smartphone communicates with the BlackBerry infrastructure via TLS.
- Messages are scrambled with a Triple DES 168-bit key.
TLS ensures transport security. However, when the message comes out at the server end, it becomes readable. Notice the word scramble instead of encrypt. All BBM messages are scrambled with the same key. Yes, you read this correctly. The same key. As a BES administrator you can create a different key, by which you create an island, where all your users can communicate with each other, but not with anyone else outside your organization*.
This is where BBM Protected comes into play. It offers a third level of encryption:
Messages between BBM Protected users are encrypted using a PGP like model. The sender and recipient have unique public / private encryption and signing keys. These keys are generated on the device, by the FIPS 140-2 certified cryptographic library, and are controlled by the enterprise. BBM and BlackBerry are not involved in brokering the key exchanges so at no time are they stored within the BlackBerry infrastructure. Plus, each message uses a new random symmetric key for message encryption. Even if one message in a conversation were somehow compromised, the remaining messages would remain protected.
Translated into plain engineering terms: BBM Protected uses a public key infrastructure. For each message a new symmetric cipher key is created and encrypted with the public key of the receiver. The message itself is encrypted with the symmetric cipher key. Then both the keys and the cipher text are transmitted over the existing two security layers of the BBM infrastructure. Assuming your BES is secure, this will protect the privacy of your messages.
Why is the symmetric key necessary? Two reasons: first, BBM can send large volumes of data, where the asymmetric encryption is too slow. And second, you can encrypt the message for multiple recipients once and then just encrypt the cipher key for all recipients individually. This will also provide an audit trail, if you encrypt the cipher key for your audit archive.
Management summary: BBM Protected may be secure. BBM probably is not.
ad *) There is a requirement in regulated industries such as finance to provide an audit trail for all communications. Easy for email on your own servers, not so easy for messaging provided by a vendor. Therefore there is an option to provide that audit trail for BBM. The BES administrator can log all BBM messages to log file or send to an email address.
the link you provided regarding BBM logging is only available on BES 5 (and therefore legacy devices). With BB10 OS the BBM always run in the personal perimeter which means it cannot be audited at the moment. However, this is going to change with BBM Protected which then is able to run in the work perimeter, too.
I never understood how many enterprises are tolerating IM´s without ANY security measurements or even SMS. BBM might not be "secure" but the basic security it delivers out of the box (for about a decade now!) is much better than what is integrated in 95% of the other IM´s. The key that is used to scramble the BBM´s is not public knowledge and even if it would be it´s still provides the TLS-layer from the device to the BlackBerry NOC which makes it unlikely that that someone reads a BBM message just by using any packet capture software in an internet cafe (hello WhatsApp! ;)
Anyway, for secure corporate IM it is recommended to use the Enterprise Messenger through BES5/BES10 which allows to connect to a Sametime or Lync environment, this also integrates Desktop users. In this case the enterprise has control over the encryption keys.
Public knowledge or not, the same key for all users is not secure. And messengers with public key encryption are indeed available today, but not widely used.
Johannes Matzke on Pebble has left the building at 05:55
Stephan H. Wissel on IBM Verse on Premises to ship at the end of the year at 02:48
Volker Weber on Pebble has left the building at 00:30
Ragnar Schierholz on Pebble has left the building at 21:33
Christian Rosner on Pebble has left the building at 21:24
Daniel Meyer on Save the date :: 30-DEC-2016 at 19:10
Ingo Seifert on Save the date :: 30-DEC-2016 at 16:54
Volker Weber on Don't break the chain :: one and a half years at 09:38
Sebastian Klossek on Don't break the chain :: one and a half years at 09:29
Chris Reckling on Mural at 03:54
Andy Mell on Sonos 7 out with two huge improvements at 00:08
Stephan H. Wissel on From my inbox at 22:48
Richard Kaufmann on From my inbox at 20:54
Frank Quednau on Sonos 7 out with two huge improvements at 20:26
John Head on From my inbox at 20:03
John Head on Sonos 7 out with two huge improvements at 20:01
Robert Glaser on Sonos 7 out with two huge improvements at 19:25
Henning Heinz on From my inbox at 18:11
Stephan Perthes on Sonos 7 out with two huge improvements at 17:36
Markus Dierker on Sonos 7 out with two huge improvements at 17:29
Leo Wiggins III on Sonos 7 out with two huge improvements at 17:28
Christopher Linfoot on Sonos 7 out with two huge improvements at 17:01
Volker Weber on Capt vowe is in the Holodeck #msts2016 at 16:53
Ian Bradbury on Capt vowe is in the Holodeck #msts2016 at 16:50
Mike Hartmann on Don't break the chain :: one and a half years at 16:26