Policy Enforcement Proxy for Container Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application container technologies lack sufficient security measures to manage the dynamic deployment of applications across various computing systems, leading to potential security risks when low-security and high-security applications are run simultaneously or transferred between servers.

Innovation Solution

Implementing a policy-enforcement proxy that authenticates application containers based on trustworthiness thresholds, intercepts and modifies deployment commands to ensure compliance with security policies, preventing potential violations by transferring or canceling actions that violate security policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional security measures are used to manage application containers, then security management is simple, but security effectiveness is insufficient due to inability to handle dynamic deployment scenarios

Engineering Contradiction:
Improvesecurity effectivenessVSAvoidsecurity management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a policy enforcement proxy as an intermediary component between application containers and the host computing system. This proxy intercepts deployment commands, authenticates containers against security policies, and enforces trustworthiness thresholds. The intermediary handles the complexity of security management centrally, allowing simple container deployment while maintaining strong security controls through the proxy's mediation layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary authentication and security policy verification before allowing application container deployment. The policy enforcement proxy checks container trustworthiness, validates security policies, and authenticates containers in advance of deployment. This preliminary action ensures security requirements are met before containers are launched, preventing security issues rather than reacting to them.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If application containers are allowed to deploy freely across servers, then deployment flexibility is high, but security risks increase when low-security containers access high-security resources

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements local quality by assigning different security policies and trustworthiness thresholds to different deployment contexts and container types. The policy enforcement proxy evaluates each container individually against relevant security policies, allowing low-security containers to deploy to appropriate servers while preventing them from accessing high-security resources. Each container receives security treatment tailored to its specific trust level and destination.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system changes security parameters dynamically based on container authentication results. The policy enforcement proxy adjusts deployment permissions, resource access levels, and security constraints according to the authenticated trustworthiness of each container. Containers with higher trust levels gain broader access while maintaining deployment flexibility, whereas lower-trust containers face restricted permissions.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If security policies are enforced strictly on all deployment commands, then security compliance is improved, but deployment speed decreases due to command interception and modification

Engineering Contradiction:
Improvesecurity complianceVSAvoiddeployment speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The policy enforcement proxy applies partial action by selectively intercepting and enforcing security policies only on deployment commands that require authentication or policy verification. Routine deployment commands that already meet security requirements proceed without full interception overhead. This partial enforcement maintains security compliance while reducing the performance impact on legitimate deployment operations.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9729579B1Systems and methods for increasing security on computing systems that launch application containers
Publication Date: 2017.08.08 GEN DIGITAL INC
  • US9729579B1 patent drawing
  • US9729579B1 patent drawing
  • US9729579B1 patent drawing

AI summary

A computer-implemented method for increasing security on computing systems that launch application containers may include (1) authenticating an application container that facilitates launching at least one application on a host computing system by verifying that the application container meets a certain trustworthiness threshold, (2) intercepting, via a policy-enforcement proxy, a command to perform a deployment action on the host computing system in connection with the authenticated application container, (3) determining that the deployment action potentially violates a security policy applied to the authenticated application container, and then in response to determining that the deployment action potentially violates the security policy, (4) modifying, via the policy-enforcement proxy, the command to prevent the potential violation of the security policy. Various other methods, systems, and computer-readable media are also disclosed.