Container Service Template Deployment for Automated Compliance Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for managing software updates are inefficient, resource-intensive, and prone to vulnerabilities, particularly in institutions with thousands of repositories, leading to increased exposure to malware, data breaches, and system crashes.

Innovation Solution

A system and method for automatically resolving compliance checks and updates by generating templates based on updated code, deploying them through a container orchestration platform, and integrating a continuous integration and deployment pipeline to ensure software services are up-to-date and secure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual compliance checks and updates are performed for each repository, then software security and compliance are maintained, but time consumption and resource usage increase significantly

Engineering Contradiction:
Improvesoftware security and complianceVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically detecting vulnerabilities and generating update templates before manual intervention is needed. The compliance check system proactively identifies security issues and prepares update strategies in advance, allowing rapid response when updates are required.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service through automated compliance checking and update generation. The platform automatically detects vulnerabilities, generates templates, and creates pull requests without requiring manual intervention for each repository, allowing the system to maintain itself across thousands of repositories.

Inventive Principle:
Principle #25Self-service

2Reliability

If manual code updates are performed for each repository, then compliance is ensured, but developer hours and operational costs increase

Engineering Contradiction:
Improvecompliance assuranceVSAvoiddeveloper efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system uses copying by generating templates that replicate successful update patterns across multiple repositories. Instead of manually updating each repository individually, the system copies proven update strategies and applies them automatically, significantly reducing developer workload.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The compliance check system serves multiple functions simultaneously: it detects vulnerabilities, generates templates, creates pull requests, and tracks compliance status across all repositories. This multi-functional approach consolidates what would otherwise require multiple manual processes into a single automated system.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of manufacture

If repositories are cloned and updated locally, then updates can be applied, but memory and computational resources are consumed

Engineering Contradiction:
Improveupdate applicabilityVSAvoidcomputational resource usage
Core Design Contradiction:
Ease of manufactureVSUse of energy by moving object

Solution Approach 1:

The system introduces an intermediary template repository that stores generated update templates before they are applied to actual repositories. This intermediate layer allows updates to be prepared and validated without requiring full cloning of repositories, reducing computational resource consumption while maintaining update applicability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260056767A1Systems and methods for resolving compliance checks and updates
Publication Date: 2026.02.26 PNC FINANCIAL SERVICES GROUP INC
  • US20260056767A1 patent drawing
  • US20260056767A1 patent drawing
  • US20260056767A1 patent drawing

AI summary

Disclosed herein are systems and methods for building and deploying containerized software services during software development. The disclosed embodiments involve accessing code from a code repository corresponding to a software service. The disclosed embodiments involve generating a template for the software service based on the code. The disclosed embodiments involve storing the template in a template repository and detecting a vulnerability in the code. In some embodiments, responsive to detecting the vulnerability in the code, the disclosed embodiments involve updating the code to mitigate the vulnerability, generating an updated template based on the updated code, deploying the updated template to a container orchestration platform, and generating an instance of the software service with the container orchestration platform based on the updated template.