Runtime Virtual Barrier for JavaScript API Taint Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cyber defense techniques often fail to perform proactive actions to prevent cyber threats or thoroughly analyze behavior of code during a runtime environment, leading to potential vulnerabilities and risks.
Innovation Solution
Implementing a runtime virtual barrier that intercepts API invocations, sanitizes data within a native environment, protects against user interface manipulations, detects communication discrepancies, and masks sensitive data using specialized hardware and software, including a JavaScript agent to prevent malicious code and phishing attempts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If basic rule sets are used for cyber defense, then the system is simple to operate, but it fails to perform proactive actions to prevent cyber threats
Solution Approach 1:
The patent implements proactive security measures by analyzing code behavior during runtime before malicious actions can execute. The virtual barrier intercepts API invocations and analyzes code patterns in advance, preventing cyber threats before they cause harm rather than reacting after detection.
Solution Approach 2:
The patent introduces a virtual barrier as an intermediary layer between the code and the runtime environment. This barrier intercepts API invocations and performs taint analysis, acting as a mediator that enables proactive threat prevention without requiring fundamental changes to the underlying system architecture.
2Measurement precision
If thorough code behavior analysis is performed during runtime, then cyber threat detection accuracy is improved, but system performance decreases
Solution Approach 1:
The patent applies taint analysis selectively to specific code regions and API invocations that are suspected of containing malicious behavior, rather than analyzing entire codebases uniformly. This localized approach maintains high detection accuracy while minimizing performance overhead by focusing computational resources on critical areas.
Solution Approach 2:
The patent dynamically adjusts analysis parameters and depth based on the context of code execution. The virtual barrier modifies its inspection intensity according to the risk level of different code segments, changing analysis parameters in real-time to balance precision and performance requirements.
3Reliability
If a virtual barrier is implemented to intercept API invocations, then code execution control is enhanced, but device complexity increases
Solution Approach 1:
The virtual barrier serves as an intermediary that intercepts API invocations between JavaScript code and native APIs. It provides fine-grained execution control by recording invocation source identifiers and influencing API execution based on taint analysis results, while maintaining a relatively simple architecture through its modular design.
Solution Approach 2:
The virtual barrier is designed to perform multiple functions within a single component: intercepting API invocations, performing taint analysis, recording source identifiers, and controlling execution flow. This multi-functionality reduces overall system complexity by consolidating security functions into one universal mechanism.
Data Source
AI summary
Systems, methods, and non-transitory computer readable media including instructions for implementing a runtime virtual barrier for fine grained execution control are disclose. Implementing the runtime virtual barrier for fine grained execution control includes receiving, by an application capable of JavaScript execution, an executable code including an API invocation; intercepting, by a virtual barrier, the API invocation; determining that the API invocation is an invocation for a native API configured for subsequent execution in response to a trigger event; based on the determination that the API invocation is an invocation for a native API configured for subsequent execution, recording an invocation source identifier; and upon occurrence of the trigger event: retrieving the invocation source identifier; and influencing execution of the native API based on the invocation source identifier.