BIOS Field Mapping via Hidden Namespace Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing BIOS field mapping in information handling systems lacks security, as it exposes setup data to unauthorized access due to its reliance on the Variable Services protocol, which is exposed to the operating system and other executing code.
Innovation Solution
The proposed solution involves generating BIOS information using a visual form code language to define property identifications, converting it to a binary format, and storing these identifications in a setup database hidden from the operating system, allowing only authorized access through a proprietary setup service, thereby using Property Services instead of Variable Services for data storage and retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If Variable Services protocol is used to store setup data, then data accessibility is improved, but security deteriorates
Solution Approach 1:
The patent segments the data storage system by creating separate namespaces: a hidden namespace for secure BIOS setup data and a visible namespace for accessible data. This segmentation isolates sensitive setup variables from the operating system and unauthorized code while maintaining accessibility through the Variable Services protocol for authorized components.
Solution Approach 2:
The patent introduces an intermediary mechanism (the hidden namespace with restricted access protocols) between the setup data and the operating system. This intermediary controls and filters access requests, allowing only authorized BIOS components to access setup data while blocking unauthorized access from the OS and other code.
2Device complexity
If monolithic system configuration structure is used, then implementation simplicity is improved, but security deteriorates
Solution Approach 1:
The patent divides the monolithic system configuration structure into separate namespaces within the Variable Services data store. The hidden namespace contains secure BIOS setup variables, while other namespaces contain accessible configuration data. This segmentation maintains the simplicity of using a single data store while preventing data exposure through namespace isolation.
3Ease of operation
If setup data is exposed to operating system, then runtime accessibility is improved, but security deteriorates
Solution Approach 1:
The patent segments the Variable Services data store into hidden and visible namespaces, allowing the operating system to access visible data while setup data remains isolated in the hidden namespace. This enables runtime accessibility for non-sensitive data while protecting sensitive setup variables from OS access.
Solution Approach 2:
The patent introduces access control mechanisms as intermediaries that mediate between the operating system and the hidden namespace. These intermediaries enforce security policies, allowing runtime accessibility only for authorized BIOS components while blocking OS access to sensitive setup data.
Data Source
AI summary
BIOS field mapping includes generating basic input/output system (BIOS) information by defining property identifications using a visual form code language and determining that a proprietary set-up service is accessible. The BIOS field mapping then includes converting the visual form code language to a binary format and storing the property identifications in binary format on a setup database as data hidden from an operating system. A BIOS driver may then request the property identifications causing a transfer of the property identifications to the BIOS driver.