Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Z-Wave Security?

Z-Wave security covers the S0 and S2 frameworks protecting a sub-gigahertz mesh used in smart locks, alarms, and building controls, where the pairing step decides whether the network can be attacked.

Illustration for the cybersecurity term Z-Wave Security
Home / Blog / Cybersecurity Terms / What Is Z-Wave Security?
17 November 2026

What Is Z-Wave Security?

What Is Z-Wave Security?

Z-Wave is a proprietary low-power mesh protocol for home and building automation, operating below 1 GHz — 868.42 MHz in the United Kingdom and the rest of Europe. The lower frequency is its selling point against 2.4 GHz alternatives: better propagation through walls, and no contention with Wi-Fi. It is widely used for smart locks, alarm sensors, blinds, and heating control, which means its security failures have physical consequences.

The protocol is controlled by Silicon Labs, which acquired the technology from Sigma Designs in 2018, and the specification was later opened for public ratification. Its security story divides cleanly into before and after S2.

S0: AES With a Fatal Pairing Step

The original security framework, introduced in 2013, encrypted traffic with AES-128. The encryption was fine. The problem was how the network key reached a new device: during inclusion, the controller sent it protected by a temporary key consisting entirely of zeros.

That value is in the specification, so anyone who captured the pairing exchange could decrypt the network key and then read and inject commands indefinitely. The attack required being within radio range at the moment a device was added — a narrow window in a home, but a much wider one in a building where installers commission dozens of devices over several days.

S2: Proper Key Agreement

Security 2 became mandatory for new certifications on 2 April 2017 and replaced that exchange with an elliptic curve Diffie-Hellman agreement over Curve25519. Passive capture of the pairing no longer yields the key.

Protection against an active intermediary comes from out-of-band verification: each device has a Device Specific Key, printed on it as a five-digit number and usually also as a QR code, and the installer enters or scans it during inclusion. The controller checks that the public key it received matches, which an attacker in the middle cannot satisfy.

S2 defines three security classes, and the distinction matters when specifying equipment:

The Z-Shave Downgrade

Backwards compatibility undermined this in practice. Because S2 controllers still had to include older S0 devices, the inclusion exchange negotiated which framework to use — and that negotiation was not protected. In May 2018 researchers at Pen Test Partners demonstrated forcing an S2-capable smart lock to pair using S0, after which the zero-key weakness applied and the network key was recoverable. The demonstration used a Yale lock and became known as Z-Shave.

Vendors responded by requiring user notification and confirmation when a downgrade occurs, so the behaviour is visible rather than silent. The underlying lesson holds generally: a protocol is only as strong as the weakest version it will negotiate down to, which is the same structural issue that affects WPA2/WPA3 transition mode.

Testing and Tooling

Z-Wave traffic is captured with a Silicon Labs Zniffer using a compatible USB stick, or from the raw radio with a software-defined radio such as a HackRF or YARD Stick One. The EZ-Wave toolkit, published in 2016, demonstrated discovery, interrogation, and command injection against unsecured devices using SDR hardware. The common findings in assessment are predictable: devices included without security because the installer used a quick-add method, S2 Unauthenticated used where Access Control was required, and a controller sitting on the main corporate or home network with a cloud account protected by a reused password.

Deploying It Sensibly

  1. Specify S2 certified devices, and for locks and entry systems insist on the S2 Access Control class.
  2. Pair using the QR code or printed DSK every time. Skipping it discards the protection that distinguishes S2 from S0.
  3. Commission in a controlled place and time. If practical, pair devices before installation, in an area where an attacker is unlikely to be waiting.
  4. Configure the controller to warn on downgrade and investigate every occurrence.
  5. Do not rely on radio alone for security-critical functions. A lock should fail safe and an alarm should have a second reporting path.
  6. Treat the controller as a computer: patch it, give its cloud account multi-factor authentication, and keep it off the network your business systems use.

Our IoT Penetration Test Services assess Z-Wave estates including inclusion behaviour, which is where the difference between a certified device and a securely deployed one becomes obvious.

FAQ – Frequently Asked Questions

Is S2 Mandatory on All Z-Wave Devices?

It has been required for new product certification since April 2017, so current devices support it. That does not mean a given network uses it. Older devices remain in service, controllers still include them, and an installer in a hurry can pair a capable device without security. Check what security class each node actually negotiated rather than what the box claims.

What Is the Device Specific Key?

A value unique to each device, printed on it as five digits and usually also as a QR code, that authenticates the key agreement during inclusion. Entering or scanning it lets the controller confirm it is talking to the intended device rather than an attacker. Skipping this step drops the pairing to S2 Unauthenticated, which an active attacker can intercept.

Can Z-Wave Devices Be Jammed?

Yes. The 868 MHz band in the UK is licence exempt and a determined transmitter can suppress communication, which for a sensor means it simply stops reporting. Design around it: use controllers that alert on loss of contact with a node, and never make an alarm or safety function depend on a single wireless path.

How Does Z-Wave Compare with Zigbee?

Z-Wave uses sub-gigahertz radio, giving better range and no Wi-Fi contention, and operates as a closed certified ecosystem with strong interoperability. Zigbee uses 2.4 GHz, supports higher data rates, and has a more open device market. Security is now comparable: S2 with out-of-band verification is broadly equivalent to Zigbee 3.0 with install codes, and both fail the same way when pairing is rushed.

Related Terms

You May Be Interested In These

What Is a DDoS Attack?

Cybersecurity Terms

15 May 2021

What Is a DDoS Attack?

Read More
What Is Ransomware Negotiation?

Cybersecurity Terms

17 November 2026

What Is Ransomware Negotiation?

Read More
What Is Phishing?

Cybersecurity Terms

17 November 2026

What Is Phishing?

Read More