Configuration Data Storage Security via Restricted Mode

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing interconnectedness of devices in the Internet of Things (IoT) makes them vulnerable to malicious configuration data, which can persist even after device restarts, posing risks to system security and integrity.

Innovation Solution

A method and device configuration that involves receiving a trusted signal to enter a restricted mode, deactivating services, rebooting, and allowing configuration data entry into a secure portion of storage, with validation using security indicators and schemas to ensure trustworthiness, and the ability to invalidate untrusted data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If configuration data storage is made accessible for easy updates and modifications, then device adaptability and ease of operation are improved, but device vulnerability to malicious configuration data increases

Engineering Contradiction:
Improvedevice adaptabilityVSAvoiddevice vulnerability
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The configuration storage is segmented into multiple portions with different security characteristics. A first portion stores configuration data accessible during normal operation, while a second portion stores restricted configuration data that requires special authentication and restricted mode to access. This segmentation allows the device to maintain adaptability through the first portion while protecting against malicious data through the second portion's restricted access controls.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If configuration data entry is permitted during normal operation, then ease of operation is improved, but security against malicious data insertion deteriorates

Engineering Contradiction:
Improveconfiguration entry easeVSAvoiddata trustworthiness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Before permitting configuration data entry into the restricted portion, the system performs preliminary actions including receiving authentication credentials, verifying them against stored credentials, and only then transitioning to restricted mode. This preliminary verification ensures that only authorized users can initiate configuration entry, thereby maintaining ease of operation for legitimate users while ensuring data trustworthiness through pre-entry authentication.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary authentication mechanism between the user and the configuration storage. When configuration data entry is requested, the system mediates by requiring authentication credentials and verifying them through an authentication module before allowing access. This intermediary layer maintains ease of operation by providing a streamlined authentication process while ensuring reliability by blocking unauthorized access attempts.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If restricted mode with service deactivation and reboot is implemented, then security against malicious data is improved, but device complexity and operational time increase

Engineering Contradiction:
Improvesecurity integrityVSAvoidoperation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system dynamically transitions between normal mode and restricted mode based on the operation being performed. During normal operation, the device operates in normal mode with full service availability. When configuration data entry into the restricted portion is required, the system dynamically switches to restricted mode, deactivates non-essential services, and reboots if necessary. After successful configuration entry, the system dynamically returns to normal mode. This dynamic approach ensures security integrity when needed while minimizing operational complexity by maintaining simple normal operation for the majority of the time.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10671730B2Controlling configuration data storage
Publication Date: 2020.06.02 ARM IP
  • US10671730B2 patent drawing
  • US10671730B2 patent drawing
  • US10671730B2 patent drawing

AI summary

A machine-implemented method is provided for securing a storage-equipped device against introduction of malicious configuration data into configuration data storage, the method comprising steps of receiving by the device, a trusted signal for modification of the configuration of the device; responsive to the receiving, placing the device into a restricted mode of operation and at least one of deactivating a service and rebooting the device; responsive to the placing the device into the restricted mode of operation and the deactivating or rebooting, permitting configuration data entry into a restricted portion of the configuration data storage. A corresponding device and computer program product are also described.