Hard Drive Protection Using Obfuscated Boot Passwords
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Transaction terminal hard drives, particularly in ATMs, are vulnerable to theft due to the value of their data and physical security threats, with existing security measures like manual password entry and whole disk encryption being cumbersome and costly.
Innovation Solution
Implementing a boot firmware that sets and obfuscates a password for the hard drive, either standalone or online, ensuring the password is never stored on the drive, and auto-fills it during boots, using either local storage or server authentication for secure unlocking.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual password entry is used to lock the hard drive, then the hard drive can be protected from theft, but the operation becomes cumbersome and time-consuming
Solution Approach 1:
The boot firmware performs preliminary action by automatically retrieving and applying the password during the boot process before the user needs to access the hard drive. This eliminates the need for manual password entry at the time of access, as the password is already in place from the preliminary boot firmware action.
Solution Approach 2:
The boot firmware acts as an intermediary between the user and the hard drive password mechanism. Instead of requiring direct manual password entry, the boot firmware mediates by automatically handling the password retrieval and application process, thereby simplifying user interaction while maintaining security.
2Reliability
If whole disk encryption is implemented, then the hard drive security is improved, but the cost and complexity increase
Solution Approach 1:
The invention extracts the password protection function from the hard drive itself and places it in the boot firmware. By taking out the password storage requirement from the drive, the system achieves security without requiring complex whole disk encryption mechanisms, thereby reducing overall system complexity while maintaining protection.
Solution Approach 2:
The system uses a simple, inexpensive password mechanism stored in boot firmware variables rather than implementing costly whole disk encryption. The password is applied temporarily during boot and then discarded, providing sufficient security without the complexity and cost of permanent encryption schemes.
3Ease of operation
If the password is stored on the hard drive, then the drive can be unlocked easily, but the security is compromised as the drive alone can provide the password
Solution Approach 1:
The boot firmware serves as an intermediary that holds the password temporarily during the boot process. It retrieves the password from boot firmware variables, applies it to unlock the hard drive, and then discards the password. This intermediary approach ensures the drive cannot be unlocked without the boot firmware's involvement, preventing theft while maintaining easy access for authorized users.
Solution Approach 2:
The boot firmware performs the preliminary action of retrieving and applying the password before the hard drive needs to be accessed. This preliminary retrieval from boot firmware variables and subsequent application ensures the drive is unlocked easily when needed, while the password is not stored on the drive itself, maintaining anti-theft protection.
4Reliability
If remote server authentication is used, then the security is enhanced, but the system complexity and dependency increase
Solution Approach 1:
The system implements partial authentication by using boot firmware variables to store authentication information locally rather than requiring continuous remote server communication. This partial action provides sufficient security for the boot process without the excessive complexity of always-online authentication, balancing security enhancement with system simplicity.
Data Source
AI summary
Boot firmware of a terminal sets a lock password on a hard disk drive of the terminal to lock the hard disk drive from access. The password is obfuscated in boot variables or stored separately on a server independently of the terminal. During subsequent boots of the terminal, the firmware de-obfuscates the password from the boot variables or obtains the password from the server and provides the password to the hard disk drive, which causes the hard disk drive to unlock for operation with the terminal following the subsequent boots.