Runtime Secure Data Writing via Trusted API and Isolated Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Illicit attacks on computer systems, particularly via the Internet, pose a significant threat due to vulnerabilities in the BIOS, which can be difficult to detect and correct, and the use of less secure storage during runtime creates a vulnerability for data integrity.
Innovation Solution
Implementing an independent compute core with a secure data storage device and a trusted Application Program Interface (API) that allows secure data to be verified and written during runtime, eliminating the need for temporary storage in less secure locations like NVRAM by using a keyed-hash message authentication code (HMAC) and a shared secret for message verification and access control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If secure data is stored in less secure storage locations like NVRAM during runtime, then data can be temporarily stored, but data integrity and security are compromised
Solution Approach 1:
The patent introduces a Trusted API as an intermediary mechanism between the BIOS and secure storage. This API provides a secure channel that allows data to be written to isolated storage during runtime without compromising security. The Trusted API acts as a mediator that ensures only authenticated data is written to the secure storage location, resolving the contradiction between runtime storage capability and data integrity.
Solution Approach 2:
The patent segments the storage system into less secure storage (NVRAM) and secure isolated storage. By dividing storage into these distinct segments with different security levels, the system can use NVRAM for temporary storage during runtime while maintaining separate secure storage for integrity-critical data. This segmentation allows the system to achieve both runtime productivity and data integrity by placing data in appropriate storage segments.
2Reliability
If the BIOS is stored in dedicated memory, then security is improved, but the complexity of the system increases
Solution Approach 1:
The patent uses cryptographic hashing to create a digital copy of the BIOS for verification purposes. Instead of physically copying the BIOS to a separate location, the system creates a hash fingerprint that can be stored and compared. This copying approach allows the system to verify BIOS integrity without duplicating the entire BIOS code, thereby maintaining security while reducing storage requirements and system complexity.
Solution Approach 2:
The patent replaces physical storage mechanisms with cryptographic verification mechanisms. Instead of using physical isolation and dedicated hardware storage to protect the BIOS, the system uses cryptographic hashes and Trusted APIs to verify and protect BIOS integrity. This substitution of mechanical/storage-based security with information-theoretic security reduces hardware complexity while maintaining or improving security.
3Productivity
If a Trusted API is opened during runtime, then secure data can be written to isolated storage, but the risk of malicious code execution increases
Solution Approach 1:
The patent implements preliminary verification actions before allowing the Trusted API to be opened. The system verifies the authenticity and integrity of data and commands before granting access to the secure storage through the Trusted API. This preliminary action ensures that only legitimate, authenticated data can trigger the API opening, thereby enabling runtime data writing while preventing malware exploitation.
Solution Approach 2:
The patent incorporates feedback mechanisms that continuously monitor and verify the state of the Trusted API and the data being written. The system provides feedback loops that authenticate each writing operation and can close the API if suspicious activity is detected. This feedback mechanism allows the system to maintain runtime data writing capability while actively detecting and preventing malicious code execution attempts.
Data Source
AI summary
A computer system includes an independent compute core; and an isolated secure data storage device to store data accessible only to the independent compute core. The independent compute core is to open an Application Program Interface (API) during runtime of the computer system in response to receiving a verified message containing secure data to be written to the secure data storage device.