RTU Privileged Mode Access Using a Local Hardware Selector
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software-only controls for switching between run-time and privileged modes on remote terminal units (RTUs) are insufficient for cybersecurity and reliability, as they allow unauthorized access that can compromise the operational integrity of critical infrastructure assets.
Innovation Solution
A combination of hardware and operating system mechanisms, including a hardware selector and a read-only production filesystem, ensures secure access to privileged functionality by requiring local physical access and preventing remote activation, with an overlay filesystem architecture for content extension.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If software-only controls are used to switch between run-time and privileged modes, then ease of operation is improved, but security and reliability deteriorate
Solution Approach 1:
The patent replaces software-only mode switching with a physical hardware switch mechanism. The hardware switch provides tactile feedback and requires physical manipulation, making it impossible to activate remotely through software attacks. This mechanical substitution ensures that privileged mode activation requires local physical access to the device, thereby maintaining security while preserving ease of operation through simple switch manipulation.
2Adaptability or versatility
If privileged access is required for development and deployment, then adaptability is improved, but security deteriorates
Solution Approach 1:
The patent segments the operational modes into distinct states (run-time mode and privileged mode) that are mutually exclusive at any given time. The hardware switch physically separates these modes, ensuring that when privileged mode is active for development and deployment, run-time operations are suspended. This segmentation prevents simultaneous execution of privileged and operational functions, eliminating the risk that privileged access could compromise operational integrity while still providing necessary adaptability for development.
3Ease of operation
If remote activation of privileged mode is allowed, then ease of operation is improved, but security deteriorates
Solution Approach 1:
The hardware switch acts as an intermediary between the user and the privileged mode activation. It serves as a physical mediator that must be manually manipulated locally, blocking any remote software-based activation attempts. The switch creates a physical barrier that prevents unauthorized remote access while still allowing legitimate local users to activate privileged mode when needed for development and deployment tasks.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A mode selector permits deactivating a run-time operational mode and activating a privileged operational mode on a remote terminal unit (RTU). One or more functionalities associated with the privileged operational mode are performed via a local and/or a remote computing device communicatively coupled to the RTU. The functionalities include at least one of developing and deploying content for the RTU, loading security certificates for the RTU, enabling Linux root account access to the RTU, and performing system maintenance on the RTU. The mode selector switch returns the RTU to the run-time operational mode after the functionalities are performed.