Automated Dynamic Penetration Testing on Active Backup Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for testing production systems can disrupt system availability and fail to adequately verify the security and functionality of constantly changing production environments.
Innovation Solution
The system and method involve creating a live backup of a production system, instantiating it on a testing computer, and applying dynamic automatic tests to validate the system's functionality without affecting the production environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing tests are applied to the production system, then the system's security and functionality can be validated, but the system's availability is affected
Solution Approach 1:
The patent creates a copy of the production system (backup instance) and performs tests on this copy rather than on the live production system. This allows comprehensive security validation including penetration testing and vulnerability scanning without affecting the availability of the original production system.
Solution Approach 2:
The system separates the production environment from the testing environment by creating distinct instances. The production system continues operating while a replicated backup instance is isolated for testing purposes, allowing simultaneous operation of both systems with different functions.
2Ease of operation
If static scanning of file storage is performed, then the system can be tested without execution, but the functionality verification is insufficient
Solution Approach 1:
The patent transitions from static file scanning to dynamic execution-based testing. By instantiating the backup system and running actual code execution, the testing process dynamically verifies functionality rather than merely examining static files, providing more accurate assurance of system behavior.
Solution Approach 2:
Instead of scanning static files in the production system, the patent creates a executable copy (backup instance) that can be dynamically tested. This copy allows actual code execution and functional verification without risking the production system.
3Reliability
If the production system is stopped for backup creation, then a consistent backup can be generated, but system downtime occurs
Solution Approach 1:
The system performs preliminary actions by creating backups during maintenance windows or low-traffic periods before production updates are deployed. This allows the backup to be prepared in advance, ensuring consistency without causing downtime during critical deployment moments.
Solution Approach 2:
The patent creates a copy of the production system that can be instantiated and tested independently. This copying mechanism allows backup creation to occur without necessarily stopping the production system, as the backup is a separate replicable instance that can be prepared and validated independently.
Data Source
AI summary
Systems and methods for verifying a production system automatically by testing a backup copy of the production system. The system comprises a backup transporter configured to copy or move a set of backup files from the backup generated of the production system and replicate the set of files on a testing computer, a mounting module configured to instantiate a copy of the production system on the testing computer, and a testing module configured to apply a set of automatic pre-defined tests to the application on the testing computer to analyze the application for vulnerabilities and defects, and generate a list of results of execution of each of the pre-defined tests on the testing computer, the list of results indicative of the vulnerabilities and defects.


