PREVENTING ABUSE OF SERVICES THROUGH INFRASTRUCTURE INCOMPATIBILITY
First Claim
1. A method of preventing an abuser from gaining access to a service, the method comprising:
- using a processor to perform acts comprising;
identifying a feature of an infrastructure that a spammer uses to register for said service;
presenting a registration page that allows a user to register for said service;
including, in said registration page, a Human Interaction Proof (HIP) challenge, wherein said HIP challenge comprises an aspect that is incompatible with said feature in that said feature prevents said infrastructure from being used to solve said HIP challenge;
determining that said user has solved said HIP challenge; and
based on said determining, allowing said user to register for said service.
2 Assignments
0 Petitions
Accused Products
Abstract
Spammers, and other abusers of web services, may be deterred in their attempts to sign up for these services at large scale by making changes to the service registration procedure, where the changes are designed to break the spammer'"'"'s infrastructure. In one example, a procedure to register for a web service involves presenting a Human Interaction Proof (HIP, or “captcha”) to the user, and gating access to the service upon receipt of a correct solution. If spammers use botnets and/or image capture techniques to initiate registration processes and to transport the HIPs to human or automated solvers, then the registration procedure can be changed in a way that is incompatible with capturing these images, or in a way that is incompatible with receiving HIP solutions from someplace other than the location at which registration was initiated.
10 Citations
20 Claims
-
1. A method of preventing an abuser from gaining access to a service, the method comprising:
using a processor to perform acts comprising; identifying a feature of an infrastructure that a spammer uses to register for said service; presenting a registration page that allows a user to register for said service; including, in said registration page, a Human Interaction Proof (HIP) challenge, wherein said HIP challenge comprises an aspect that is incompatible with said feature in that said feature prevents said infrastructure from being used to solve said HIP challenge; determining that said user has solved said HIP challenge; and based on said determining, allowing said user to register for said service. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
8. One or more computer-readable storage media that store executable instructions to prevent an abuser from gaining access to a service, wherein said executable instructions, when executed by a computer, cause the computer to perform acts comprising:
-
identifying a feature of an infrastructure that an entity uses to register for said service; including, in a registration page for said service, a Human Interaction Proof (HIP) challenge, wherein said HIP challenge comprises an aspect that is incompatible with said feature in that said feature prevents said infrastructure from being used to solve said HIP challenge; receiving, from a user, a solution to said HIP challenge; and allowing said user to register for said service based on a determination that said user has solved said HIP challenge. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A system for preventing an abuser from gaining access to a service, the system comprising:
-
a memory; a processor; and a component that is stored in said memory and executes on said processor, that identifies a feature of an infrastructure that a spammer uses to register for said service, presenting a registration page that allows a user to register for said service, that includes, in said registration page, a Human Interaction Proof (HIP) challenge, wherein said HIP challenge comprises an aspect that prevents said infrastructure from being used to solve said HIP challenge, and that allows said user to register for said service based on a determination that said user has solved said HIP challenge. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification