Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Bluetooth Low Energy security covers the pairing, encryption, privacy, and application-layer controls that protect the short-range radio link used by wearables, sensors, locks, and medical devices.

What Is Bluetooth Low Energy Security?
Bluetooth Low Energy arrived with Bluetooth 4.0 in 2010 as a separate radio designed for devices that run on a coin cell for years. It now carries the traffic of fitness trackers, glucose monitors, door locks, asset tags, industrial sensors, and most of the smart home. BLE security is the set of mechanisms protecting that link: how two devices pair, whether the connection is encrypted, whether addresses can be tracked, and — the part that fails most often — whether the device checks who is allowed to issue a command.
BLE has two generations of pairing, and products in the field still use both.
LE Legacy pairing, from Bluetooth 4.0 and 4.1, exchanges a Temporary Key whose strength depends on the association model. With Just Works the Temporary Key is zero. Mike Ryan demonstrated in 2013 that anyone capturing the pairing exchange could recover the long-term key by brute force in under a second, and released crackle to do it. Passkey Entry uses a six-digit value, which narrows the search to a million candidates — also trivial offline.
LE Secure Connections, introduced in Bluetooth 4.2 in December 2014, replaced that with an elliptic curve Diffie-Hellman exchange over P-256. Passive eavesdropping on the key agreement no longer helps. Protection against an active intermediary, however, still depends on the association model: Numeric Comparison and Passkey Entry authenticate the exchange, while Just Works does not. A product that supports Secure Connections but pairs with Just Works has solved half the problem.
In assessment after assessment, the finding is not cryptographic. It is that the device accepts commands from anyone in range. BLE exposes functionality through GATT characteristics, and each characteristic can require encryption, authentication, or authorisation before a write is accepted. Many products set none of these and rely on the mobile app to behave properly. Replace the app with gatttool, bleak, or the bettercap BLE module, write to the characteristic directly, and the lock opens or the pump setpoint changes.
The fix is application-layer authentication: a challenge-response using a per-device key, implemented above GATT, so that possession of radio proximity is not possession of control.
A BLE device advertises constantly, and if it advertises a fixed public address it is a beacon anyone can follow. The specification provides resolvable private addresses that rotate on a timer and can only be resolved by a peer holding the Identity Resolving Key. Many low-cost products never enable them. For an employer issuing wearables or asset tags, that is a UK GDPR consideration as much as a security one, because a rotating identifier tied to a named individual is still personal data.
Capturing BLE traffic requires following the hop sequence across 37 data channels. An nRF52840 dongle running Sniffle, an Ubertooth One, or a dedicated analyser will follow a connection; btlejack can also hijack an established one. Relay and intermediary tooling such as gattacker sits between phone and device to replay or modify traffic.
For designers, the short list is: require LE Secure Connections, use an association model with real user interaction rather than Just Works, enforce encryption and authentication on every writable characteristic, add application-layer authentication with a per-device secret, enable address privacy, and keep the vendor stack updated — most of the SweynTooth fixes arrived as SDK patches that device makers had to rebuild and ship through OTA updates.
Our IoT Penetration Test Services cover BLE alongside the mobile application and cloud API, since the three are rarely separable in a real product.
No. Encryption only applies once two devices have paired and bonded, and a device can be designed to accept connections and commands without pairing at all. Plenty do, because pairing complicates the user experience. Whether a given product encrypts its link depends entirely on how the developer configured the stack, which is why it is worth testing rather than assuming.
Just Works is the association model for devices with no display or keypad, so there is no way for a user to confirm they are pairing with the right peer. The key exchange completes without authentication, which leaves it open to an active intermediary who pairs with both sides. It is acceptable only where the application layer adds its own authentication on top.
If the device advertises a static address, yes, with nothing more than a phone and an app. Shops and venues have used exactly this for footfall analytics. Resolvable private addresses that rotate every fifteen minutes or so prevent casual tracking, but only peers holding the identity resolving key can still recognise the device, so the feature has to be enabled in the product.
Further than the marketing range suggests. A standard phone reaches perhaps ten metres, but a directional antenna and an amplified adapter extend reception well beyond a hundred metres, and relay techniques remove the distance constraint altogether. Designing on the assumption that proximity proves legitimacy is unsafe for locks, vehicles, and anything else where presence grants access.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.