RE: Security in BLE/SD

OskarM — Fri, 09 Dec 2016 09:18:39 GMT

Thanks. After extensive dig-through I could maybe summarize:

All traffic for BLE is encrypted using AES-128 CCM, the nrf52832 uses the HW module for that. This is done without user interaction and most probaly blocks use access to this module with sd enabled.
In non secure BLE there was symmetrical key exchange using some custom BLE algorithm, embedded in soft device.
In LESC (4.2) even during paring ECDH is used for "cipher key" exchange - using micro ECC features
For parties authentication (to protect against MITM attack) the ECDSA is used (p-256 + SHA256 signing) using micro ECC and/or sha256 libraries
DFU uses ECDSA to sign data needed for update;

In general since transmission is encrypted after pairing and data is encrypted, the only weak point is the pairing, which is know BLE limitation (except OOB).

THe most "unknown" here is that to use the LESC features also the phone needs to support that, i.e. has to have BLE 4.2 support.

regards oskar

RE: Security in BLE/SD

Petter Myhre — Fri, 09 Dec 2016 08:43:32 GMT

The CCM module is used for encryption/decryption.

For legacy pairing no libraries are needed.

For LESC the nRF52832 requires an external library, micro-ecc, while I believe it is not needed in the nRF52840 (because of the cryptocell)

Authorization is just that the application has to authorize access to an attribute, for example a read or write.

The Secure DFU bootloader supports signing of the image to ensure that the update stems from a trusted source.