Lock Bit for Hash Function Security in Information Handling Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Information handling systems lack secure methods to enable and lock access to hash functions within modules, leading to potential unauthorized access and data security breaches.

Innovation Solution

A method and security card configuration that includes a lock bit to secure hash functions by setting it during installation, ensuring irreversible locking and preventing further access, thereby enhancing data security within information handling systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If hash functions are made accessible within modules for data processing, then data processing capability is improved, but security against unauthorized access deteriorates

Engineering Contradiction:

Improvedata processing capabilityVSAvoidunauthorized access

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by setting the lock bit during module installation or initialization, before any hash function operations occur. This ensures that security measures are in place prior to data processing, preventing unauthorized access while allowing legitimate processing to proceed.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The lock bit serves as an intermediary mechanism between the hash function and access requests. It mediates access control by providing a controllable barrier that can be set during installation to either allow or prevent access to the hash function, thus securing the processing capability while blocking unauthorized use.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If access control mechanisms are implemented for hash functions, then security is improved, but system complexity increases

Engineering Contradiction:

ImprovesecurityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent changes a single parameter (the lock bit state) to control access to the hash function. By toggling this binary parameter during installation, the system achieves robust security control without introducing complex access management structures, keeping the overall system complexity low while maintaining high reliability.

Inventive Principle:

Principle #35Parameter changes

3Object-affected harmful factors

If lock bits are set during installation to secure hash functions, then security against unauthorized access is improved, but flexibility for future access modifications deteriorates

Engineering Contradiction:

Improveunauthorized access preventionVSAvoidaccess modification flexibility

Core Design Contradiction:

Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The lock bit is configured during installation or initialization before the module enters operational use. This preliminary configuration establishes the security state that will persist throughout the module's operational life, preventing unauthorized access while maintaining the intended level of flexibility for legitimate access modifications during the design phase.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS8898445B2System and method of enabling a function within a module configured to be used within an information handling system

Publication Date: 2014.11.25 DELL SOFTWARE INC

AI summary

A system and method of enabling a function within a module configured to be used with an information handling system is disclosed. In one form, the method of enabling functions includes detecting whether to install a custom install routine within a module configured to enable access to a hash function, and accessing a lock bit configured to lock access to the hash function. The method can further include detecting whether to set the lock bit to lock access to the hash function.