Automated Code Validation and Deployment Security Scanning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing number of software flaws, particularly security vulnerabilities, poses challenges in ensuring the security and performance of software applications, leading to costly corrections, negative customer experiences, and difficulties in ensuring all users have the latest patches.

Innovation Solution

An automated system for software code validation and deployment, where a server computer performs a security scan on obtained software code before deployment, identifying vulnerabilities and their threat levels, and either terminating deployment or proceeding based on the scan results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software code is scanned for security vulnerabilities before deployment, then security reliability is improved, but deployment time and processing complexity increase

Engineering Contradiction:
Improvesecurity reliabilityVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs security scanning of software code before deployment to identify vulnerabilities in advance. The security scan engine automatically analyzes the code for known vulnerability patterns, allowing issues to be detected and addressed before the software is deployed to production environments, thereby preventing security breaches while maintaining efficient deployment timelines

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If security scanning is performed on all software code, then vulnerability detection capability is improved, but system complexity and computational resources increase

Engineering Contradiction:
Improvevulnerability detection capabilityVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The security scan engine automatically performs vulnerability scanning without requiring manual intervention. The system self-manages the scanning process, including automatically comparing code against vulnerability databases, generating reports, and notifying relevant personnel, thereby reducing operational complexity while maintaining high detection capability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual security review processes with automated computational scanning. Instead of relying on human analysts to manually examine code for vulnerabilities, the security scan engine uses automated pattern recognition and comparison algorithms to rapidly identify security issues, reducing both time and human resource requirements

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If deployment is terminated when vulnerabilities are detected, then security reliability is improved, but productivity and deployment speed decrease

Engineering Contradiction:
Improvesecurity reliabilityVSAvoiddeployment speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies different handling approaches based on the specific vulnerability characteristics. Critical vulnerabilities that pose immediate security risks result in deployment termination, while minor vulnerabilities may be flagged for monitoring or addressed in subsequent updates. This selective approach ensures high security reliability for critical issues while maintaining deployment productivity for non-critical cases

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12299136B2Automated software code validation and deployment
Publication Date: 2025.05.13 AT&T INTELLECTUAL PROPERTY I L P
  • US12299136B2 patent drawing
  • US12299136B2 patent drawing
  • US12299136B2 patent drawing

AI summary

Automated software code validation and deployment can include obtaining software code. The software code can be created via interactions with a computing device. In response to obtaining the software code and prior to receiving a request to deploy the software code, a security scan can be performed on the software code. After performing the security scan on the software code, a request to deploy the software code can be detected and in response to detecting the request, it can be determined if the software code includes a vulnerability that was detected during the security scan. If a determination is made that the software code does not include the vulnerability, the software code can be deployed. If a determination is made that the software code includes the vulnerability, deployment of the software code can be terminated, a security scan report can be generated, and the security scan report can be output.