A GATT UUID is the 16-bit or 128-bit identifier used in Bluetooth Low Energy to name a Generic Attribute Profile service, characteristic, or descriptor. It lets a client discover and access specific attributes on a device, and the UUID is the key used to distinguish one exposed capability from another.
What the GATT UUID identifies
In Bluetooth Low Energy, a GATT UUID is the identifier that names a service, characteristic, or descriptor inside the Generic Attribute Profile. It is not just a label, it is how a client finds the exact attribute it wants to read, write, subscribe to, or enumerate on a device.
The distinction matters because BLE devices often expose several attributes at once. The UUID is what separates a battery service from a sensor characteristic, or one descriptor from another, so the client can target the right capability without guessing.
How GATT UUIDs structure BLE discovery
GATT is the attribute model that makes BLE usable beyond a simple radio link. During discovery, the client learns which services exist, which characteristics each service exposes, and which descriptors refine those characteristics. The UUID is the stable identifier that ties that structure together across devices and sessions.
This structure is why UUIDs matter at both the specification level and the implementation level. Developers can reuse standard 16-bit UUIDs for common Bluetooth services, while vendors can define 128-bit UUIDs for custom capabilities. That flexibility keeps the model interoperable without forcing every device to expose the same feature set.
Why the UUID size and format matter
A 16-bit UUID usually indicates a standardized Bluetooth-defined attribute, while a 128-bit UUID is commonly used for custom or vendor-specific attributes. The size alone does not tell you whether the attribute is safe or trusted, but it does tell you something about naming scope and interoperability expectations.
Because the UUID is used as a lookup key, collisions or sloppy reuse create confusion at the application layer. A client that assumes the wrong service or characteristic can read the wrong value, write to the wrong endpoint, or mis-handle a device capability. In practice, the UUID namespace is part of how BLE keeps device behaviour predictable.
How practitioners use GATT UUIDs in implementation
Implementers use UUIDs when they design profiles, map application logic to BLE attributes, and decide which services should be discoverable. The most important discipline is consistency: the UUID published by the device must match the client logic that consumes it, otherwise discovery succeeds but the application still fails.
For custom BLE designs, good UUID hygiene is mostly about avoiding ambiguity. Use standard UUIDs when the attribute already has a standard meaning, use unique vendor UUIDs when it does not, and keep service, characteristic, and descriptor naming aligned so that clients can distinguish capability boundaries correctly.
Risk and Threat Considerations
UUIDs are not secrets, but they do define what a BLE client can discover and target, so mistakes can expose unintended functionality or make a device easier to interrogate. The main risk is not the UUID itself, but weak attribute design, broad exposure, or poor authorization around attributes that should not be freely accessible.
Failure mechanism: If a sensitive characteristic is discoverable or writable without strong access control, an attacker or untrusted client may enumerate device capabilities, infer hidden functions, or abuse a management endpoint that was assumed to be obscure rather than protected.
Impact: The result can be unintended data exposure, unsafe device behaviour, or unauthorized control over a BLE feature. In security-sensitive devices, that can translate into integrity loss, privacy leakage, or a stepping stone to broader device compromise.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | BLE UUID-driven access often depends on controlled attribute access and credential handling. |
| AC-6 — Least Privilege | Sensitive BLE characteristics should expose only the minimum access needed by clients. | |
| Recommendation — Manage attribute-facing credentials and rotate them when BLE access paths change. Restrict BLE attribute permissions to the minimum access required for each client role. | ||
| NIST CSF 2.0 | PR.AA-01 — Identity Management, Authentication, and Access Control | BLE attribute access depends on identifying and controlling who can discover or use functions. |
| Recommendation — Apply access control to BLE-exposed capabilities so only intended clients can use them. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | BLE attribute exposure is governed by who can discover and invoke device functions. |
| Recommendation — Limit BLE attribute access to approved users, devices, or applications. | ||
Practitioner Guidance
What to watch for: Treat UUID design as part of the device’s public interface, not just an implementation detail. Standard UUIDs should be reserved for standard behaviour, and custom UUIDs should be stable, unique, and documented so clients do not silently bind to the wrong attribute.
Governance implication: If an attribute matters for safety, privacy, or control, do not rely on obscurity in the UUID name. Make sure the device enforces the right access checks at the attribute layer, because discovery naming alone does not provide protection.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org