Security Guidelines for Devices¶
This chapter describes all mandatory and optional security guidelines for device builders to become a member of the Ecosystem.
Mandatory¶
Network Segmentation¶
Prohibit general routing or bridging between connected networks by default. It can be possible to adjust the routing via a configuration mechanism or installing specific apps if metrics on routes or individual routes mustbe set.
Hard Reset¶
Whenever the hard reset is triggered, it must be ensured that all security-relevant information e.g., passwords are securely deleted from the device.
Handling Of Onboarding Credentials¶
You need to deploy an appropriate edge device onboarding process. Ensure that onboarding trust file (JSON from IEM) is properly secured during transport from IEM to IED.
Time Synchronization¶
It is necessary to provide an up-to-date time on the device. Therefore, the platform provides NTP services within IEM which canbe used by IED. It is possible to also use other NTP compatible protocols, like NTPsec.
Storage of Credentials¶
The device needs the capability to storecredentials and certificates in a secure manner that cannot be manipulated
Storage of Artificats¶
It must be ensured that all directories, which contain IE packages and the corresponding volumes to store app data are protected against read access and modification.
Secure Logging¶
Devices must emit logs via an API to be able to export them on IEM e.g., for auditing or operational purposes.
Trusted Deployment Of Updates¶
Devices must implement a trusted deployment of updates to ensure the integrity of update packages
Authentication¶
If a user needs access to an Edge Device for administration or configuration purposes the access needs to be secured by a login mechanism with state-of-the-art credential policies.
Root Privileges / Runtime Protection¶
Based on the user roles, authentication must be enforced. Root-privileges are prohibited on productive devices.
Optional¶
Secure the Boot-Process¶
Deploy a secure boot mechanism like secure boot.