Firmware Anonymizer Module for Unique Identifier Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computing systems' unique identifiers generated during the boot process can be used to track user activity, even when operating-system-level privacy measures are enabled, as these identifiers remain accessible after the OS is loaded.
Innovation Solution
An anonymizer module within the firmware generates anonymized versions of firmware tables during the boot process, making these anonymized versions accessible to the operating system, thereby preventing unauthorized access to unique identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If firmware tables containing unique identifiers are made accessible to the operating system, then system identification and compatibility functions are enabled, but tracking and privacy violations occur
Solution Approach 1:
The patent introduces an anonymizer module as an intermediary between the firmware tables and the operating system. This module intercepts access requests to firmware tables and returns anonymized versions of unique identifiers (such as replacing actual serial numbers with randomly generated pseudonyms) while allowing the OS to continue functioning. The anonymizer thus mediates between the need for system identification and the need to prevent tracking.
Solution Approach 2:
The patent extracts the harmful unique identifiers from the firmware tables by creating separate anonymized copies. The anonymizer module removes or replaces specific tracking-sensitive fields (like serial numbers, MAC addresses, and processor IDs) while retaining the table structure and other non-sensitive information, allowing the OS to access modified tables without exposure to actual identifying data.
2Object-affected harmful factors
If anonymized firmware tables are provided to the operating system, then tracking is prevented, but access to original unique identifiers is lost
Solution Approach 1:
The patent segments the firmware table access into two separate pathways: one for anonymized access (available to the OS and applications) and one for original access (restricted to authorized firmware components). The anonymizer module creates and maintains separate anonymized versions of firmware tables, allowing simultaneous existence of both anonymized and original data structures with different access permissions.
Solution Approach 2:
The anonymizer module performs preliminary anonymization of firmware tables before they are made accessible to the operating system. By pre-processing the tables during the boot process or before OS access is granted, the system ensures that only anonymized data is exposed to potential trackers while the original identifiers remain protected in the firmware layer.
3Ease of operation
If firmware tables are made readable by operating system components, then standard system functionality is enabled, but privacy protection mechanisms are bypassed
Solution Approach 1:
The anonymizer module serves as a persistent intermediary layer between the firmware tables and OS components. It intercepts all read requests from the OS, applications, or web browsers attempting to access firmware tables and returns anonymized data instead of original identifiers. This intermediary layer remains active throughout OS operation, continuously protecting privacy while enabling standard OS functionality.
Data Source
AI summary
Discovery of unique identifiers in firmware can be prevented. During the boot process on a computing system, and after the firmware has generated firmware tables containing unique identifiers, an anonymizer module of the firmware can generate an anonymized version of the firmware tables and cause the anonymized version of the firmware tables, rather than the original, system-unique firmware tables, to be accessible after the operating system is loaded. In this way, once the operating system is loaded, when a module attempts to read the firmware tables, the read will be performed against the anonymized version of the firmware tables thereby preventing the module from obtaining any of the computing system's unique identifiers. A copy of the firmware tables may be maintained separately from the anonymized version of the firmware tables to enable authorized utilities to obtain the computing system's unique identifiers.