Reflection-Based Endpoint Security Testing Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current endpoint security testing for APIs is inefficient, requiring manual verification of security attributes across multiple endpoints, which can lead to errors and increased workload, especially in systems with a large number of endpoints.

Innovation Solution

A computing system employing reflection-based methods to automatically determine controller types, method information objects, and endpoint failures within an API, adjusting endpoints and displaying lists of unverified endpoints, thereby streamlining the security testing process and ensuring adequate security measures are implemented.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual verification of security attributes is performed at each endpoint, then security checking can be done, but the workload increases and efficiency decreases

Engineering Contradiction:
Improvesecurity verificationVSAvoidtesting efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs self-service by automatically discovering endpoints through reflection on the web server library and autonomously verifying security attributes without requiring manual intervention at each endpoint, thereby maintaining security verification while dramatically improving testing efficiency

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the manual mechanical process of verifying security attributes at each endpoint with an automated computational system that uses reflection to discover endpoints and automatically performs security checks, eliminating the need for manual verification while maintaining thoroughness

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

2Reliability

If manual security testing is performed across multiple endpoints, then security attributes can be checked, but time consumption increases

Engineering Contradiction:
Improvesecurity attribute verificationVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by using reflection to automatically discover and catalog all endpoints and their associated security attributes before actual security testing begins, which streamlines the subsequent verification process and reduces overall testing time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements continuous useful action by automatically iterating through all discovered endpoints and systematically verifying security attributes without interruption or manual reset, maintaining continuous testing flow that significantly reduces total testing time compared to manual methods

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If comprehensive security checking is performed at all endpoints, then security coverage is improved, but system complexity increases

Engineering Contradiction:
Improvesecurity coverageVSAvoidtesting system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system achieves universality by creating a multi-functional automated testing framework that can handle endpoint discovery, security attribute identification, and verification across diverse endpoint types using a single unified approach through reflection, thereby maintaining comprehensive security coverage without proportionally increasing system complexity

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

Data Source

PatentUS11366883B2Reflection based endpoint security test framework
Publication Date: 2022.06.21 PROGRESS SOFTWARE CORP
  • US11366883B2 patent drawing
  • US11366883B2 patent drawing
  • US11366883B2 patent drawing

AI summary

Methods and systems for deploying an enhanced processing system that performs reflection based endpoint security testing are described herein. A computing system may determine, by performing reflection on a web server library, controller types corresponding to an API. For each of the controller types, the computing system may determine method information objects corresponding to the respective controller types. Based on calls to an endpoint method for each of the one or more method information objects, the computing system may determine endpoint failures associated with the API. The endpoint methods may correspond to each of the one or more method information objects. Based on the determined endpoint failures associated with the API, the computing system may adjust one or more endpoints of the API.