Code-signed modules

To ensure secure installation, each software module (file) is digitally signed. At run time, the system validates each module’s signature. This ensures that malware cannot modify the code (core framework content) during commissioning.

Each software module is distributed with a runtime profile, designated by a suffix on the module’s file name. Many modules have multiple runtime profiles. For example, the alarm module is distributed as three separate .jar files: alarm-rt, alarm-se, and alarm-wb. The suffixes -rt, -se, and -wb identify the associated profile. The module signature is based on the module’s runtime profile and runtime profiles define what type of software module to install.

Although these features are seamless to the user, knowing about them provides assurance of system security.