deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
windows-itpro-docs/windows/client-management/mdm/policy-csp-bluetooth.md
ManikaDhiman fe4edd0b33 More updates
2020-02-11 17:02:43 -08:00

18 KiB
Raw Blame History

title, description, ms.author, ms.topic, ms.prod, ms.technology, author, ms.localizationpriority, ms.date, ms.reviewer, manager
title description ms.author ms.topic ms.prod ms.technology author ms.localizationpriority ms.date ms.reviewer manager
Policy CSP - Bluetooth Policy CSP - Bluetooth dansimp article w10 windows manikadhiman medium 02/12/2020 dansimp

Policy CSP - Bluetooth

Warning

Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.

Bluetooth policies

Bluetooth/AllowAdvertising
Bluetooth/AllowDiscoverableMode
Bluetooth/AllowPrepairing
Bluetooth/AllowPromptedProximalConnections
Bluetooth/LocalDeviceName
Bluetooth/ServicesAllowedList
Bluetooth/SetMinimumEncryptionKeySize

Bluetooth/AllowAdvertising

Windows Edition Supported?
Home cross mark
Pro check mark
Business check mark
Enterprise check mark
Education check mark

Scope:

[!div class = "checklist"]

  • Device

Specifies whether the device can send out Bluetooth advertisements.

If this is not set or it is deleted, the default value of 1 (Allow) is used.

Most restricted value is 0.

The following list shows the supported values:

  • 0 – Not allowed. When set to 0, the device will not send out advertisements. To verify, use any Bluetooth LE app and enable it to do advertising. Then, verify that the advertisement is not received by the peripheral.
  • 1 (default) – Allowed. When set to 1, the device will send out advertisements. To verify, use any Bluetooth LE app and enable it to do advertising. Then, verify that the advertisement is received by the peripheral.

Bluetooth/AllowDiscoverableMode

Windows Edition Supported?
Home cross mark
Pro check mark
Business check mark
Enterprise check mark
Education check mark

Scope:

[!div class = "checklist"]

  • Device

Specifies whether other Bluetooth-enabled devices can discover the device.

If this is not set or it is deleted, the default value of 1 (Allow) is used.

Most restricted value is 0.

The following list shows the supported values:

  • 0 – Not allowed. When set to 0, other devices will not be able to detect the device. To verify, open the Bluetooth control panel on the device. Then, go to another Bluetooth-enabled device, open the Bluetooth control panel, and verify that you cannot see the name of the device.
  • 1 (default) – Allowed. When set to 1, other devices will be able to detect the device. To verify, open the Bluetooth control panel on the device. Then, go to another Bluetooth-enabled device, open the Bluetooth control panel and verify that you can discover it.

Bluetooth/AllowPrepairing

Windows Edition Supported?
Home cross mark
Pro check mark1
Business check mark1
Enterprise check mark1
Education check mark1

Scope:

[!div class = "checklist"]

  • Device

Specifies whether to allow specific bundled Bluetooth peripherals to automatically pair with the host device.

The following list shows the supported values:

  • 0 – Not allowed.
  • 1 (default)– Allowed.

Bluetooth/AllowPromptedProximalConnections

Windows Edition Supported?
Home cross mark
Pro check mark4
Business check mark4
Enterprise check mark4
Education check mark4

Scope:

[!div class = "checklist"]

  • Device

Added in Windows 10, version 1803. This policy allows the IT admin to block users on these managed devices from using Swift Pair and other proximity based scenarios.

The following list shows the supported values:

  • 0 - Disallow. Block users on these managed devices from using Swift Pair and other proximity based scenarios
  • 1 - Allow (default). Allow users on these managed devices to use Swift Pair and other proximity based scenarios

Bluetooth/LocalDeviceName

Windows Edition Supported?
Home cross mark
Pro check mark
Business check mark
Enterprise check mark
Education check mark

Scope:

[!div class = "checklist"]

  • Device

Sets the local Bluetooth device name.

If this is set, the value that it is set to will be used as the Bluetooth device name. To verify the policy is set, open the Bluetooth control panel on the device. Then, go to another Bluetooth-enabled device, open the Bluetooth control panel, and verify that the value that was specified.

If this policy is not set or it is deleted, the default local radio name is used.

Bluetooth/ServicesAllowedList

Windows Edition Supported?
Home cross mark
Pro check mark
Business check mark
Enterprise check mark
Education check mark

Scope:

[!div class = "checklist"]

  • Device

Added in Windows 10, version 1511. Set a list of allowable services and profiles. String hex formatted array of Bluetooth service UUIDs in canonical format, delimited by semicolons. For example, {782AFCFC-7CAA-436C-8BF0-78CD0FFBD4AF}.

The default value is an empty string. For more information, see ServicesAllowedList usage guide

Bluetooth/SetMinimumEncryptionKeySize

Windows Edition Supported?
Home cross mark
Pro check mark7
Business check mark7
Enterprise check mark7
Education check mark7

Scope:

[!div class = "checklist"]

  • Device

Added in the next major release of Windows 10. There are multiple levels of encryption strength when pairing Bluetooth devices. This policy helps prevent weaker devices cryptographically being used in high security environments.

The following list shows the supported values:

  • 0 (default) - All Bluetooth traffic is allowed.
  • N - A number from 1 through 16 representing the bytes that must be used in the encryption process. At this time, 16 is the largest allowed value for N and 16 bytes is the largest key size that Bluetooth supports so far. If you wish to enforce Windows to use Bluetooth encryption at all times, but do not care about the precise encryption key strength, use a value of 1.

Footnotes:

  • 1 - Added in Windows 10, version 1607.
  • 2 - Added in Windows 10, version 1703.
  • 3 - Added in Windows 10, version 1709.
  • 4 - Added in Windows 10, version 1803.
  • 5 - Added in Windows 10, version 1809.
  • 6 - Added in Windows 10, version 1903.
  • 7 - Added in the next major release of Windows 10.

ServicesAllowedList usage guide

When the Bluetooth/ServicesAllowedList policy is provisioned, it will only allow pairing and connections of Windows PCs and phones to explicitly defined Bluetooth profiles and services. It is an allowed list, enabling admins to still allow custom Bluetooth profiles that are not defined by the Bluetooth Special Interests Group (SIG).

  • Disabling a service shall block incoming and outgoing connections for such services
  • Disabling a service shall not publish an SDP record containing the service being blocked
  • Disabling a service shall not allow SDP to expose a record for a blocked service
  • Disabling a service shall log when a service is blocked for auditing purposes
  • Disabling a service shall take effect upon reload of the stack or system reboot

To define which profiles and services are allowed, enter the semicolon delimited profile or service Universally Unique Identifiers (UUID). To get a profile UUID, refer to the Service Discovery page on the Bluetooth SIG website.

These UUIDs all use the same base UUID with the profile identifiers added to the beginning of the base UUID.

Here are some examples:

Example of how to enable Hands Free Profile (HFP)

BASE_UUID = 0x00000000-0000-1000-8000-00805F9B34FB

UUID name Protocol specification UUID
HFP(Hands Free Profile) Hands-Free Profile (HFP) * 0x111E

Footnote: * Used as both Service Class Identifier and Profile Identifier.

Hands Free Profile UUID = base UUID + 0x111E to the beginning = 0000111E-0000-1000-8000-00805F9B34FB

Allow Audio Headsets (Voice)

Profile Reasoning UUID
HFP (Hands Free Profile) For voice-enabled headsets 0x111E
Generic Audio Service Generic audio service 0x1203
Headset Service Class For older voice-enabled headsets 0x1108
PnP Information Used to identify devices occasionally 0x1200

This means that if you only want Bluetooth headsets, the UUIDs to include are:

{0000111E-0000-1000-8000-00805F9B34FB};{00001203-0000-1000-8000-00805F9B34FB};{00001108-0000-1000-8000-00805F9B34FB};{00001200-0000-1000-8000-00805F9B34FB}

Allow Audio Headsets and Speakers (Voice & Music)

Profile Reasoning UUID
HFP (Hands Free Profile) For voice enabled headsets 0x111E
A2DP Source (Advance Audio Distribution) For streaming to Bluetooth speakers 0x110B
Generic Audio Service Generic service used by Bluetooth 0x1203
Headset Service Class For older voice-enabled headsets 0x1108
AV Remote Control Target Service For controlling audio remotely 0x110C
AV Remote Control Service For controlling audio remotely 0x110E
AV Remote Control Controller Service For controlling audio remotely 0x110F
PnP Information Used to identify devices occasionally 0x1200

{0000111E-0000-1000-8000-00805F9B34FB};{0000110B-0000-1000-8000-00805F9B34FB};{00001203-0000-1000-8000-00805F9B34FB};{00001108-0000-1000-8000-00805F9B34FB};{0000110C-0000-1000-8000-00805F9B34FB};{0000110E-0000-1000-8000-00805F9B34FB};{0000110F-0000-1000-8000-00805F9B34FB};{00001200-0000-1000-8000-00805F9B34FB};

Classic Keyboards and Mice

Profile Reasoning UUID
HID (Human Interface Device) For classic BR/EDR keyboards and mice 0x1124
PnP Information Used to identify devices occasionally 0x1200

{00001124-0000-1000-8000-00805F9B34FB};{00001200-0000-1000-8000-00805F9B34FB};

LE Keyboards and Mice

Profile Reasoning UUID
Generic Access Attribute For the LE Protocol 0x1801
HID Over GATT * For LE keyboards and mice 0x1812
GAP (Generic Access Profile) Generic service used by Bluetooth 0x1800
DID (Device ID) Generic service used by Bluetooth 0x180A
Scan Parameters Generic service used by Bluetooth 0x1813

Footnote: * The Surface pen uses the HID over GATT profile

{00001801-0000-1000-8000-00805F9B34FB};{00001812-0000-1000-8000-00805F9B34FB};{00001800-0000-1000-8000-00805F9B34FB};{0000180A-0000-1000-8000-00805F9B34FB};{00001813-0000-1000-8000-00805F9B34FB}

Allow File Transfer

Profile Reasoning UUID
OBEX Object Push (OPP) For file transfer 0x1105
Object Exchange (OBEX) Protocol for file transfer 0x0008
PnP Information Used to identify devices occasionally 0x1200

{00001105-0000-1000-8000-00805F9B34FB};{00000008-0000-1000-8000-00805F9B34FB};{00001200-0000-1000-8000-00805F9B34FB}

Disabling file transfer shall have the following effects

  • Fsquirt shall not allow sending of files
  • Fsquirt shall not allow receiving of files
  • Fsquirt shall display error message informing user of policy preventing file transfer
  • 3rd-party apps shall not be permitted to send or receive files using MSFT Bluetooth API