In-Band Log Authentication Using BIOS-Signed Secondary Messages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenant resource environments, unauthenticated system event logs can be sent by a host operating system, leading to potential denial-of-service attacks and costly manual maintenance, as attackers can trigger false alerts or resend valid logs.
Innovation Solution
Implementing a secondary message authentication mechanism using a secret key, such as an HMAC-based signature, to verify the authenticity of system event logs, ensuring only the BIOS can generate valid secondary messages, thus preventing unauthorized access and attacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If system event logs are sent without authentication, then communication simplicity is maintained, but system security and reliability deteriorate due to unauthorized access and denial-of-service attacks
Solution Approach 1:
A secondary message containing authentication data (HMAC signature) is introduced as an intermediary element between the primary system event log message and the verification process. This intermediary carries the cryptographic proof needed to authenticate the message source without complicating the core communication protocol, as the authentication happens in a separate verification layer.
Solution Approach 2:
The authentication mechanism performs preliminary verification by checking the HMAC signature against the primary message content before processing the system event log. This preliminary action ensures that only authenticated messages from authorized sources (BIOS or management controller) are accepted, preventing unauthorized access and attacks before they can impact system reliability.
2Reliability
If authentication mechanisms are implemented, then system security is improved, but processing time and operational complexity increase
Solution Approach 1:
The patent replaces complex cryptographic verification mechanics with a simplified comparison operation. Instead of performing full cryptographic validation, the system substitutes the primary message with the secondary message content and compares them directly. This substitution approach maintains security while dramatically reducing processing time and computational overhead.
Solution Approach 2:
The authentication approach changes the verification parameter from complex cryptographic computation to simple content comparison. By transforming the verification task into a straightforward string comparison between the primary and secondary messages, the system achieves fast authentication with minimal time loss while maintaining message authenticity guarantees.
3Reliability
If existing communication protocols are modified to include authentication, then security is improved, but protocol compatibility and ease of operation deteriorate
Solution Approach 1:
The patent adds authentication to the communication protocol by introducing a new dimension - a secondary message layer that operates parallel to the primary message exchange. This dimensional addition allows authentication capability to be layered on top of existing protocols without modifying their core structure, maintaining backward compatibility while enabling security enhancements.
Solution Approach 2:
The secondary message mechanism serves multiple functions: it provides authentication verification, prevents denial-of-service attacks, and maintains compatibility with existing communication protocols. This multi-functional approach allows a single mechanism to address various security concerns while preserving ease of operation and protocol compatibility across different system configurations.
Data Source
AI summary
Communications, such as system event log messages, can be authenticated using a secondary message, as may be sent over a common channel. Each secondary message can be a copy of a corresponding primary message signed with a hash, where that hash can be generated using a secret, such as a secret key. In some embodiments, the secret can be stored in BIOS where the messages are generated, such that an operating system executing on a computing device cannot access the secret in order to send valid secondary messages that match content of the corresponding first messages.