← Back to the chapter · Previous detail

Technical detail · Z-Wave Architecture and Devices

Why S2 inclusion differs from S0

Security inclusion is part of architecture because it decides whether the controller knows and trusts the physical device it just added. S0 is legacy. S2 is the current security model used for sensitive devices such as locks, access-control devices, and many modern certified products.

Review itemS0 legacy behaviorS2 current behavior
Encryption primitiveAES-128 after inclusionAES-128 after inclusion
Inclusion key exchangeNetwork key sent under a hardcoded temporary keyECDH key agreement, commonly described with Curve25519 in Z-Wave S2 material
Device authenticationNo useful defense against a sniffer during pairingDevice Specific Key (DSK) confirmed by QR scan or PIN entry for authenticated inclusion
Practical weaknessSniffing inclusion can reveal the network keyResists inclusion-time interception and man-in-the-middle substitution when DSK verification is followed

The Device Specific Key (DSK) is printed on the device and encoded in its QR code; part of it is entered as a PIN for manual confirmation. During authenticated S2 inclusion, the installer confirms part of the DSK so the controller authenticates the exact physical device rather than a nearby impostor. S2 also separates keys by security class; a door lock can use an access-control class key that is distinct from ordinary sensor traffic.

S0’s weakness was concrete: to bootstrap encryption, the new device and controller exchanged the network key protected by a temporary key that was effectively public. An attacker recording that brief inclusion window could recover the network key, so security depended on nobody listening during pairing. S2 removes that pattern by deriving a shared secret through ECDH, where each side contributes public material but the resulting key is not transmitted in recoverable form, and, for authenticated inclusion, by verifying the physical device with its DSK.

← Back to the chapter · Previous detail