Container Validation Service for Code Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In containerized software development environments, code releases are slowed down by the need for continuous human intervention and are vulnerable to malicious microservices that can compromise the integrity of containers, leading to potential security threats.

Innovation Solution

A release bot creates a union container object (pod) with an enterprise-certified microservice for validation, which generates and transmits validation data to a validation service, ensuring secure code integrity by isolating the validation process from developers and detecting anomalies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual verification and monitoring of application code is performed, then security and code integrity can be ensured, but the code release process is slowed down and requires continuous human intervention

Engineering Contradiction:
Improvecode integrityVSAvoidrelease time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by embedding validation services and monitoring agents into the containerization process itself. Code verification, security scanning, and integrity checks are performed automatically during the build and deployment stages, before the application goes live. This eliminates the need for continuous manual intervention after release, as the system proactively validates code at each stage of the CI/CD pipeline.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service through automated validation services that continuously monitor and verify application code without human intervention. These services automatically detect anomalies, validate code integrity, and enforce security policies. The containerized environment includes built-in monitoring agents that autonomously track code changes and validate compliance, replacing manual verification processes with self-executing validation mechanisms.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If developers have full access to containerized applications, then development flexibility is improved, but the system becomes vulnerable to malicious microservices that can compromise container integrity

Engineering Contradiction:
Improvedevelopment flexibilityVSAvoidsecurity threats
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces intermediary validation services and monitoring agents that act as mediators between developers and the containerized application environment. These intermediaries enforce security policies, validate code changes, and monitor for malicious activities without restricting developer access. The validation services serve as a protective layer that allows flexible development while automatically detecting and preventing security threats from malicious microservices.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system applies preliminary anti-action by implementing proactive security measures that prevent malicious actions before they can compromise container integrity. Validation services scan and verify code before deployment, and monitoring agents continuously detect suspicious behaviors. This preemptive approach counters potential security threats by establishing defensive mechanisms in advance, allowing developers to maintain flexibility while the system automatically neutralizes security risks.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS10666443B2Continued verification and monitoring of application code in containerized execution environment
Publication Date: 2020.05.26 RED HAT INC
  • US10666443B2 patent drawing
  • US10666443B2 patent drawing
  • US10666443B2 patent drawing

AI summary

A method includes receiving, by a processing device executing a validation service, a validation data associated with a first instance of an execution environment, the validation data provided by a publication service associated with a second instance of the execution environment, acquiring a decryption key from a release server associated with the execution environment, determining, using the decryption key, a validation status associated with the first instance in view of the validation data, and notifying the release server of the validation status.