User's Manual

USER MANUAL

PTM 210 / PTM 215 / PTM 215U / PTM 215J

DC Step code and later

Figure 9 Example of harmful attacking scenarios PTM Modules are protected from

For details on the secure mechanisms please refer to the security specification of the EnOcean

Radio Protocol [3] together with the examples given in the application note

Secure telegrams include a rolling code based on an incrementing counter (RLC) which guar-

antees that identical message content will be encrypted differently.

The counter can be:

 Included in each data message - explicit (recommended)

 Not included in data messages – implicit (legacy, not recommended)

The counter value is also part of the teach-in telegram. The selection if the counter is implicit

or explicit is done via the NFC interface (see chapter 5.3.4.3) or special button combinations

at mode switching (see chapter 3.3).

There is no advantage in term of being “more secure” or “more protected” by using the

implicit mode over explicit or vice versa. The “protection level” and security mechanisms are

identical.

The RLC counter bit-size (24 bit explicit mode) practically ensures no “run over” will ever

occur and one RLC value is never reused during the PTMs lifetime twice. It is initialized to 0

at production.

http://www.enocean.com/fileadmin/redaktion/pdf/app_notes/AN509_Over-

view_of_EnOcean_Security_features.pdf