04-06-2022 04:16 AM
Hello,
Seems XDR - Device control only block USB-related devices on the Endpoint, is it blocking any new Bluetooth devices if the GUID is unknown?
any ideas?
04-06-2022 06:29 PM
Hi @SeanDeHarris you can consider leveraging on MDM controls to disable bluetooth on endpoints.
04-06-2022 09:26 PM
Thanks for your sharing.
I did some testing with the GUID, the Bluetooth devices will be blocked either by the Class GUID for Network Adaptor or Bluetooth level.
Network Adaptor (Bluetooth device PAN)
{4d36e972-e325-11ce-bfc1-08002be10318}
Bluetooth
{e0cbf06c-cd8b-4647-bb8a-263b43f0f974}
With the class GUID of Bluetooth device, it will block everything bluetoothish, eg built-in Windows bluetooth services, headset, mouse...
Seems cannot block individual bluetooth headset.
04-07-2022 01:15 AM
every single device should have a unique number for identifying it, try to investigate which one is yours.
This number appears an registry keys once you plug it in on a windows system
the same with bluetooth or any other device connected. Otherwise the OS wont be able to handle it.
This unique identifiers are used as evidences in courts of law when performing forensics and they all leave traces in registry keys
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
