Abstract: A method for binding applications to a platform root of trust includes pre-provisioning application binding components in an information handling system. An application requesting OS access sends its access control list (ACL) and application metadata to the BIOS, which performs initial checks. The BIOS responds with platform metadata and a first nonce. The application communicates the metadata, the first nonce and a second nonce to a server. The server checks the nonces and metadata, creates a third nonce and an application binding object (ABO). The application checks the nonces and sends a binding certificate to the BIOS. The BIOS checks the nonces, creates a binding certificate, verifies the binding certificate and sends a binding session credential (BSC) to the application. The application binds the BSC with platform credentials.

Abstract: A method for binding applications to a platform root of trust includes pre-provisioning application binding components in an information handling system. An application requesting OS access sends its access control list (ACL)and application metadata to the BIOS, which performs initial checks. The BIOS responds with platform metadata and a first nonce. The application communicates the metadata, the first nonce and a second nonce to a server. The server checks the nonces and metadata, creates a third nonce and an application binding object (ABO). The application checks the nonces and sends a binding certificate to the BIOS. The BIOS checks the nonces, creates a binding certificate, verifies the binding certificate and sends a binding session credential (BSC) to the application. The application binds the BSC with platform credentials.

Abstract: A power profile diagnostic system includes a power rail. At least one subsystem is coupled to the power rail. A controller is coupled to the power rail and to a power profile database. The controller is configured to monitor the power rail and determine a power consumption profile of the at least one subsystem during a predefined operation of the at least one subsystem. The controller then compares the power consumption profile to a predetermined power profile that is stored in the power profile database in association with the predefined operation, and determines whether a difference between the predetermined power profile and the power consumption profile is indicative of a malfunction of the at least one subsystem. If the difference between the predetermined power profile and the power consumption profile is indicative of the malfunction of the at least one subsystem, the controller provide a malfunction report for display.

Abstract: A power profile diagnostic system includes a power rail. At least one subsystem is coupled to the power rail. A controller is coupled to the power rail and to a power profile database. The controller is configured to monitor the power rail and determine a power consumption profile of the at least one subsystem during a predefined operation of the at least one subsystem. The controller then compares the power consumption profile to a predetermined power profile that is stored in the power profile database in association with the predefined operation, and determines whether a difference between the predetermined power profile and the power consumption profile is indicative of a malfunction of the at least one subsystem. If the difference between the predetermined power profile and the power consumption profile is indicative of the malfunction of the at least one subsystem, the controller provide a malfunction report for display.

Abstract: An error injection tool, connected to a bus to be tested in such a manner as not to interfere with normal operation, is employed for error detection and recovery design verification. The error injection tool is connected to the bus to be tested within a data processing system, the system is powered on, and applications simulating normal system loading are run. A desired error is then selected, and the error injection tool is actuated. The error injection tool monitors bus cycles and transactions through selected signals and, upon detecting an appropriate cycle or transaction, overdrives a selected conductor within the bus being tested to inject an error. The selected bus conductor is overdriven (forced) to a logic high or a logic low for a single clock cycle, simulating the intermittent nature of errors likely to occur during normal operation. Bus error signals are then monitored to ascertain whether the error was successfully injected.