Containerized Service Updates for Automated Compliance Resolution

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 container orchestration platforms, and integrating continuous integration and deployment pipelines 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 improved, but time consumption and resource usage increase significantly

Engineering Contradiction:
Improvesoftware security and complianceVSAvoidtime for compliance checks and updates
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service by having the compliance management system automatically check compliance status, generate update templates, and deploy updates across repositories without requiring manual intervention from developers or security teams for each individual repository

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by proactively scanning all repositories for compliance status and pre-generating update templates before vulnerabilities are exploited, allowing updates to be deployed automatically when compliance checks fail

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If manual code cloning and pull request generation is performed for each repository, then update accuracy is improved, but computational resources and developer hours increase

Engineering Contradiction:
Improveupdate accuracyVSAvoidupdate deployment efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system uses copying by creating a standardized update template that can be replicated across multiple repositories. Instead of manually cloning and modifying code for each repository, the same validated template is applied to all repositories that require updates, maintaining accuracy while improving efficiency

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The update template serves multiple functions simultaneously: it provides the updated code, includes compliance check results, contains deployment instructions, and can be applied across all repositories. This universal template eliminates the need for separate manual update processes for each repository

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

3Ease of manufacture

If local machine cloning of repositories is performed, then update implementation is improved, but memory consumption increases

Engineering Contradiction:
Improveupdate implementationVSAvoidmemory consumption
Core Design Contradiction:
Ease of manufactureVSQuantity of substance

Solution Approach 1:

The system introduces a cloud-based compliance management system as an intermediary between the update source and local repositories. This intermediary handles the heavy lifting of template generation, compliance checking, and update coordination, allowing local machines to participate in updates without needing to clone entire repositories, thus reducing memory requirements

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260079741A1Systems and methods for resolving compliance checks and updates
Publication Date: 2026.03.19 PNC FINANCIAL SERVICES GROUP INC
  • US20260079741A1 patent drawing
  • US20260079741A1 patent drawing
  • US20260079741A1 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.