Modular Endpoint Security Agent with Cloud Plugin Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale systems, efficiently distributing malware combat updates and commands to numerous connected endpoint devices is challenging due to the constant evolution of malware, requiring regular software updates and efficient distribution methods.

Innovation Solution

A cloud-based endpoint security system that allows for the installation of plug-ins on endpoint security agents, enabling automatic and efficient updates and command distribution through a cloud server, where policies specify configurations, and plug-ins are retrieved and configured accordingly, allowing for modular security enhancements without full re-installation of the endpoint agent.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional update distribution methods are used for endpoint security agents in large-scale systems, then update delivery can be achieved, but the distribution efficiency and automation level are insufficient

Engineering Contradiction:
Improveupdate distribution efficiencyVSAvoidautomatic update deployment
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The endpoint security agent automatically checks for updates, retrieves plug-ins, and applies configuration changes without manual intervention. The agent autonomously manages its own update process by communicating with the server, downloading necessary components, and implementing security policies independently.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The server pre-prepares update packages and plug-in configurations before they are needed at the endpoint. Configuration files and plug-in binaries are staged on the server in advance, allowing the endpoint agent to quickly retrieve and install them when updates are required, reducing deployment time.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the endpoint security agent is updated to combat new malware, then security effectiveness improves, but system stability may be disrupted during updates

Engineering Contradiction:
Improvesecurity effectivenessVSAvoidendpoint agent stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The security agent is divided into a core component and separate plug-in modules. The core agent remains stable and continues to provide basic security functions, while updates and new malware combat capabilities are delivered through separate plug-ins that can be installed, updated, or removed without affecting the core agent's stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The security agent employs dynamic loading and hot-swapping of plug-ins, allowing update components to be integrated without restarting the entire agent. The system can dynamically load new security modules into memory and activate them while the agent continues running, maintaining stability during updates.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If complete endpoint agent re-installation is performed to add security capabilities, then all security features are updated, but service continuity is interrupted and deployment time increases

Engineering Contradiction:
Improvesecurity capability flexibilityVSAvoiddeployment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Specific security capabilities are extracted from the main agent into separate plug-in components. This allows individual security features to be updated, added, or removed independently through plug-in installation without requiring re-installation of the entire endpoint agent, significantly reducing deployment time.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The endpoint agent is designed as a universal platform that can support multiple different plug-in types and configurations. A single agent installation provides a foundation that can be adapted to various security requirements by loading different plug-ins, eliminating the need for multiple re-installations to add capabilities.

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

4Ease of operation

If manual configuration updates are performed on each endpoint, then precise control is achieved, but operational complexity and time consumption increase significantly

Engineering Contradiction:
Improveconfiguration management simplicityVSAvoidconfiguration update time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

A configuration file serves as an intermediary between the administrator's intent and the endpoint agent's implementation. The configuration file contains all necessary update instructions, plug-in specifications, and security policy parameters. The endpoint agent reads this single configuration file to automatically perform all updates, eliminating the need for manual step-by-step configuration on each endpoint.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10623445B2Endpoint agent for enterprise security system
Publication Date: 2020.04.14 THREATDOWN INC
  • US10623445B2 patent drawing
  • US10623445B2 patent drawing
  • US10623445B2 patent drawing

AI summary

An endpoint security agent facilitates a security policy on an endpoint computing device. The endpoint agent comprises an engine and one or more plugins that each provide a particular security feature. The endpoint agent receives a policy from a cloud server specifying one or more plug-ins used by the policy and configuration of those plug-ins. The endpoint agent retrieves, installs, and configures the one or more plugins. The endpoint agent updates a communication table with command subscription information obtained from each installed plugin indicating command types subscribed to by each plug-in. When a command is received, a lookup of the command type is performed in the table, and the command is sent to the subscribing plugin.