Cloud Executable Security via Segmented Pull Requests

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Cloud-based computing systems face vulnerabilities due to the rapid creation and execution of executables across numerous user accounts and permission groups, leading to potential harmful code execution, which existing technologies fail to adequately manage.

Innovation Solution

A system and method for securing executables in a cloud-based environment by implementing a process that includes receiving and approving pull requests for executable documents and scripts, storing them in separate repositories, and generating commands for system managers to create and execute these documents and scripts, with automated checks for malicious code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If executables are distributed widely across computing resources and accounts for rapid commissioning, then productivity is improved, but security reliability deteriorates due to increased risk of harmful code execution

Engineering Contradiction:

Improverate of commissioning virtual machinesVSAvoidsecurity risk of harmful code execution

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by requiring pull requests and approvals before executables can be distributed. The approval process validates executables beforehand, ensuring they are safe to execute. This preliminary validation step prevents harmful code from being distributed while still enabling rapid commissioning of virtual machines through automated workflows.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary approval mechanism between executable creation and distribution. The pull request system acts as a mediator that validates executables before they are propagated to computing resources. This intermediary layer separates the productivity benefit of rapid distribution from the security risk by requiring validation through the intermediary approval process.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple user accounts with various permission groups are created to manage cloud resources, then adaptability is improved, but security vulnerability increases due to more potential entry points for malfeasance

Engineering Contradiction:

Improvenumber of user accounts and permission groupsVSAvoidsecurity vulnerability to malfeasance

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the permission structure into hierarchical levels with the system manager account having elevated privileges. Instead of allowing all user accounts to directly create and distribute executables, the system divides permissions so that only the system manager can approve and propagate executables. This segmentation reduces security vulnerability by limiting the scope of permissions each account holds while maintaining adaptability through the hierarchical structure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system manager account serves as an intermediary between regular user accounts and the executable distribution system. Regular users can create pull requests, but the system manager must approve them before executables are distributed. This intermediary role prevents direct execution by untrusted accounts while maintaining system adaptability through controlled approval processes.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If executables are created and executed dynamically without approval processes, then ease of operation is improved, but manufacturing precision deteriorates due to lack of code validation

Engineering Contradiction:

Improvespeed of executable deploymentVSAvoidcode quality and safety validation

Core Design Contradiction:

Ease of operationVSManufacturing precision

Solution Approach 1:

The system performs preliminary validation through pull requests and approvals before executables are deployed. This preliminary action ensures code quality and safety are validated beforehand. The approval process checks executables for harmful code and validates their purpose, maintaining manufacturing precision while still enabling rapid deployment through automated workflows after approval.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent allows skipping detailed manual review by using automated approval workflows for trusted executables. Once an executable is approved, it can be rapidly propagated and executed without repeated validation steps. This skipping mechanism maintains ease of operation for subsequent deployments while the initial approval ensures manufacturing precision through proper validation.

Inventive Principle:

Principle #21Skipping (Rushing through)

Data Source

PatentUS20230359773A1Document management for cloud-based 5g networks

Publication Date: 2023.11.09 BOOST SUBSCRIBERCO LLC

AI summary

Systems, methods, and devices secure executables in a cloud-based environment. An example process includes receiving a first pull request to create an executable document for execution by an instance running in the cloud-based environment. The executable document is stored in a document repository in response to the first pull request and approval of the executable document. A command is generated for a system manager in the cloud-based environment to create the executable document. A second pull request is received to create a script that is executable by the document. The script is stored in a script repository in response to the second pull request and an approval of the script. The executable document runs in response to a run command from the instance running in the cloud-based environment, and the approved script stored in the script repository runs in response to a call from the executable document.