Encrypted Container Image Layering for Cloud Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software container technologies lack robust security measures, allowing privileged administrators to access and understand the contents of software containers, which compromises data and application security, especially in cloud computing environments.

Innovation Solution

A method and system for creating a secure software container by transforming layered images into encrypted volumes with incremental differences, where each block is encrypted and stored with unencrypted metadata for rebuilding, ensuring confidentiality and secure execution even in untrusted environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is encrypted while transmitting and storing, then data security is improved, but data processing accessibility by cloud administrators is worsened

Engineering Contradiction:
Improvedata securityVSAvoiddata processing accessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The container image is divided into multiple layers, with each layer independently encrypted. This segmentation allows selective decryption and processing of specific layers while maintaining security of others, resolving the contradiction between security and accessibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different encryption approaches are applied to different parts of the container structure. Metadata remains unencrypted for accessibility, while data blocks are encrypted for security. This local differentiation resolves the contradiction by applying appropriate security measures only where needed.

Inventive Principle:
Principle #3Local quality

2Reliability

If virtual machines are used with complete operating system overhead, then security isolation is improved, but resource efficiency is worsened

Engineering Contradiction:
Improvesecurity isolationVSAvoidresource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The invention extracts the essential security isolation mechanisms from complete virtual machines, implementing them at the container level through encrypted layer structures. This removes unnecessary operating system overhead while preserving security isolation benefits.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Security isolation is moved from the traditional vertical dimension of full virtual machines to a new dimension of encrypted container layers. This dimensional shift enables security at the container level without requiring complete OS virtualization overhead.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If all files in container layers are encrypted, then security is improved, but metadata accessibility for rebuilding container order is worsened

Engineering Contradiction:
ImprovesecurityVSAvoidmetadata accessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Metadata is deliberately left unencrypted while data blocks are encrypted. This local quality differentiation ensures that metadata remains accessible for container rebuilding and management operations, while security is maintained on the actual data content.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

Metadata acts as an intermediary between the encrypted data blocks and the container management system. It provides the necessary information for rebuilding container structure without requiring decryption, thus mediating between security and operational accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11475138B2Creation and execution of secure containers
Publication Date: 2022.10.18 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11475138B2 patent drawing
  • US11475138B2 patent drawing
  • US11475138B2 patent drawing

AI summary

A computer-implemented method for creating a secure software container. The method comprises providing a first layered software container image, transforming all files, except corresponding metadata, of each layer of the first layered software container image into a volume, the volume comprises a set of blocks, wherein each layer comprises an incremental difference to a next lower layer, encrypting each block of the set of blocks of a portion of the layers, and storing each encrypted set of the blocks as a layer of an encrypted container image along with unencrypted metadata for rebuilding an order of the set of blocks equal to an order of the first layered software container image, so that a secure encrypted software container is created.