IoT Device Configuration Hash Verification for Security Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current building management systems (BMS) lack a secure method to verify if default IoT device configurations have been changed, posing a significant security risk due to unaltered default passwords and settings.

Innovation Solution

A method and system that generate and compare hash values for device configuration data to determine security compliance, using a processing circuit to analyze configuration data with a hash function and a server to receive and compare these values with pre-determined hash values, flagging non-compliance when defaults are not changed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If default configuration settings are used for IoT devices, then device complexity is reduced and ease of manufacture is improved, but security reliability deteriorates due to unaltered default passwords and settings

Engineering Contradiction:
Improveease of manufactureVSAvoidsecurity reliability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system performs preliminary action by generating hash values of default configuration settings during device manufacturing and storing them in a database before deployment. This allows automatic verification of whether default settings have been changed, resolving the contradiction by maintaining ease of manufacture while ensuring security reliability through pre-configured verification mechanisms

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by continuously monitoring and comparing current configuration hash values against stored default hash values. When deviations are detected, the system generates alerts and notifications, providing ongoing security verification that maintains reliability without adding complexity to the manufacturing process

Inventive Principle:
Principle #23Feedback

2Reliability

If a secure verification system for configuration settings is implemented, then security reliability is improved, but device complexity increases due to additional verification mechanisms

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

Solution Approach 1:

The system extracts the verification logic from the device itself and places it on the server side. The device only needs to send configuration data for hashing, while the server performs the complex verification operations by comparing hash values against the database. This reduces device complexity while maintaining security reliability through server-based verification

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces a server as an intermediary between devices and security verification. The server manages the database of default hash values and performs all comparison operations, acting as a mediator that enables secure verification without adding complexity to individual devices. This centralized approach maintains reliability while simplifying device architecture

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If configuration data is transmitted in plain text, then ease of operation is improved and device complexity is reduced, but information security deteriorates due to exposure of sensitive configuration data

Engineering Contradiction:
Improveease of operationVSAvoidinformation security
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system extracts only the essential configuration parameters needed for verification and transmits them as hashed values rather than complete configuration data. This selective transmission approach maintains ease of operation by sending minimal data while improving information security through hash obfuscation, preventing exposure of sensitive configuration details

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system transforms configuration parameters by applying hash functions to convert readable configuration data into non-reversible hash values. This parameter transformation maintains ease of operation for verification purposes while dramatically improving information security, as the hashed values cannot be reverse-engineered to reveal original sensitive data

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11757875B2System and method for checking default configuration settings of device on a network
Publication Date: 2023.09.12 TYCO FIRE & SECURITY GMBH
  • US11757875B2 patent drawing
  • US11757875B2 patent drawing
  • US11757875B2 patent drawing

AI summary

A method and system for securely verifying security compliance of a device on a network by generating a hash value for configuration data of the device, sending this value to a compliance service agent, comparing the hash value with hash value of default configuration data of the device, and reporting security non-compliance of the device when the generated hash value is same as the default hash values.