Embedded System Dual Runtime Mode for Secure Development Access
Solution Overview
Problem
Existing edge computing systems face challenges in providing secure access for development, debugging, and testing on industrial edge devices, as IT-security constraints limit full access needed during development and operation phases, leading to late detection of software issues and increased development costs.
Innovation Solution
Implementing two runtime modes on edge devices: a first mode with predefined IT-security constraints and a second mode with elevated rights for development operations, allowing access and execution with elevated privileges for a predefined time period, which can be switched automatically or by a system administrator.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IT-security constraints are enforced on edge devices, then security is improved, but access for development and debugging is restricted
Solution Approach 1:
The system dynamically switches between two runtime modes: a first runtime mode with IT-security constraints enforced, and a second runtime mode with elevated access rights for development and debugging. This dynamic transition allows the system to adapt its security posture based on operational context, resolving the contradiction between security and development access.
Solution Approach 2:
The system changes the security parameter state by transitioning between runtime modes. In the first runtime mode, security constraints are active; in the second runtime mode, security constraints are relaxed to allow elevated access. This parameter change enables the system to satisfy both security requirements and development access needs at different times.
2Productivity
If full access is provided during development, then development efficiency is improved, but security risks increase
Solution Approach 1:
The system uses dynamic mode switching to provide full access during development phases (second runtime mode) while enforcing security constraints during normal operation (first runtime mode). This temporal separation allows high productivity during development without exposing the system to security risks during production.
Solution Approach 2:
The system periodically transitions between development mode and operation mode, allowing full access during development periods and security-constrained access during operation periods. This periodic action pattern enables the system to achieve both development efficiency and security by alternating between the two states.
3Reliability
If security constraints are enforced during operation, then system security is improved, but software issue detection is delayed
Solution Approach 1:
The system dynamically transitions to the second runtime mode when development or debugging activities are needed, allowing rapid software issue detection with elevated access rights. After debugging is complete, the system returns to the first runtime mode to enforce security constraints, thus resolving the contradiction between security and timely issue detection.
Solution Approach 2:
The system performs preliminary actions by switching to the second runtime mode before debugging activities begin, allowing developers to access the system with elevated rights to detect and fix software issues. This preliminary mode switch ensures that issue detection can proceed quickly without security constraints, while the system remains secure during normal operation.
Data Source
AI summary
A method for controlling access to at least one computer program which is accessible and executable on an embedded system is disclosed. The embedded system is provided and comprises two different runtime modes, a first runtime mode and a second runtime mode. In the first runtime mode, a predefined set of IT-security constraints is associated with the at least one computer program. In the second runtime mode at least a part of the predefined set of the IT-security constraints associated with the at least one computer program is void and the at least one computer program is accessible and executable with elevated rights for performing software development operations on the at least one computer program. The embedded system is set into the second runtime mode for a predefined time period. After the predefined time period is expired, the embedded system is set into the first runtime mode.