Deployment Token Validation for Compliant Cloud Artifact Release

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud deployment systems lack a mechanism to ensure that artifacts are deployed only when customer-specific conditions, such as security, regulatory compliance, and performance requirements are met, leading to potential inconsistencies and vulnerabilities.

Innovation Solution

A system that obtains a deployment token representing verification of customer-designated conditions before deploying artifacts to a target computing environment, ensuring that these conditions are satisfied before deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a deployment verification mechanism is implemented, then security and compliance are improved, but deployment process complexity increases

Engineering Contradiction:
Improvedeployment securityVSAvoiddeployment process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a verification service as an intermediary component that mediates between the artifact deployment tool and the target computing environment. This service evaluates deployment conditions, generates verification tokens, and validates them during deployment, thereby improving security without requiring complex changes to the core deployment process. The intermediary handles the complexity of condition evaluation and token management centrally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary verification of deployment conditions before actual deployment occurs. The verification service evaluates customer-designated conditions (security, compliance, performance) in advance and generates a deployment token that represents this verification. This preliminary action ensures that only artifacts meeting all required conditions are deployed, improving reliability while keeping the deployment process straightforward through token-based validation.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If deployment conditions verification is added, then compliance and security are enhanced, but deployment time increases

Engineering Contradiction:
Improvecompliance assuranceVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The verification service performs condition evaluation and generates deployment tokens in advance, before the actual deployment process. This preliminary verification ensures that compliance and security requirements are met while allowing the actual deployment to proceed quickly using the pre-validated token. The time-consuming verification work is done beforehand, not during the critical deployment window.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The deployment token serves as a copy or representation of the verification result. Instead of re-evaluating conditions during each deployment attempt, the system uses the token (a copy of the verification state) to quickly validate that conditions are met. This copying mechanism significantly reduces deployment time while maintaining compliance assurance.

Inventive Principle:
Principle #26Copying

3Reliability

If artifact deployment is restricted by conditions, then system security is improved, but deployment flexibility decreases

Engineering Contradiction:
Improvesystem securityVSAvoiddeployment flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically evaluates deployment conditions based on the specific artifact and target environment. Customer-designated conditions can be customized for different deployment scenarios, allowing the system to adapt its security requirements dynamically. The verification service adjusts its evaluation based on the context, maintaining security while preserving flexibility for different deployment needs.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent allows customer-designated conditions to be modified and configured according to specific deployment requirements. Security parameters, compliance rules, and performance thresholds can be changed based on the artifact type, target environment, and organizational policies. This parameter customization enables the system to maintain high security while adapting to diverse deployment scenarios and maintaining flexibility.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250370740A1Obtaining Deployment Tokens For Deploying Artifacts To A Cloud Environment
Publication Date: 2025.12.04 ORACLE INT CORP
  • US20250370740A1 patent drawing
  • US20250370740A1 patent drawing
  • US20250370740A1 patent drawing

AI summary

Techniques for deploying artifacts to a computing environment are disclosed. A system includes a deployment service for routing requests to destination addresses in a target computing environment. The deployment service detects a request from an artifact deployment tool to deploy an artifact to the target computing environment. The deployment service obtains a deployment token representing verification that a set of one or more customer designated conditions are satisfied to deploy the artifact to the target computing environment. The deployment service obtains validation of the deployment token. Responsive to successfully obtaining validation of the deployment token, the deployment service directs the artifact to a destination address in the target computing environment. The artifact is received at the destination address and deployed in the target computing environment.