Trusted Entity Backend for Online Bot Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Merchants and online entities face challenges in distinguishing between genuine users and fraudulent bots accessing their services, leading to security breaches and fraudulent activities.
Innovation Solution
Implementing a system where a trusted entity verifies customer electronic devices by storing cookies and using hash values to confirm device authenticity, with mechanisms for data sharing and authorization to ensure secure interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If merchants implement basic authentication methods, then ease of operation is improved, but reliability is worsened due to inability to distinguish bots from genuine users
Solution Approach 1:
A trusted entity backend acts as an intermediary between the customer electronic device and the online entity. The backend receives validation calls from the web browser, checks for trusted cookies, and returns validation values indicating whether the device is known to the trusted entity. This intermediary layer enables reliable bot detection without requiring complex authentication at the merchant system.
2Reliability
If merchants implement complex authentication methods, then reliability is improved, but device complexity is worsened
Solution Approach 1:
The complex authentication logic is extracted from the merchant system and placed in a separate trusted entity backend. The web browser includes a hidden iframe with code that automatically executes validation calls to the backend, removing the burden of complex authentication implementation from the merchant while maintaining high reliability through cookie verification and device recognition.
Data Source
AI summary
A method for providing online security may include: (1) receiving, by a validation computer program executed by a trusted entity backend for a trusted entity, a call from a web browser executed on a customer electronic device browsing a webpage for an online entity, the call comprising an online entity identifier for the online entity and a session identifier, wherein the webpage for the online entity may include a hidden <iframe> comprising code that causes the web browser to execute the call; (2) confirming, by the validation computer program, that a cookie for the trusted entity may be stored on the customer electronic device; and (3) returning, by the validation computer program, a first value indicating that the customer electronic device is known to the trusted entity or a second value indicating that the customer electronic device is not known to the trusted entity based on the confirmation.