Bluetooth Low Energy
BLE Pairing, Bonding and Access Control
A connected device is not automatically an authorised device.
A connected device is not automatically an authorised device. Plan how operators establish trust and how access is revoked.
Separate the security functions
Pairing establishes security material; bonding retains information for future connections. Application authorisation determines what a peer may do. Choose a pairing method compatible with the hardware interface and required protection rather than assuming all methods provide identical authentication.
Protect configuration operations
Require appropriate security for writes that change calibration, identity or operating limits. Avoid leaving a permanent unrestricted commissioning mode. Define how a physical action, controlled time window or approved account permits onboarding without exposing every deployed sensor.
Handle lost and replaced clients
Document removal of old bonds, ownership transfer and factory reset behaviour. Test what an unauthorised phone can read and write. Keep recovery usable for legitimate operators without relying on one shared secret across every installation.
FAQ
Does bonding replace application permissions?
No. Remembering a trusted link and deciding which operations are allowed are separate responsibilities.
Technical References
Need Help Applying This?
Baztech can assess the hardware, connectivity, software and deployment constraints for your specific project.