Client Integrity Verifier for Security Policy Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security systems face challenges in verifying the integrity of security policy data on client devices, making them vulnerable to malicious attacks that can alter security operations and compromise device security.

Innovation Solution

A computerized method and system that uses an integrity verifier on the client device to receive and compare verified checksums from a server with client-side checksums generated from stored policy data sets, generating a checksum failure indicator when discrepancies are found, allowing for corrective measures to restore integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If security policy data is stored and accessed by security software on client devices, then security operations can be performed, but the system becomes vulnerable to malicious attacks that can alter the policy data and compromise security

Engineering Contradiction:
Improvesecurity operationsVSAvoidmalicious attacks
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by obtaining verified checksums from a trusted server before executing security policy data on the client device. The integrity verifier compares these pre-obtained checksums against checksums generated from the actual policy data, detecting any alterations before they can compromise security operations. This proactive verification prevents malicious attacks from successfully altering security behavior.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system frequently verifies policy data integrity by comparing checksums, then security against malicious attacks is improved, but additional computational overhead and verification time are introduced

Engineering Contradiction:
Improvepolicy data integrityVSAvoidverification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent uses checksums as lightweight, disposable verification objects instead of comparing entire policy data sets. By generating and comparing only checksum values (hashes), the system achieves frequent integrity verification with minimal computational overhead and time loss. The checksums serve as efficient proxies that can be quickly computed and compared without the burden of processing large policy files.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Measurement precision

If the system uses checksum verification to detect policy data alterations, then detection precision is improved, but the complexity of the verification system increases

Engineering Contradiction:
Improvedetection precisionVSAvoidverification system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces checksums as intermediary objects that mediate between the policy data and the verification process. Instead of directly analyzing or comparing complex policy data structures, the system uses checksums as simplified intermediaries that capture the essential integrity information. This intermediary approach maintains high detection precision while significantly reducing verification system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11062033B2Independent integrity verification of security policy data in applications on a client
Publication Date: 2021.07.13 VMWARE INC
  • US11062033B2 patent drawing
  • US11062033B2 patent drawing
  • US11062033B2 patent drawing

AI summary

The disclosure herein describes verifying integrity of security policies on a client device. Policy data sets associated with security applications of virtual machines on the client device are received from a server and stored on the client device. An integrity verifier on the client device receives verified checksums from the server, wherein the verified checksums are associated with the policy data sets. Client-side checksums are generated by the integrity verifier based on the stored policy data sets. Upon generating the client-side checksums, the integrity verifier compares the verified checksums to the generated client-side checksums. Based on the comparison indicating that a verified checksum and a client-side checksum differ, the integrity verifier generates a checksum failure indicator, wherein the client device is configured to take corrective measures to restore integrity of the virtual machines based on the checksum failure indicator.