Script Execution Control via Agent Hooks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Scripts embedded in documents can pose a security threat by performing unauthorized operations, compromising host computers, and existing methods struggle to effectively control and monitor their execution.

Innovation Solution

An agent inserts hooks into the sub-execution runtime environment of scripts to monitor behavior, obtain context information, and control script execution based on policy, allowing or inhibiting execution, and reporting malicious activities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If scripts are allowed to execute freely in documents, then document functionality and automation capabilities are improved, but security risks and unauthorized operations increase

Engineering Contradiction:
Improvescript execution capabilityVSAvoidsecurity risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

An agent is introduced as an intermediary component that inserts hooks into the script execution environment. This agent monitors script behaviors, obtains context information, and controls execution based on policy decisions, thereby enabling script functionality while preventing unauthorized operations and security risks

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary analysis and control decisions before script execution proceeds. The agent monitors behaviors and evaluates context information in advance, making policy-based decisions to allow, block, or control script execution before harmful actions can occur

Inventive Principle:
Principle #10Preliminary action

2Reliability

If hooks are inserted to monitor script behavior, then security control and detection capabilities are improved, but system complexity and performance overhead increase

Engineering Contradiction:
Improvesecurity controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The monitoring system is segmented into modular components: hooks inserted at specific points in the execution environment, an agent that processes monitoring data, and policy-based control mechanisms. This segmentation allows for targeted monitoring of critical script behaviors without overwhelming system complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The agent serves multiple functions simultaneously: it monitors script behaviors, obtains context information, evaluates policies, and controls execution. This multi-functionality reduces the need for separate specialized components, thereby managing system complexity while maintaining comprehensive security control

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

Data Source

PatentEP3469509B1Macro-script execution control
Publication Date: 2022.10.19 CYLANCE INC
  • EP3469509B1 patent drawingFigure 1
  • EP3469509B1 patent drawingFigure 2
  • EP3469509B1 patent drawingFigure 3

AI summary

An agent inserts one or more hooks into a sub-execution runtime environment that is configured to include a script and/or targeted to include the script. The agent including the one or more hooks monitors a behavior of the sub-execution runtime environment and/or the script. The agent subsequently obtains context information regarding the sub-execution runtime environment and/or the script so that it can control the runtime of at least the sub-execution runtime environment. Related systems, methods, and articles of manufacture are also disclosed.