Proxy Event Monitoring Code for Client-Side File Upload Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Proxy services in networked computer systems often fail to detect and enforce policy rules on user actions taken by client-side applications, such as file uploads, leading to unauthorized actions.
Innovation Solution
Injecting event monitoring code into documents requested by clients, which intercepts user actions and communicates with a proxy service to determine if the actions are permitted or prohibited based on predefined policy rules, allowing or blocking the actions accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a proxy service is used to monitor internet traffic and enforce policy restrictions, then security and compliance are improved, but the proxy service becomes unable to detect user actions taken by client-side applications
Solution Approach 1:
The patent introduces event monitoring code as an intermediary component that bridges the gap between the proxy service and client-side applications. This code injects itself into the client application's execution environment, capturing user actions locally and forwarding them to the proxy service for policy evaluation, thereby extending monitoring capability without requiring changes to the proxy service's core architecture
Solution Approach 2:
The monitoring function is segmented into two distinct components: event monitoring code that runs within the client application to capture user actions, and the proxy service that receives and evaluates these events against policy rules. This segmentation allows each component to specialize in its specific function, improving overall system effectiveness
2Measurement precision
If event monitoring code is injected into documents to intercept user actions, then monitoring capability is improved, but the system complexity increases
Solution Approach 1:
The event monitoring code is designed to be self-injecting into the client application's execution environment. Once injected, it autonomously intercepts user actions, formats events, and forwards them to the proxy service without requiring additional configuration or manual intervention, thereby reducing operational complexity despite the sophisticated monitoring capability
Solution Approach 2:
The event monitoring code performs preliminary actions by injecting itself into the client application before user actions occur. It establishes event interception capabilities in advance, so that when users perform actions, the monitoring is already in place and immediately captures the events with high precision
3Reliability
If the event monitoring code blocks prohibited user actions on the client, then security control is improved, but the client application functionality is restricted
Solution Approach 1:
The proxy service provides feedback to the event monitoring code regarding whether user actions comply with policy rules. This feedback mechanism enables the system to dynamically control action execution based on policy evaluation results, blocking only prohibited actions while allowing permitted actions to proceed normally, thus maintaining both security and usability
Data Source
AI summary
A computer-implemented method includes receiving, by a proxy device, a document from a service provider in response to a request to the service provider from a client device. The proxy device injects into the document event monitoring code for monitoring user actions on the client device. The proxy device sends the document with the event monitoring code to the client device. The event monitoring code intercepts a user request for a file upload event using a client-side application on the client device. The proxy device receives a client request including file information regarding the file upload event from the event monitoring code. The proxy device determines whether the file upload event should be allowed or blocked based on the received file information and stored policy data.