Delayed Content Serving via Reconnaissance Code
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web server systems face challenges in distinguishing between legitimate and illegitimate requests, as fraudsters use botnets and scraping activities to intercept sensitive information, leading to security risks and load issues, necessitating effective methods to differentiate human-controlled from bot-controlled client devices.
Innovation Solution
A computer-implemented method is introduced that serves reconnaissance code to client devices to determine their control type, with follow-up content served based on the determination, including CAPTCHA tests for ambiguous cases, and polymorphic transformations to secure content, all managed by a separate security intermediary system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If reconnaissance code is served to all clients to determine control type, then security accuracy is improved, but processing load and response time increase
Solution Approach 1:
The system applies reconnaissance code selectively rather than universally. It serves the code only to clients that exhibit suspicious behavior patterns or fail initial heuristic checks, while allowing clearly legitimate traffic to pass through without the overhead of full reconnaissance. This partial application maintains high security accuracy for suspicious traffic while preserving processing throughput for normal traffic.
Solution Approach 2:
The security verification process is segmented into multiple stages: initial heuristic filtering, selective reconnaissance code deployment, and follow-up verification. By dividing the verification process into segments applied at different thresholds, the system achieves high security accuracy for suspicious clients while minimizing the processing load on overall system throughput.
2Ease of operation
If follow-up content is served immediately, then user experience is improved, but security verification completeness deteriorates
Solution Approach 1:
The system performs preliminary security verification using reconnaissance code and behavioral analysis before serving follow-up content. This preliminary action ensures that security verification is completed in advance, allowing legitimate content to be served immediately to verified users while blocking suspicious traffic before it can access protected resources.
Solution Approach 2:
The system implements periodic verification where follow-up content delivery is interspersed with additional verification checks. Rather than serving all content at once, the system delivers content in periodic batches with verification checkpoints, ensuring both user experience through progressive delivery and security through continuous verification.
3Measurement precision
If CAPTCHA tests are administered to all clients, then bot detection accuracy is improved, but processing time and user frustration increase
Solution Approach 1:
The system applies CAPTCHA tests locally to specific high-risk scenarios rather than universally. CAPTCHAs are administered only to clients that exhibit bot-like behavior patterns, such as unusually high request rates, suspicious user agents, or failed authentication attempts. This localized application maintains high bot detection accuracy while minimizing time loss for legitimate users.
Solution Approach 2:
The system dynamically adjusts the threshold parameters for triggering CAPTCHA challenges based on traffic patterns, time of day, and risk assessment. By changing these parameters adaptively, the system maintains high detection accuracy for bots while reducing the frequency of CAPTCHA challenges to legitimate users, thereby minimizing overall verification time loss.
Data Source
AI summary
Techniques are described for delayed serving of protected content. A request has been made by a client computing device for a requested resource comprising a first portion and a second portion that is initially withheld from the client computing device. First content comprising the first portion of the requested resource and reconnaissance code is served for execution on the client computing device. When executed at the client computing device, the reconnaissance code gathers data at the client computing device that indicates whether the client computing device is human-controlled or bot-controlled. The data gathered by the reconnaissance code is received. Based on the data, it is determined that the client computing device is not bot-controlled. In response to determining that the client computing device is not bot-controlled, the second portion of the requested resource is served to the client computing device.


