Bluetooth on Windows: The Radio Your Audit Forgot
WinSentinel Bluetooth Security Audit checks the radio most machines carry and nobody audits: discoverability, stale pairings, exposed profiles, and driver age.
Bluetooth is the radio most Windows machines carry and almost nobody audits. It is on by default on every laptop, it pairs with speakers and headsets and phones without a second thought, and it runs a full protocol stack — classic Bluetooth and Bluetooth Low Energy — with its own drivers, services, and attack history. BlueBorne in 2017 showed that a Bluetooth stack bug could give an attacker code execution on a machine that had never paired with anything. The radio is a network interface. Treat it like one.
WinSentinel's Bluetooth Security Audit checks this surface on the machine in front of you: whether the radio is on, whether the machine is discoverable, which devices are paired and trusted, which Bluetooth profiles are exposed, and whether the drivers behind the stack are current. It is a single-machine check, run locally, and it belongs in the same routine as your firewall and Defender checks.
What the audit actually looks at
A Bluetooth audit has four questions, and each one maps to a real exposure:
- Is the radio on, and does it need to be? A laptop that never connects a Bluetooth peripheral has no reason to broadcast. The radio should be off when it is not in use — not because Bluetooth is uniquely dangerous, but because an interface doing nothing is still an interface.
- Is the machine discoverable? On Windows, a PC is generally discoverable only while the Bluetooth settings page is open — but that page gets opened constantly, in meeting rooms, on planes, at conferences, usually on networks you do not control. Discoverability is the difference between an attacker scanning for targets and an attacker finding you.
- What is paired, and what does pairing trust? Every paired device is a trust relationship. A conference-room speaker paired three jobs ago, a rental-car hands-free kit, a hotel TV — each one can reconnect and, depending on the profile, reach services on your machine. Stale pairings are the Bluetooth equivalent of stale credentials.
- Which profiles are exposed? Bluetooth is not one service. Object Push (OBEX) can move files, HID turns a paired device into a keyboard, A2DP and HSP carry audio, PAN carries network traffic. A machine exposing HID to any paired device is a machine that trusts a remote keyboard.
Seeing the state yourself
Before you fix anything, look at what is actually there. PowerShell will show you the Bluetooth devices Windows knows about:
Get-PnpDevice -Class Bluetooth | Select-Object FriendlyName, Status, InstanceId
And the Bluetooth Support Service, which has to be running for any of this to work:
Get-Service bthserv | Select-Object Name, Status, StartType
Paired devices live in Settings under Bluetooth and devices. Walk the list and ask of each entry: do I still own this device, do I still use it, and would I notice if it connected right now? Anything you cannot answer gets unpaired. The check takes two minutes and it is the single highest-value Bluetooth action on a personal machine.
The fixes, in order of value
Turn the radio off when it is not in use. On a laptop that lives on a desk with wired peripherals, Bluetooth can stay off permanently. On a laptop that uses Bluetooth headphones, turn it off at the end of the day. Windows exposes the toggle in Quick Settings and in Settings; the habit matters more than the mechanism.
Unpair what you do not use. Pairing is trust, and trust should expire. Remove rental cars, conference hardware, demo units, and anything belonging to a previous employer. If you need it again, pairing takes thirty seconds — that is not a reason to carry the trust forever.
Keep the drivers current. Bluetooth vulnerabilities are overwhelmingly driver and stack bugs, and they are fixed the same way every other driver bug is fixed: through Windows Update and the manufacturer's driver package. A Bluetooth driver from 2021 on a machine that gets every other update is a gap worth closing. WinSentinel flags the driver age as part of the audit so it does not hide behind the rest of the update queue.
Block it where it does not belong. On managed machines, Bluetooth can be restricted by device setup class — the Bluetooth class GUID can be blocked through Device Installation Restrictions in Group Policy, so the radio never comes up on machines that have no business using it. Kiosk machines, lab machines, and servers in particular should not have a discoverable radio.
Why this audit earns its place
Bluetooth gets skipped because it feels like a consumer feature — headphones and speakers, not infrastructure. But the stack runs with system privileges, the radio is always within range of strangers, and the pairing list on a typical three-year-old laptop reads like a travel diary. None of that makes Bluetooth an emergency. It makes it exactly the kind of quiet, accumulating surface that an audit exists to surface: low drama, real exposure, and fixable in minutes once you can see it.
Run the Bluetooth Security Audit the same way you run the rest of the local audit — on the machine, as part of the routine — and treat a clean result the way you would treat a clean firewall check: not as proof nothing can happen, but as proof the surface you control is actually controlled.