Containerized Code Execution With Proxy Auditing and Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software development processes allow untrusted code execution in production environments without adequate audit trails or access controls, posing security risks and compliance challenges.

Innovation Solution

Executing untrusted code within a container using a 'virtually air-gapped' environment with network traffic proxied through security proxies, enforcing access controls, and requiring multi-party approval before execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If untrusted code is executed in production environment without containerization, then code execution flexibility is improved, but security risk and lack of audit controls worsen

Engineering Contradiction:
Improvecode execution flexibilityVSAvoidsecurity risk and audit control
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the execution environment by implementing containerization, isolating untrusted code within dedicated containers that have limited access to system resources. This segmentation allows flexible code execution while containing security risks within isolated boundaries, preventing lateral movement to other system components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer between code execution and the host system through container runtimes and security proxies. This intermediary mediates all system calls and network traffic, enabling audit controls and access management while maintaining code execution flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If access controls are implemented for untrusted code, then security and audit control are improved, but device complexity and operational overhead worsen

Engineering Contradiction:
Improveaccess control and auditingVSAvoidsystem complexity and operational overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple security functions into the container runtime itself, combining execution management, isolation, and access control in a single integrated layer. This reduces overall system complexity by eliminating the need for separate security infrastructure while maintaining comprehensive audit controls.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The container runtime provides self-service security mechanisms where the system automatically enforces access controls, generates audit logs, and manages isolation without requiring external security infrastructure. This reduces operational overhead by automating security functions that would otherwise require manual configuration and monitoring.

Inventive Principle:
Principle #25Self-service

3Reliability

If network traffic is proxied through security proxies, then access control and auditing are improved, but network performance and throughput worsen

Engineering Contradiction:
Improveaccess control and auditingVSAvoidnetwork performance and throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial proxying where only specific network traffic requiring security inspection is routed through security proxies, while other traffic can bypass the proxy infrastructure. This selective approach maintains access control and auditing for critical operations while minimizing impact on overall network performance and throughput.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12511373B2Processing transactions involving card reader devices containerized execution of code
Publication Date: 2025.12.30 STRIPE LLC
  • US12511373B2 patent drawing
  • US12511373B2 patent drawing
  • US12511373B2 patent drawing

AI summary

A method and apparatus for executing code in a container are described. In one embodiment, the method comprises generating code on a host computer system using a user interface; and executing the code inside a container on the host computer system, including performing access control based on one or more properties of the host computer system.