Why verify a wristband that only transmits
In a typical concept a BLE wristband only transmits, is charged once a year, has an alarm for photo or strap cut, and has an SOS button, so it seems a simple device. Even so, at a critical site it needs the same attention as a server: every employee wears one, and its signal reaches antennas in the OT network.
Three supply chain risks
The device trust procedure for a BLE wristband has 12 steps and answers three risks: unintended functionality in the circuit, unauthorised firmware, and batches that do not match the sample. Each step checks one of them, and the result goes into the protocol.
Questions from the critical infrastructure operator
The operator asks about the origin of the electronics, who holds the firmware keys, whether the wristband lasts without daily charging and where the servers run. The purchasing team should have an answer to each in the documentation before security asks.
Step by step: from the inquiry to admission to the site
The order below groups the 12 steps of the procedure into four stages. Each stage states who leads it and what stays in the documentation.
Stage 1: documents and origin
The purchasing team collects from the supplier a description of the origin of the electronics, a list of components and the manufacturer's declaration. The documents state what should be in the wristband, and the later stages check whether it actually is.
Stage 2: X-ray inspection of samples
Wristband samples are X-rayed, which shows the contents of the board and housing. The aim is to detect circuits or components outside the list, that is, unintended functionality. Photos and conclusions go into the protocol.
Stage 3: firmware and keys
Firmware control checks that the software in the wristband is the one the supplier declared, and key control checks who generates the keys and where they are stored. At energy facilities the client may require frames signed with its own keys, so this stage settles who has real control over the device.
Stage 4: batches and acceptance
Each delivered batch is compared with the sample approved in stages 2 and 3. A batch that does not match the sample does not enter the site, and the rejection is recorded in the acceptance protocol together with the batch number.
Split of the 12 procedure steps into stages (sample calculation)
Where it fits in the network architecture
Wristband verification does not end at the device. The system's architecture in the OT network is presented in the PERA model, with levels 0-6 and DMZ 3.5: the OT network separated by firewalls, no hosts with interfaces in two levels, separate VLANs for management, backup and monitoring, logs to a SIEM, and VPN access with 2FA and a jump host in the OT DMZ.
In the location concept for a large energy site, wristband data left only through the main antennas to the OT VLAN and servers in the OT network. A team that verified the wristband but did not check this data flow leaves a gap on the network side.
Audit evidence: what to record
The auditor will ask how one knows that the wristband on an employee's arm is the one that was approved. The documentation should allow an answer without talking to the author of the procedure. The list below gives the minimum that covers the three supply chain risks.
- description of the origin of the electronics and a component list from the supplier
- X-ray inspection protocol for samples, with photos and conclusions
- firmware control result and an indication of who holds the keys
- comparison of each batch with the approved sample
- record of who signed the admission to the site and when
The most common mistakes of purchasing teams
The most common mistake is treating the wristband as a gadget and ordering it without a procedure, because it costs less than a single camera. The second is a one-off check of a sample with no check of later batches. The third is having no answer to the question about keys before acceptance.
Checklist
Video
Frequently asked questions
How many steps does the device trust procedure for a BLE wristband have?
Twelve. It answers three supply chain risks: unintended functionality, unauthorised firmware and batches that do not match the sample.
Is checking one wristband sample enough?
No. Each delivered batch is compared with the approved sample, because the risk is precisely a batch that does not match the sample.
Who should hold the keys for the wristband firmware?
The critical infrastructure operator asks this, and the client may require frames signed with its own keys. The answer is settled before the order.
Does the wristband need daily charging?
In the described concept the wristband only transmits and is charged once a year. Battery life without daily charging comes up in operator questions and needs confirming for the specific model.
Let's prepare the procedure for your purchasing
We will provide the documentation of the device trust procedure and go through it with your purchasing and security team. Tell us when to arrange the talk.
Let's talk