Secure Kernel Launch in Multiprocessor Systems via Trusted Agent Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In computer systems with link-based topologies, ensuring a trusted environment for secure operations is challenging due to untrusted software configurations that can lead to memory aliasing and configuration errors, making it difficult to validate memory access correctly at the outset of system operation.

Innovation Solution

A secure kernel is launched across all processors using a trusted hardware chain, with a trusted software agent executed to validate the system configuration, and a spanning tree protocol is used to ensure all nodes are properly configured and communicate securely, allowing for the recording of a trusted environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a protocol is used to access memory with address decoding and routing mechanisms configured by software, then memory access flexibility is improved, but trustworthiness and reliability deteriorate due to untrusted software configuration

Engineering Contradiction:
Improvememory access flexibilityVSAvoidtrustworthiness of memory access
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system divides memory access into two distinct phases: a trusted setup phase where address decoding and routing are validated by a trusted agent, and an operational phase where the protocol executes. This segmentation allows flexible software configuration while ensuring reliability through separate validation, resolving the contradiction between adaptability and trustworthiness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The trusted agent performs preliminary validation of address decoding and routing mechanisms before the protocol begins memory access operations. By pre-validating the configuration, the system ensures that subsequent memory accesses are trustworthy while maintaining the flexibility of software-configurable protocols.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If hardware mechanisms and link controllers are trusted to behave as specified, then system simplicity is improved, but the ability to detect and measure configuration errors deteriorates

Engineering Contradiction:
Improvesystem simplicityVSAvoidconfiguration error detection
Core Design Contradiction:
Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The trusted agent serves as an intermediary between the hardware mechanisms and the protocol. It validates hardware configurations and link controller behaviors without adding significant system complexity, while enabling detection of configuration errors that would otherwise be undetectable in a trusted hardware model.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The trusted agent provides feedback about the validity of hardware configurations and routing mechanisms. This feedback mechanism enables detection of configuration errors while maintaining relatively simple hardware that can be trusted to behave as specified, resolving the contradiction between simplicity and error detection capability.

Inventive Principle:
Principle #23Feedback

3Reliability

If a trusted environment is established through validation of all hardware and software components, then security and reliability are improved, but system complexity and initialization time increase

Engineering Contradiction:
Improvesecurity of trusted environmentVSAvoidvalidation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The trusted agent is extracted as a separate, dedicated component responsible for validation, rather than distributing validation logic throughout the entire system. This extraction concentrates the complexity of trusted environment establishment in a single manageable entity, improving security while controlling overall system complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The trusted agent performs multiple validation functions including verifying address decoding, validating routing mechanisms, and authenticating the protocol. By consolidating these diverse validation tasks into a single multi-functional component, the system achieves comprehensive security without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If address decoding and routing are configured by untrusted software, then system adaptability is improved, but the risk of configuration errors and memory aliases increases

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidconfiguration errors and memory aliases
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The trusted agent performs preliminary validation of address decoding and routing configurations before the protocol uses them, preventing configuration errors and memory aliases from affecting system operation. This preliminary anti-action allows flexible software configuration while neutralizing the harmful effects of potential errors.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS7698552B2Launching a secure kernel in a multiprocessor system
Publication Date: 2010.04.13 INTEL CORP
  • US7698552B2 patent drawing
  • US7698552B2 patent drawing
  • US7698552B2 patent drawing

AI summary

In one embodiment of the present invention, a method includes verifying an initiating logical processor of a system; validating a trusted agent with the initiating logical processor if the initiating logical processor is verified; and launching the trusted agent on a plurality of processors of the system if the trusted agent is validated. After execution of such a trusted agent, a secure kernel may then be launched, in certain embodiments. The system may be a multiprocessor server system having a partially or fully connected topology with arbitrary point-to-point interconnects, for example.