Container Security Policy Generation From Static Binary Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current security policy tools for container orchestration systems like Kubernetes and OpenShift require manual effort to set privilege constraints, often resulting in overly permissive policies that violate the principle of least privilege, posing a security risk.

Innovation Solution

Automated static analysis of containerized application binary code to generate a control-flow graph and infer security policy configurations that adhere to the principle of least privilege, ensuring only necessary access and permissions for proper application execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual security policy configuration is used, then ease of operation is improved, but security strength deteriorates due to overly permissive policies

Engineering Contradiction:
Improveease of policy configurationVSAvoidsecurity policy strength
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs self-service by automatically analyzing container binary code and generating security policies without requiring manual intervention. The automated static analysis tool examines the binary code, constructs control-flow graphs, and infers the minimum necessary security policies, eliminating the need for users to manually configure policies while ensuring security strength through algorithmic derivation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes the parameter of policy generation from manual configuration to automated inference. By transforming the policy creation process into an automated analysis that infers parameters from binary code execution paths, the system achieves both ease of operation (no manual config needed) and security strength (precise least-privilege policies).

Inventive Principle:
Principle #35Parameter changes

2Productivity

If automated security policy generation is implemented, then productivity is improved, but device complexity increases

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system replaces the mechanical process of manual policy configuration with an automated computational analysis. By using static analysis of binary code and control-flow graph construction, the system substitutes human expertise with algorithmic processing, achieving automated policy generation that improves productivity while managing complexity through standardized analysis procedures.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system performs preliminary action by analyzing container binary code before deployment to automatically generate security policies. This advance analysis and policy inference occurs during the build or deployment phase, eliminating the need for manual policy configuration at runtime and improving deployment efficiency through automated preparation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12587568B2Generation of security policies for container execution
Publication Date: 2026.03.24 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12587568B2 patent drawing
  • US12587568B2 patent drawing
  • US12587568B2 patent drawing

AI summary

Automated generation of security policies for container execution includes performing automated static analysis of binary code of a containerized application and generating, based on the static analysis, a control-flow graph of expected runtime execution flow of the containerized application, the containerized application providing an expected set of functionality when properly executing, inferring, from the expected runtime execution flow of the containerized application, security policy configurations for a plurality of resources used in execution of the containerized application and that suffice for the containerized application to provide the expected set of functionality, and automatically generating, as part of configuration file(s) used in deploying a container having the containerized application for execution, a security policy for execution of the container including the containerized application thereof, the security policy specifying the security policy configurations for the plurality of resources used in the execution of the containerized application.