UEFI Boot Blocking Using Authenticated Remote Tickets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer blocking methods are limited in protecting systems beyond the operating system, rely on real-time clock integrity, and lack robustness against unauthorized unblocking attempts, especially in scenarios involving theft or non-compliance with contractual conditions.
Innovation Solution
A computer blocking system embedded in fundamental and non-modifiable components of computer systems, utilizing a boot control module within software/firmware chips, which operates independently of the operating system and makes autonomous decisions based on pre-defined parameters, using tickets authenticated by a remote server to control boot authorization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software-based blocking solutions are used, then the system can be remotely located and blocked, but an attacker can completely remove the software by replacing or formatting the hard drive
Solution Approach 1:
The blocking system is segmented into multiple layers: firmware-level boot control module embedded in non-modifiable components, operating system-level agent, and remote server. The critical blocking function is isolated to the firmware layer, which cannot be easily removed or modified, while the OS-level agent handles communication. This segmentation ensures that even if the OS is reformatted, the firmware-level blocking control remains intact.
Solution Approach 2:
The boot control module executes preliminary actions during the boot process before the operating system loads. It verifies tickets and makes blocking decisions at the firmware level during system initialization, preventing the system from booting if authorization is invalid. This preliminary action occurs before any user-level software can interfere or be removed.
2Reliability
If TPM physical chip technology is used, then laptop tracking and data protection are provided, but the tracking precision is low due to IP address sharing and the cipher key becomes inaccessible when blocked
Solution Approach 1:
The system moves the blocking control from the application/OS layer to the firmware/boot layer, adding a new dimensional layer of protection. The boot control module operates at a fundamental system level below the OS, creating a hierarchical structure where firmware-level ticket verification provides robust protection independent of OS integrity or network location tracking precision.
3Productivity
If boot control solutions with time limits are used, then the system can enforce usage time restrictions, but protection against real-time clock manipulations is required which consumes more memory resources
Solution Approach 1:
The ticket serves as an intermediary that encapsulates all necessary authorization information including time limits, usage counters, and conditions. Instead of implementing complex real-time clock verification logic that consumes memory, the system uses the pre-validated ticket as a mediator that already contains the trusted time-based authorization data, eliminating the need for extensive memory-based time validation routines.
Data Source
AI summary
The present document discloses a method and system for blocking a computer system based on tickets issued by a remote server, with an operating system configured for booting from a UEFI, wherein the blocking system comprises: a transfer engine, i.e. an agent, of tickets comprised in an application or module of the operating system; an authentication engine comprised in said UEFI; a data or file transfer area accessible by both engines; wherein the transfer engine is configured for receiving tickets and storing tickets; wherein the authentication engine is configured for: reading a stored ticket; checking authentication and obtaining read ticket type; and if the authenticity is verified, processing the verified ticket, depending on the type: a normal ticket, setting the system to a leased state wherein the operating system can start; or a block ticket, setting the system to a blocked state wherein the operating system cannot boot.