Partial-Application Vulnerability Assessment Using Feature Files

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional vulnerability assessment methods require fully functional software applications, leading to delayed detection of vulnerabilities and extensive modifications, which can introduce additional issues and delays in the development process.

Innovation Solution

A system and method for performing vulnerability assessment on partially functional software applications using feature files and script sets that mimic complete application functionality, allowing for early detection and minimal modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If vulnerability assessment is performed on fully functional applications at beta testing phase, then the application is sufficiently complete for intended use and vulnerabilities can be detected, but the detection and remediation process causes additional downstream changes and delays

Engineering Contradiction:

Improvevulnerability detection capabilityVSAvoiddevelopment cycle time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent performs vulnerability assessment on partially functional applications before they reach the beta testing phase. By conducting security testing earlier in the development cycle on incomplete applications, the system detects vulnerabilities before extensive downstream changes are required, thereby reducing remediation time and accelerating the overall development process while maintaining effective vulnerability detection

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent divides the application into compartmentalized features that can be tested independently. Each feature can be assessed for vulnerabilities separately using feature files and script sets, allowing parallel testing of multiple features and reducing the overall time required for comprehensive vulnerability assessment across the entire application

Inventive Principle:

Principle #1Segmentation

2Ease of manufacture

If vulnerability assessment is performed on partially functional applications, then fewer modifications are required and development is accelerated, but conventional DAST tools and queries are not compatible with incomplete applications

Engineering Contradiction:

Improvemodification effortVSAvoidtool compatibility

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces feature files as an intermediary layer between the partially functional application and the vulnerability assessment tools. These feature files contain metadata and configuration information that enable DAST tools to understand and test incomplete application features without requiring full application functionality, thus bridging the compatibility gap

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent modifies the testing parameters and configurations to match the partial functionality state of the application. By adjusting the scope and depth of security tests based on which features are complete and which are still in development, the system achieves effective vulnerability assessment adapted to the current development stage

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS20250390587A1Systems and methods for performing vulnerability assessment on partially functional applications

Publication Date: 2025.12.25 CITIBANK N A

AI summary

Systems and methods are described herein for performing vulnerability assessment on partially functional software applications (e.g., software applications currently at a phase in the development cycle prior to a user acceptance testing phase). By doing so, the system may detect vulnerabilities, if any, more easily based on the fewer functional components of the application. Additionally or alternatively, curing any vulnerabilities will require fewer modifications to the application's software, architecture, and/or intended functionality (as these characteristics are also earlier in their development cycle).