EnOcean Security Model

EnOcean Security Model
All EnOcean modules have a  unique 32-bit identification number (ID),  which cannot be changed or copied and therefore protects against duplication. This authentication method already offers field-proven secure and reliable communication in building automation. For applications requesting additional data security, a security mode protects battery-less wireless communication with enhanced security measures. These include a maxi- mum 24-bit rolling code (RC) incremented with each telegram, which is used to calculate a maximum 32-bit cipher-based message authentication code (CMAC). The CMAC uses the AES 128 encryption algorithm. Another mechanism is the encryption of data packets by the transmitter. The data is encrypted using the AES algorithm with a 128-bit key.

EnOcean Security Model

 
The EnOcean standard 868 MHz sensor modules integrate these state-of-the-art data encryption mechanisms to meet the requirements of specific applications such as monitoring or alert sensor systems. These enhanced security mechanisms can optionally be activated to prevent different types of attacks, including replay and eavesdropping attacks or forging of messages. Shipped in standard mode, the encrypted data transmission can be activated by simply pressing the learn button for ten seconds. If needed, the security mode can be deactivated by pressing and holding the learn button again. Also a receiver that decodes encrypted telegrams can still process standard telegrams enabling OEMs to effortlessly include enhanced data security in their existing EnOcean-based portfolio.

One fundamental problem with both content protection and content authentication is that using the same input data (plain text) with the same key always yields the same encrypted data and same signature. In order to prevent this type of attack, either the data or the key must continuously change to ensure that identical input data does not create The mechanism used by the transmitter to change data or key must be known to the receiver in order to correctly decrypt and authenticate received data telegrams. One common approach is to use the secret key together wit to generate a dynamic key.

Summary
1. Feature: content protection – implemented with: data encryption
2. Feature: content authentication – implemented with: CMAC – cipher based message authentication
3. Feature: dynamic content modification – implemented with: RLC – rolling code

 

 14byte

Contact Us

Contact us via phone (+1 866-383-1657) or leave a detailed message below for sales, support, or any other needs

*Required Field
*Required Field
I'd like to receive the newsletter. *Check email for confirmation.
*Required Field
8:00am - 12:00pm 12:00pm - 5:00pm