Dormant Software Version Swapping for Security Transition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for upgrading or replacing security software products, such as Microsoft Installer (MSI) and Microsoft Patch (MSP), leave systems vulnerable during the transition period when the old security product is uninstalled and the new one is not yet installed or activated.
Innovation Solution
A method that installs a new version of the security software in a dormant state while the existing version is running, swaps the versions by activating the new and deactivating the old, and reboots the system with the new version enabled before network access, minimizing downtime and vulnerability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional MSI or MSP methods are used to upgrade or replace security software, then the software product is updated to a new version, but the computing system becomes vulnerable during the transition period when the old product is uninstalled or the new product is activated
Solution Approach 1:
The patent applies preliminary action by installing the new security software version in advance while the old version is still running and active. The new version is installed in a dormant state beforehand, prepared and staged, then activated immediately when needed, eliminating the security gap that occurs with conventional uninstall-then-install approaches.
2Loss of time
If the new security software version is installed immediately and activated, then the vulnerability window is reduced, but the existing security product must be uninstalled first creating a protection gap
Solution Approach 1:
The patent uses an intermediary approach by introducing a dormant installation state as a mediator between the running old version and the activated new version. This intermediate state allows the new software to be present on the system without being active, serving as a bridge that maintains continuous protection while enabling seamless version transition.
3Ease of manufacture
If the old security product is uninstalled before the new one is installed, then the new installation process is simpler, but the system is left unprotected during the uninstallation and installation period
Solution Approach 1:
The patent applies preliminary action by performing the installation of the new security software version before uninstalling the old version. The new version is installed in advance in a dormant state, prepared and staged on the system while the old version continues to provide protection, ensuring no security gap occurs during the transition.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method may include receiving a request to install a second version of a software product over a first version of the software product, installing the second version of the software product in a dormant state while the first version of the software product is running, and swapping the first and second versions of the software product by activating the second version of the software product and deactivating the first version of the software product. Various other methods, systems, and computer-readable media are also disclosed.