Endpoint Scan Profiling Through Single-Request Data Collection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional endpoint scanning systems are inefficient, time-consuming, and prone to errors due to the need for multiple discrete requests to gather endpoint data, which can lead to crashes and resource-intensive operations.

Innovation Solution

A structured request is used to gather endpoint data, including a set of inquiries with anticipated data types and parameter names, allowing for a single response that includes metadata-organized data storage and flexible data type handling, reducing the number of requests and crashes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple discrete requests are used to gather endpoint data, then comprehensive data collection is achieved, but scan time increases and system resource consumption increases

Engineering Contradiction:
Improvedata collection completenessVSAvoidscan time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent combines multiple discrete data collection requests into a single consolidated request message that can gather comprehensive endpoint data in one operation. The request message includes multiple inquiry objects, each targeting different data types (filesystem, registry, processes, etc.), allowing the management device to collect all necessary information simultaneously rather than sequentially, thus reducing scan time while maintaining data completeness

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The request message structure is designed to be universal and multi-functional, capable of handling various data collection needs through a single standardized interface. The inquiry objects within the request can specify different data types and parameters, making the single request as versatile as multiple specialized requests would be, thereby eliminating the need for multiple discrete operations

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

2Reliability

If multiple discrete requests are used to gather endpoint data, then comprehensive data collection is achieved, but system resource consumption increases

Engineering Contradiction:
Improvedata collection completenessVSAvoidsystem resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

By merging multiple data collection operations into a single request message, the patent reduces the overhead associated with multiple separate communications. The endpoint agent processes one consolidated request rather than multiple discrete ones, reducing CPU context switching, memory allocations, and I/O operations, thereby lowering overall system resource consumption while maintaining complete data collection

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If conventional scanning processes are used, then endpoint data is collected, but the system is prone to errors and crashes

Engineering Contradiction:
Improvedata collection capabilityVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements error handling and validation mechanisms beforehand in the request message structure and processing logic. The inquiry objects include predefined data type specifications and parameter validations that prevent malformed requests from causing crashes. Error tolerance is built into the system, allowing it to handle unexpected data formats or missing information gracefully without failing the entire scanning operation

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The system incorporates feedback mechanisms where the endpoint agent validates received requests and provides structured responses about data collection status. This feedback loop allows the management device to detect and handle errors immediately, adjusting subsequent operations accordingly, thereby preventing error propagation and system crashes while maintaining productive data collection

Inventive Principle:
Principle #23Feedback

4Reliability

If multiple requests are configured in multiple ways to generate endpoint profile, then comprehensive profiling is achieved, but the process becomes complex and error-prone

Engineering Contradiction:
Improveprofiling completenessVSAvoidrequest configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent employs a universal request message structure that can handle multiple data collection scenarios through a single standardized format. The inquiry objects within the request provide a flexible yet consistent interface for specifying different data types (filesystem, registry, processes, network, etc.), eliminating the need for multiple specialized request configurations. This universal approach maintains profiling completeness while significantly reducing configuration complexity

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

Data Source

PatentUS12367199B2Endpoint scan and profile generation
Publication Date: 2025.07.22 IVANTI INC
  • US12367199B2 patent drawing
  • US12367199B2 patent drawing
  • US12367199B2 patent drawing

AI summary

A method of profiling an endpoint includes generating a structured request including a set of inquiries, each of which being directed to an endpoint parameter and including a parameter name. The method includes generating a scan message including the set of inquiries and an additional inquiry directed to an additional endpoint parameter. The method includes receiving a single response from the endpoint including raw parameter data responsive to the set of inquiries and the additional inquiry. The method includes storing the raw parameter data in a data lake organized according to extracted metadata. The method includes labeling each data portion using the parameter name and the extracted metadata. The method may include accessing, from the data lake, portions of the raw parameter data responsive to the set of inquiries based on labels associated therewith. The method includes generating a profile report derived from the accessed data.