Data Traffic Manager for Server Interconnect Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-tenant compute service systems, maintaining a secure execution environment for clients is challenging due to performance degradation caused by the hypervisor layer and the risk of clients modifying firmware to compromise other users' data when renting servers, which can lead to security breaches and resource contention issues.

Innovation Solution

A data traffic manager is introduced to control data traffic between internal server components, using bridge circuits and control logic to enforce access policies, allowing or blocking transactions based on pre-determined rules, and supporting modes like filtering, pass-through, and disabled to manage access to non-volatile memory and hardware interconnects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a hypervisor layer is introduced to provide secure environments for multiple clients, then security and isolation are improved, but performance degradation occurs

Engineering Contradiction:
ImprovesecurityVSAvoidperformance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces a data traffic manager as an intermediary component that sits between the hypervisor and the hardware resources. This traffic manager enforces access control policies and manages data flow without requiring deep modifications to the hypervisor architecture, thereby maintaining security while reducing the performance overhead associated with traditional hypervisor-based isolation mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If clients are allowed direct access to hardware resources, then performance is improved, but security risks increase due to potential firmware modification

Engineering Contradiction:
ImproveperformanceVSAvoidsecurity risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The data traffic manager serves as a mediator between client virtual machines and hardware resources. It intercepts and validates access requests, enforcing security policies while allowing legitimate performance-critical operations. This prevents direct client access to firmware and hardware, eliminating the security risk of unauthorized modification while maintaining efficient data flow for authorized operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the hardware access path by introducing multiple traffic managers at different levels (host-level and VM-level). This segmentation allows fine-grained control over which VMs can access which hardware resources, enabling performance optimization for authorized access while blocking unauthorized firmware modification attempts.

Inventive Principle:
Principle #1Segmentation

3Productivity

If multiple clients share server resources, then resource utilization is improved, but resource contention and interference between clients occur

Engineering Contradiction:
Improveresource utilizationVSAvoidresource contention
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The patent implements segmentation at multiple levels by deploying traffic managers both at the host level and within individual VMs. This multi-level segmentation creates isolated data flow paths for different clients, allowing efficient shared resource utilization while preventing resource contention and interference between tenants through enforced access control policies.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10810036B1Traffic management on an interconnect
Publication Date: 2020.10.20 AMAZON TECH INC
  • US10810036B1 patent drawing
  • US10810036B1 patent drawing
  • US10810036B1 patent drawing

AI summary

Disclosed herein are techniques for maintaining a secure execution environment on a server. In one embodiment, the server includes a bus manager circuit. The bus manager circuit comprises a first bus interface configured to be coupled with a first hardware device of the server, and a second bus interface configured to be coupled with a second hardware device of the sever. The bus manager further includes a control module. Under a first mode of operation, the control module is configured to receive an access request from the first hardware device to access the second hardware device, and responsive to determining not to grant the access request based on a pre-determined access policy, and block at least some of data bits corresponding to the access request from the second bus interface. The control module may also process the access request in a different manner under other modes of operations.