NIST SP 800-121 Revision 2, "Guide to Bluetooth Security," gives organizations a working reference for Bluetooth's built-in security modes and a checklist for hardening the devices, firmware and policies around them. Its own Introduction frames the purpose directly: "to provide information to organizations on the security capabilities of Bluetooth and provide recommendations to organizations employing Bluetooth wireless technologies on securing them effectively." Authored by John Padgette, John Bahr, Mayank Batra, Marcel Holtmann, Rhonda Smithbey, Lily Chen and Karen Scarfone, it was originally published in May 2017 and received a substantive errata correction on 19 January 2022 (a clarification to the Security Mode 1 Level 4 cryptography description in Section 3.2.1). NIST's publication page lists it as Final, covering Bluetooth versions 1.1 through 4.2 — explicitly not Bluetooth 5.0, which the Introduction states "is not in the scope of this document."
Key takeaways
- NIST SP 800-121 Revision 2, "Guide to Bluetooth Security," gives organizations a working reference for Bluetooth's built-in security modes and a checklist for hardening the devices, firmware and policies around them.
- Bluetooth is embedded in a huge range of connected products: wearables, medical devices, industrial sensors, access-control hardware, and consumer IoT of every kind.
- Section 3 states that "the family of Bluetooth BR/EDR/HS specifications defines four security modes.
- LE Security Mode 2 — levels tied to data signing (integrity, not confidentiality).
Why should a device maker care about SP 800-121?
Bluetooth is embedded in a huge range of connected products: wearables, medical devices, industrial sensors, access-control hardware, and consumer IoT of every kind. SP 800-121 is one of the few vendor-neutral, publicly free references that explains which Bluetooth security mode and level a given radio implements, and whether that is the strongest option available for its Bluetooth version. Those are design decisions that live in firmware and stack configuration, so they belong in the same review as the component inventory a firmware SBOM provides.
What are the BR/EDR/HS security modes, 1 through 4?
Section 3 states that "the family of Bluetooth BR/EDR/HS specifications defines four security modes. Each Bluetooth device must operate in one of these modes, called Security Modes 1 through 4."
| Mode | How it behaves | NIST's guidance |
|---|---|---|
| Mode 1 | Never initiates security; no authentication, no encryption | "NIST recommends never using Security Mode 1" |
| Mode 2 | Service-level-enforced: security may start after link establishment but before logical channel setup | Authentication/encryption implemented in the controller; superseded in 2.1+ by Mode 4 |
| Mode 3 | Link-level-enforced: a device initiates security procedures before the link is fully established | Recommended for Bluetooth 2.0 and older devices |
| Mode 4 | Service-level-enforced using Secure Simple Pairing (SSP) with ECDH key agreement | Mode 4 Level 4 recommended for 4.1 BR/EDR/HS devices; Mode 4 Level 3 recommended for 2.1 through 4.0 devices |
The Executive Summary is explicit about the hierarchy: "For Bluetooth 4.1 devices that have BR, EDR, and High Speed (HS) features, Security Mode 4, Level 4 is recommended because it requires Secure Connections, which uses authenticated pairing and encryption using 128-bit strength keys generated using FIPS-approved Advanced Encryption Standard (AES) encryption."
How do low energy security modes and pairing differ?
Low energy devices (Bluetooth 4.0 and later) use a separate pair of security modes, defined in Section 3.2.1:
- LE Security Mode 1 — levels tied to encryption, from Level 1 (no security) up to Level 4, added in Bluetooth 4.2, which "requires authenticated low energy Secure Connections pairing with encryption" using AES-CMAC and P-256 elliptic curve for pairing and AES-CCM for encryption. NIST "strongly recommends its use for all low energy connections in 4.2."
- LE Security Mode 2 — levels tied to data signing (integrity, not confidentiality).
A sharp warning in Section 3.2.2: LE Legacy Pairing (the 4.0/4.1 pairing method, renamed once 4.2 introduced Secure Connections pairing) "should be considered broken" for every pairing method except out-of-band with a 128-bit temporary key, "because if an attacker can capture the pairing frames, he or she can determine the resulting LTK" — the Long-Term Key used to encrypt the link. Bluetooth 4.2 also added a Secure Connections Only Mode, which forces every service except the no-security Level 1 case onto LE Security Mode 1 Level 4, guaranteeing only FIPS-approved algorithms are used on the physical transport — at the cost of breaking backward compatibility with 4.0/4.1 LE devices, which don't support the P-256 curve.
Which pairing association model should a product use?
The one with the strongest protection that the product's input and output allow. The SP 800-121 Rev. 2 text (§3.1.1.2 for BR/EDR, §3.2.2 for LE) describes four models, and the radio picks one from the two devices' declared capabilities:
| Model | Needs | MITM protection | NIST notes |
|---|---|---|---|
| Numeric Comparison | A display and yes/no input on both devices | Yes | The six-digit value is not an input to key generation, so seeing it does not help an eavesdropper; for LE, only with 4.2 Secure Connections |
| Passkey Entry | Keyboard on one device, display or keyboard on the other | Yes | Six digits give at most 20 bits of entropy; NIST recommends "a unique, random passkey for each pairing" |
| Out of Band (OOB) | A shared second channel such as NFC | Depends on the OOB channel | Protection is only as good as the OOB link's own eavesdropping and MITM resistance |
| Just Works | Nothing; for devices with no display or keyboard | No | Produces an unauthenticated key; in LE Legacy Pairing the temporary key is all zeros |
The I/O capabilities a product advertises are therefore a security decision. A device that declares "no input, no output" to simplify setup forces Just Works on every pairing.
Which named Bluetooth attacks does Section 4.2 describe?
The guide names several Bluetooth-specific attacks on top of general wireless threats (denial of service, eavesdropping, MITM, message modification):
- Bluesnarfing — exploits "a firmware flaw in older (circa 2003) devices" to force a connection and read stored data, including the device's IMEI.
- Bluejacking — sending unsolicited messages to a Bluetooth device's owner, "resembles spam and phishing attacks."
- Bluebugging — exploits "a security flaw in the firmware of some older (circa 2004) Bluetooth devices" to run the device's commands (placing calls, eavesdropping, sending messages) without the owner's knowledge.
- Car Whisperer — exploits a standard, non-random passkey in hands-free car kits to transmit or receive audio.
- Fuzzing attacks and pairing eavesdropping — malformed-data probing, and capturing PIN/Legacy or LE Legacy pairing frames to recover the secret key.
- Secure Simple Pairing attacks — forcing a device into the unauthenticated "Just Works" method, which provides no MITM protection.
The three attacks tied to "older (circa 2003-2004)" firmware flaws are a direct reminder that Bluetooth security is a firmware property, not just a protocol-configuration one — the same device can carry a vulnerable Bluetooth stack years after the spec itself added stronger modes, which is exactly what a firmware SBOM and vulnerability match are built to catch.
Which Table 4-1 weaknesses are decided in firmware?
Table 4-1, "Key Problems with Native Bluetooth Security," lists 27 issues with the Bluetooth versions each affects. Several are not fixed by the specification at all; they depend on how the device maker configures and implements the stack:
| # | Issue (Table 4-1) | Firmware or design decision |
|---|---|---|
| 8 | SSP ECDH key pairs may be static or weakly generated | Generate unique, strong key pairs that change regularly |
| 9 | Static SSP passkeys facilitate MITM attacks | Random passkey per pairing attempt, never a printed constant |
| 10 | Mode 4 devices may fall back to any mode, including Mode 1 | Limit fallback; NIST "strongly recommends" falling back to Mode 3 |
| 19 | Link keys can be stored improperly | Protect key storage with access controls |
| 20 | PRNG strength is unknown | Use strong generators per NIST SP 800-90 guidance |
| 21 | Encryption key length is negotiable | Enforce full-length keys; NIST recommends Secure Connections Only Mode |
| 25 | Discoverable or connectable devices are prone to attack | Discoverable only for a short pairing window |
| 26 | Just Works provides no MITM protection | "Just Works pairing should not be used for low energy" |
Item 21 is the root of a later, widely reported attack class: the 3.0 and earlier specifications let devices negotiate keys as small as one byte, while LE requires a minimum of seven bytes.
What has the Bluetooth SIG published since Rev. 2?
Several specification-level vulnerabilities, each with a SIG security notice and a CVE. SP 800-121 Rev. 2 predates all of them, so a current design review needs both documents. The SIG lists its notices on the reporting security vulnerabilities page; a selection relevant to device firmware:
| Notice (year) | CVE | Specifications affected (SIG list) | SIG mitigation in brief |
|---|---|---|---|
| Key Negotiation of Bluetooth, KNOB (2019) | CVE-2019-9506 | Core v4.2, 5.0, 5.1 | Enforce a minimum BR/EDR encryption key length |
| Bluetooth Impersonation Attacks, BIAS (2020) | CVE-2020-10135 | Core v2.1 to 5.2 | No key length below 7 octets, mutual authentication in legacy authentication, Secure Connections Only mode where possible |
| Pairing Method Confusion (2020) | CVE-2020-10134 | Core v2.1 to 5.2 | UI and documentation that warn users not to enter the numeric-comparison value as a passkey |
| Cross-Transport Key Derivation, BLURtooth (2020) | CVE-2020-15802 | Core v4.2 to 5.0 | Apply the CTKD restrictions mandated in Core 5.1 and later |
| BLUFFS (2023) | CVE-2023-24023 | Core v4.2 to 5.2; the notice text and NVD say 4.2 through 5.4 | Notes 7 octets as the recommended minimum BR/EDR key length |
The common thread is the same as Table 4-1 item 21: negotiated key length and downgrade to legacy procedures. Each notice also asks vendors to "rapidly integrate any necessary patches," which for a device maker means tracking the Bluetooth stack version in every shipped image. Report a suspected specification flaw to the SIG at the address on the same page; implementation bugs go to your chip or stack vendor's PSIRT.
How do you use the Table 4-2 checklist?
Table 4-2, the Bluetooth Piconet Security Checklist, organizes recommendations under Management (write a Bluetooth security policy, run regular assessments, maintain a device inventory by BD_ADDR, train users) and Technical headings (change default settings, set the lowest necessary transmit power, use random and sufficiently long PINs, use unique passkeys per pairing, disable unneeded profiles and services, use the strongest available mode), each marked Recommended Practice or Should Consider, with a blank Status column meant for literal use as an audit checklist. Table 4-3 then maps checklist items to specific NIST SP 800-53 Revision 4 controls, letting an assessor tie a Bluetooth finding directly to a control family — the same cross-reference pattern SP 800-128 uses for its own configuration-management checklist. For a manufacturer, the Technical rows double as product requirements: whatever defaults you ship are the defaults a customer's audit will find.
Worked example: which settings fit a headless BLE sensor?
Synthetic example, not a real product. A battery-powered BLE temperature sensor has one button and an LED, pairs with a phone app, and uses a Bluetooth 5.x controller. The team reviews it against SP 800-121 and the SIG notices:
Pairing modelWith no display or keyboard, the sensor would fall into Just Works, which NIST says should not be used for LE. The team adds an NFC tag for OOB pairing, keeping Just Works out of the field build. Mode and levelLE Security Mode 1 Level 4 with Secure Connections Only Mode, since the app runs on phones that support LE Secure Connections; Legacy Pairing is refused. DiscoverabilityAdvertising for pairing only for two minutes after a button press, per Table 4-1 item 25. Keys and randomnessBonding keys stored in the controller's protected storage; the firmware RNG checked against the chip vendor's documentation. Stack trackingThe Bluetooth host stack version is recorded in the per-release SBOM so that a new SIG notice or CVE can be matched to shipped versions.
Item 1 shows why scope matters: SP 800-121 stops at 4.2, but its pairing analysis still decides this 5.x design. For the LE protocol details, see our Bluetooth LE security guide.
How should a device maker start, and what are the pitfalls?
Identify the actual Bluetooth version and security mode each device implementsbefore assuming it supports the strongest option — a chip from 2015 may be stuck on Mode 3 even though Mode 4 existed since Bluetooth 2.1. Treat Security Mode 1 (and LE Legacy Pairing without out-of-band exchange) as a finding, not a defaultNIST's own language is "should never be used" / "should be considered broken." Run Table 4-2 as a literal auditagainst each product line — policy and inventory items first, then the technical defaults. Remember the scope boundary: this guide stops at Bluetooth 4.2. For 5.x radios, use this guide's threat categories and checklist structure as background, and confirm current mode/level guidance against Bluetooth SIG and NIST's more recent publications before relying on specific recommendations.
Common pitfalls:
- Declaring minimal I/O capabilities for convenience, which silently forces Just Works.
- Leaving the chip vendor's sample configuration in production, including static passkeys or permanent discoverability.
- Patching the phone app but not the device: KNOB-class fixes have to reach the device's controller or host stack, usually through a firmware update.
- Reading "Bluetooth 5" as "secure": newer specifications keep legacy procedures for backward compatibility, and the BIAS and BLUFFS attacks both work by downgrading to them.
SoftWSP covers the component side of this review: it extracts a CycloneDX SBOM from a firmware image, matches the packages it identifies against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report that an engineer reviews. It does not test which security mode or pairing model a radio negotiates; that needs the design review above. See Device & Firmware Security.
This guide summarises NIST SP 800-121 Revision 2 (May 2017, including the January 2022 errata update) and Bluetooth SIG security notices; it is not a substitute for the full text and does not constitute compliance or legal advice.
Put this guide to work
Frequently asked questions
What is NIST SP 800-121 Revision 2?
"Guide to Bluetooth Security," a NIST Special Publication that, per its own abstract, "provides information on the security capabilities of Bluetooth and gives recommendations to organizations employing Bluetooth wireless technologies on securing them effectively." Authored by John Padgette, John Bahr, Mayank Batra, Marcel Holtmann, Rhonda Smithbey, Lily Chen and Karen Scarfone, it was originally published in May 2017 as the second revision of SP 800-121 and carries a substantive errata update dated 19 January 2022 (tracked in its own Errata table). NIST's publication page lists its current status as Final. Scope is explicit: Bluetooth versions 1.1, 1.2, 2.0+EDR, 2.1+EDR, 3.0+HS, 4.0, 4.1 and 4.2 — the Introduction states plainly that "Bluetooth 5.0 is not in the scope of this document," so anyone assessing a 5.x radio needs to treat this guide as background, not a current checklist for that version.
What are the Bluetooth BR/EDR/HS security modes, and which does NIST recommend?
Section 3 states "the family of Bluetooth BR/EDR/HS specifications defines four security modes... Each Bluetooth device must operate in one of these modes, called Security Modes 1 through 4." Mode 1 initiates no security at all and "NIST recommends never using Security Mode 1." Modes 2 and 4 are service-level-enforced (security procedures start after the link is already established); Mode 3 is link-level-enforced (security starts before the link is established). The Executive Summary's own recommendation: "For Bluetooth 4.1 devices that have BR, EDR, and High Speed (HS) features, Security Mode 4, Level 4 is recommended" (Secure Connections, AES-128 encryption); "For Bluetooth 2.1 through 4.0 devices, Security Mode 4, Level 3 is the most secure"; "for Bluetooth 2.0 and older devices Security Mode 3 is recommended."
What is different about low energy (LE) security modes and pairing?
Section 3.2.1 defines two separate LE security modes: "Low energy Security Mode 1 has multiple levels associated with encryption" (Level 1 = no security, up to Level 4, added in Bluetooth 4.2, which "requires authenticated low energy Secure Connections pairing with encryption"); "Low energy Security Mode 2 has multiple levels associated with data signing" (integrity without confidentiality). NIST's own guidance: "NIST strongly recommends its use for all low energy connections in 4.2" for Mode 1 Level 4, and warns that LE Legacy Pairing (used before Bluetooth 4.2's Secure Connections pairing) "should be considered broken" for every pairing method except out-of-band with a 128-bit temporary key, because an attacker who captures the pairing frames can derive the resulting Long-Term Key.
What named attacks does the guide cover, and what else does the security checklist include?
Section 4.2 names and describes bluesnarfing (unauthorized access to data, including the device's IMEI, via an older firmware flaw), bluejacking (unsolicited messages, similar to spam/phishing), bluebugging (exploiting a firmware flaw to access a device's commands without the user's knowledge), the Car Whisperer tool (exploiting standard, non-random passkeys in hands-free car kits), denial-of-service, fuzzing attacks, pairing eavesdropping, and Secure Simple Pairing attacks that force a victim device into the unauthenticated "Just Works" method. Section 4.4's Table 4-2, the Bluetooth Piconet Security Checklist, organizes dozens of Management and Technical recommendations (policy, user awareness, device inventory, default-setting changes, discoverability limits, and more) into Recommended Practice / Should Consider columns plus a blank Status column for use as a literal audit checklist, and Table 4-3 maps several checklist items to specific NIST SP 800-53 Revision 4 control numbers.
Sources
- NIST: SP 800-121 Rev. 2, Guide to Bluetooth Security (includes updates as of 1-19-2022) — publication page
- NIST SP 800-121 Rev. 2 (Padgette, Bahr, Batra, Holtmann, Smithbey, Chen, Scarfone), full text PDF
- NIST CSRC: ITL Bulletin, Updated NIST Guidance for Bluetooth Security (July 2017)
- Bluetooth SIG: Reporting security vulnerabilities and Bluetooth security notices list
- Bluetooth SIG: Security notice, Key Negotiation of Bluetooth (KNOB, 2019)
- Bluetooth SIG: Security notice, Bluetooth Impersonation Attacks (BIAS, 2020)
- Bluetooth SIG: Security notice, Method-Confusion Pairing Vulnerability (2020)
- Bluetooth SIG: Security notice, Cross-Transport Key Derivation (BLURtooth, 2020)
- Bluetooth SIG: Security notice, BLUFFS (2023)
- NVD: CVE-2019-9506 (KNOB)
- NVD: CVE-2020-10135 (BIAS)
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 131 guides.

In this cluster
Questions about this page?
