Software Version Updates for Malicious Software Defense

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer network security measures are inadequate in detecting and preventing highly sophisticated malicious software attacks, which can evade traditional antivirus systems and compromise network security by learning hardware and software structures, leading to data extraction and system disruption.

Innovation Solution

Implementing a security control module that routinely changes software applications and processing resources, using software creation tools to generate new versions quickly, and maintaining a library of application versions to render learned vulnerabilities obsolete, thereby making it difficult for malicious software to exploit system weaknesses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional antivirus software and firewall security measures are used, then basic malicious software detection is improved, but highly sophisticated attacks can still evade detection and compromise system security

Engineering Contradiction:
Improvemalicious software detection capabilityVSAvoideffectiveness against sophisticated attacks
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies dynamics by making the software target constantly changing through routine version updates. The system automatically updates applications and operating systems to new versions that are different from what malicious software has learned, thereby neutralizing previously exploited vulnerabilities before they can be used again.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the software version parameter routinely to render learned vulnerabilities obsolete. By updating software versions, the internal structures and vulnerabilities that malicious software has studied and exploited are changed, making the attacker's learned knowledge ineffective.

Inventive Principle:
Principle #35Parameter changes

2Object-affected harmful factors

If software versions are changed routinely to prevent malicious software learning, then security against learned vulnerabilities is improved, but system complexity and update management requirements increase

Engineering Contradiction:
Improvevulnerability exploitation riskVSAvoidsoftware version management complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent implements self-service through automated security control modules that monitor for malicious software presence and automatically update software versions without requiring manual user intervention. The system detects when updates are needed and applies them automatically, reducing the operational burden on users.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies preliminary action by proactively updating software versions before malicious software can exploit vulnerabilities. The system maintains a library of updated versions and automatically applies them, preventing attackers from learning and exploiting current vulnerabilities in the first place.

Inventive Principle:
Principle #10Preliminary action

3Object-affected harmful factors

If the system constantly changes software applications and processing resources to thwart malicious software, then security effectiveness is improved, but operational stability and predictability deteriorate

Engineering Contradiction:
Improvemalicious software learning capabilityVSAvoidsystem configuration stability
Core Design Contradiction:
Object-affected harmful factorsVSStability of the object's composition

Solution Approach 1:

The patent applies periodic action by implementing routine, scheduled version updates rather than continuous random changes. The system updates software at predetermined intervals or when specific security triggers are detected, providing a balance between changing frequently enough to thwart attackers and maintaining stability through predictable update cycles.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9104862B2Secure computing device using new software versions
Publication Date: 2015.08.11 UPDRAFT LLC
  • US9104862B2 patent drawing
  • US9104862B2 patent drawing
  • US9104862B2 patent drawing

AI summary

A computing device includes a central processing resource, memory, a network interface, and a security control module. The security control module is operable to determine to change at least a portion of a program of the computing device. When the program, or portion thereof, is to be changed, the security control module sends a request to a software generation module for a new version of the program, or portion thereof. The security control module then receives the new version of the program, or portion thereof, and replaces, within the memory, the program, or portion thereof, with the new version of the program, or portion thereof. When the program is evoked, the central processing resource uses the new version of the program, or portion thereof, such that execution of the program is changed, which changes internal operation of the computing device thereby reducing adverse impact of malicious software.