Source: http://www.google.com/patents/US20070250916?dq=5,815,794
Timestamp: 2014-03-15 20:37:05
Document Index: 451049721

Matched Legal Cases: ['Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60']

Patent US20070250916 - B2C Authentication - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsEmbodiments of the invention provide systems and methods for providing authentication of a web site. According to one embodiment, authenticating a web site can comprise receiving a request from a verifier to authenticate the web site. For example, the web site can be authenticated based on pre-stored...http://www.google.com/patents/US20070250916?utm_source=gb-gplus-sharePatent US20070250916 - B2C AuthenticationAdvanced Patent SearchPublication numberUS20070250916 A1Publication typeApplicationApplication numberUS 11/550,142Publication dateOct 25, 2007Filing dateOct 17, 2006Priority dateOct 17, 2005Also published asWO2007047695A2, WO2007047695A3Publication number11550142, 550142, US 2007/0250916 A1, US 2007/250916 A1, US 20070250916 A1, US 20070250916A1, US 2007250916 A1, US 2007250916A1, US-A1-20070250916, US-A1-2007250916, US2007/0250916A1, US2007/250916A1, US20070250916 A1, US20070250916A1, US2007250916 A1, US2007250916A1InventorsMark Shull, Ihab ShraimOriginal AssigneeMarkmonitor Inc.Export CitationBiBTeX, EndNote, RefManReferenced by (5), Classifications (6), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetB2C AuthenticationUS 20070250916 A1Abstract Embodiments of the invention provide systems and methods for providing authentication of a web site. According to one embodiment, authenticating a web site can comprise receiving a request from a verifier to authenticate the web site. For example, the web site can be authenticated based on pre-stored registration information for the web site. Additionally or alternatively, authenticating the web site can be based on reputation information related to the web site. A secure link can be established with the verifier and results of authenticating the web site can be reported to the verifier via the secure link. Establishing a secure link with the verifier can comprise connecting with a secure reporting feature of a client application of the verifier. Images(9) Claims(24)
1. A method for authenticating a web site, the method comprising: receiving a request from a verifier to authenticate the web site; authenticating the web site based on pre-stored registration information for the web site; establishing a secure link with the verifier; and reporting results of authenticating the web site to the verifier via the secure link. 2. The method of claim 1, further comprising validating the pre-stored registration information for the web site prior to authenticating the web site. 3. The method of claim 1, wherein authenticating the web site is further based on reputation information related to the web site. 4. The method of claim 3, wherein the reputation information is obtained from a Universal Reputation Service (URS). 5. The method of claim 1, wherein establishing a secure link with the verifier comprises connecting with a secure reporting feature of a client application of the verifier. 6. The method of claim 5, wherein the client application comprises a web browser. 7. The method of claim 4, wherein establishing a secure link with the verifier comprises connecting with a secure reporting feature of a client application of the verifier via the URS. 8. The method of claim 1, wherein reporting results of authenticating the web site comprises reporting a level of a plurality of levels, wherein each level of the plurality of levels relates to a different amount of possible risk presented by the web site. 9. A system comprising: communications network; a verifier communicatively coupled with the communications network and adapted to request authentication of a web site; and an authentication registry communicatively coupled with the communications network and adapted to receive the request from the verifier to authenticate the web site, authenticate the web site based on pre-stored registration information for the web site, establish a secure link with the verifier, and report results of authenticating the web site to the verifier via the secure link. 10. The system of claim 9, wherein the authentication registry is further adapted to validate the pre-stored registration information for the web site prior to authenticating the web site. 11. The system of claim 9, wherein authenticating the web site is further based on reputation information related to the web site. 12. The system of claim 11, wherein the reputation information is obtained from a Universal Reputation Service (URS). 13. The system of claim 9, wherein establishing a secure link with the verifier comprises connecting with a secure reporting feature of a client application of the verifier. 14. The system of claim 13, wherein the client application comprises a web browser. 15. The system of claim 12, wherein establishing a secure link with the verifier comprises connecting with a secure reporting feature of a client application of the verifier via the URS. 16. The system of claim 9, wherein reporting results of authenticating the web site comprises reporting a level of a plurality of levels, wherein each level of the plurality of levels relates to a different amount of possible risk presented by the web site. 17. A machine-readable medium having stored thereon a series of instruction which, when executed by a processor, cause the processor to authenticate a web site by: receiving a request from a verifier to authenticate the web site; authenticating the web site based on pre-stored registration information for the web site; establishing a secure link with the verifier; and reporting results of authenticating the web site to the verifier via the secure link. 18. The machine-readable medium of claim 17, further comprising validating the pre-stored registration information for the web site prior to authenticating the web site. 19. The machine-readable medium of claim 17, wherein authenticating the web site is further based on reputation information related to the web site. 20. The machine-readable medium of claim 19, wherein the reputation information is obtained from a Universal Reputation Service (URS). 21. The machine-readable medium of claim 17, wherein establishing a secure link with the verifier comprises connecting with a secure reporting feature of a client application of the verifier. 22. The machine-readable medium of claim 21, wherein the client application comprises a web browser. 23. The machine-readable medium of claim 20, wherein establishing a secure link with the verifier comprises connecting with a secure reporting feature of a client application of the verifier via the URS. 24. The machine-readable medium of claim 17, wherein reporting results of authenticating the web site comprises reporting a level of a plurality of levels, wherein each level of the plurality of levels relates to a different amount of possible risk presented by the web site.
CROSS-REFERENCES TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Application No. 60/727,676, filed Oct. 17, 2005 by Shull and entitled �B2C Authentication System,� the entire disclosure of which is incorporated herein by reference. This application is also related to the following commonly-owned, co-pending applications (the �Related Applications�), of which the entire disclosure of each is incorporated herein by reference, as if set forth in full in this document, for all purposes: U.S. patent application Ser. No. 10/709,398, filed May 2, 2004, by Shraim et al. and entitled �Online Fraud Solution�; U.S. Provisional Application No. 60/615,973, filed Oct. 4, 2004, by Shraim et al. and entitled �Online Fraud Solution�; U.S. Provisional Application No. 60/610,714, filed Sep. 17, 2004, by Shull and entitled �Methods and Systems For Preventing Online Fraud�; U.S. Provisional Application No. 60/610,715, filed Sep. 17, 2004, by Shull and entitled �Customer-Based Detection Of Online Fraud�; U.S. patent application Ser. No. 10/996,991, filed Nov. 23, 2004, by Shraim et al. and entitled �Online Fraud Solution�; U.S. patent application Ser. No. 10/996,567, filed Nov. 23, 2004, by Shull et al. and entitled �Enhanced Responses To Online Fraud�; U.S. patent application Ser. No. 10/996,990, filed Nov. 23, 2004, by Shull et al. and entitled �Customer-Based Detection Of Online Fraud�; U.S. patent application Ser. No. 10/996,566, filed Nov. 23, 2004, by Shull et al. and entitled �Early Detection Of Online Fraud�; U.S. patent application Ser. No. 10/996,646, filed Nov. 23, 2004, by Shull et al. and entitled �Enhanced Responses To Online Fraud�; U.S. patent application Ser. No. 10/996,568, filed Nov. 23, 2004, by Shull et al. and entitled �Generating Phish Messages�; U.S. patent application Ser. No. 10/997,626, filed Nov. 23, 2004, by Shull et al. and entitled �Methods and Systems For Analyzing Data Related To Possible Online Fraud�; U.S. patent application Ser. No. 11/237,642, filed Sep. 27, 2005, by Shull et al. and entitled �Platform-Independent Fraud Detection System and Methods�; U.S. Provisional Application No. 60/658,124, filed Mar. 2, 2005, by Shull et al. and entitled �Distribution Of Trust Data�; U.S. Provisional Application No. 60/658,087, filed Mar. 2, 2005, by Shull et al. and entitled �Trust Evaluation System and Methods�; U.S. Provisional Application No. 60/658,281, filed Mar. 2, 2005, by Shull et al. and entitled �Implementing Trust Policies�; U.S. Provisional Application No. 60/727,891 filed Oct. 17, 2005 by Silver and entitled �Client-Side Brand Protection�; and U.S. Provisional Application No. 60/735,335 filed Nov. 10, 2005 by Shull and entitled �B2C Authentication Systems and Methods.�
BACKGROUND OF THE INVENTION Embodiments of the present invention relate generally to preventing online fraud. More specifically, embodiments of the present invention relate to methods and systems for providing authentication of a web site. Today, banks and/or other entities are trying to find ways to extend strong enterprise-to-enterprise (also known as business-to-business) authentication schemes to consumers to enable consumers to know if they are actually connected to the legitimate bank and/or entity they believe they are connected to. These business-to-consumer or B2C approaches are complex, expensive and/or require considerable consumer understanding, compliance and patience. One of the biggest challenges facing corporations and others entities trying to use the Internet for business and/or other legitimate purposes today is that it is very easy for a fraudster or bad actor to buy and use an Internet domain name or IP address that would appear to belong to the legitimate entity and that the fraudster promotes as belonging to the legitimate entity. The fraudster may use the similar domain name or IP address to deceive, confuse, scare or entice a consumer, customer or partner of the company or entity as part of an actual or attempted fraud, fake transaction, counterfeit sale, false association or other identity based crime or other abuse. As a result of these scams, consumers and partners are losing trust in and are becoming less willing to use the Internet, online commerce or self-service systems, email, and/or other Internet based services to interact with and transact business with the entity. This causes harm to the entity such as lost revenue due to lower sales and/or increased operations costs as consumers and others become reluctant to use online services such as online banking, online account management, ecommerce, shopping, travel planning, etc. In response to this, corporations, regulators and others are actively discussing multiple enhanced authentication solutions, such as enhanced authentication for online banking and other types of business to consumer (B2C) commerce and/or services. However, traditional authentication solutions are very costly or impractical, if not impossible to implement globally, across a large consumer population. Hence, there is a need in the art for improved methods and systems for providing authentication of a web site. BRIEF SUMMARY OF THE INVENTION Embodiments of the invention provide systems and methods for providing authentication of a web site. According to one embodiment, a method for authenticating a web site can comprise receiving a request from a verifier to authenticate the web site. For example, the web site can be authenticated based on pre-stored registration information for the web site. Additionally or alternatively, authenticating the web site can be based on reputation information related to the web site. In such a case, the reputation information can be obtained, for example, from a Universal Reputation Service (URS). In some cases, the method can also include validating the pre-stored registration information for the web site prior to authenticating the web site. According to one embodiment, a secure link can be established with the verifier and results of authenticating the web site can be reported to the verifier via the secure link. Establishing a secure link with the verifier can comprise connecting with a secure reporting feature of a client application of the verifier. For example, the client application can comprise a web browser. In some cases, establishing a secure link with the verifier can comprises connecting with a secure reporting feature of a client application of the verifier via the URS. According to one embodiment, reporting results of authenticating the web site can comprise reporting a level of a plurality of levels, wherein each level of the plurality of levels relates to a different amount of possible risk presented by the web site. According to another embodiment, a system can comprise a communications network and a verifier communicatively coupled with the communications network and adapted to request authentication of a web site. The system can also include an authentication registry communicatively coupled with the communications network. The authentication registry can be adapted to receive the request from the verifier to authenticate the web site and authenticate the web site base on pre-stored registration information for the web site. In some cases, the authentication registry is further adapted to validate the pre-stored registration information for the web site prior to authenticating the web site. Authenticating the web site can be based on reputation information related to the web site. For example, the reputation information can be obtained from a Universal Reputation Service (URS). The authentication registry can establish a secure link with the verifier and report results of authenticating the web site to the verifier via the secure link. Establishing a secure link with the verifier can comprise connecting with a secure reporting feature of a client application of the verifier. For example, the client application can comprise a web browser. In some cases, establishing a secure link with the verifier comprises connecting with a secure reporting feature of a client application of the verifier via the URS. Reporting results of authenticating the web site can comprise reporting a level of a plurality of levels, wherein each level of the plurality of levels relates to a different amount of possible risk presented by the web site. According to yet another embodiment, a machine-readable medium can have stored thereon a series of instruction which, when executed by a processor, cause the processor to authenticate a web site by receiving a request from a verifier to authenticate the web site. The web site can be authenticated. For example, the web site can be authenticated based on pre-stored registration information for the web site. Additionally or alternatively, authenticating the web site can be based on reputation information related to the web site. In such a case, the reputation information can be obtained, for example, from a Universal Reputation Service (URS). In some cases, the method can also include validating the pre-stored registration information for the web site prior to authenticating the web site. According to one embodiment, a secure link can be established with the verifier and results of authenticating the web site can be reported to the verifier via the secure link. Establishing a secure link with the verifier can comprise connecting with a secure reporting feature of a client application of the verifier. For example, the client application can comprise a web browser. In some cases, establishing a secure link with the verifier can comprises connecting with a secure reporting feature of a client application of the verifier via the URS. According to one embodiment, reporting results of authenticating the web site can comprise reporting a level of a plurality of levels, wherein each level of the plurality of levels relates to a different amount of possible risk presented by the web site.
In certain cases, the system 400 could used be provide warnings if the payload data in the URL associated with the domain name or IP address included dangerous and/or unusual data such as access to a high port or secure application. Analysis by systems, such as those disclosed by the Related Applications, for instance, may be used to provide analysis supporting such features. FIG. 5 is a flowchart illustrating a process for registering a web site with a registration authority according to one embodiment of the present invention. In this example, processing begins with receiving 505 a registration request associated with a web site from a principal. As noted above, the registration request can include information identifying the web site, the principal, and other possible information. Registration information can be recorded 510 in a registration data store. The registration information identify the web site and, possibly, the principal. The registration data may include other information as well as described above. The registration information can be validated 515 in any of a number of different ways or based on any of a number of different factors as described above. For example, the web site can be authenticated based, at least in part, on reputation information related to the web site. Such reputation information can be obtained, for example, from a Universal Reputation Service (URS). A determination 520 can be made as to whether the information identifying the web site is valid. In response to determining 520 the information identifying the web site is valid, an indication of validity associated with the web site can be recorded 525 in the registration data store. In response to determining 520 the information identifying the web site is invalid, an indication of invalidity associated with the web site can be recorded 530 in the registration data store. As described above, in response to determining the information identifying the web site is invalid the registration information can additionally or alternatively be updated to reflect the invalidity. FIG. 6 is a flowchart illustrating a process for authentication of a web site according to one embodiment of the present invention. In this example, processing begins with receiving 605 a request from a verifier to authenticate the web site. The web site can be authenticated 610 based on the registration information as described above. Results of authenticating the web site can then be reported 615 to the verifier in response to the request. FIG. 7 is a flowchart illustrating a process for authentication of a web site according to another embodiment of the present invention. In this example, as in the previous, processing begins with receiving 705 a request from a verifier to authenticate the web site. The web site can be authenticated 710 based on the registration information as described above. A secure link can be established 715 with the browser or other client application requesting the authentication. As noted above, a secure or trusted link can be established with the URS or similar reputation service, which in turn maintains a secure link to the secure reporting features on the browser or to similar secure reporting features on client applications. Alternatively, a secure link can be established with a gateway, which in turn has a secure link to reporting feature on the browser or other client application. Results of authenticating the web site can then be reported 720 to the verifier via the secure link in response to the request. In the foregoing description, for the purposes of illustration, methods were described in a particular order. It should be appreciated that in alternate embodiments, the methods may be performed in a different order than that described. Additionally, the methods may contain additional or fewer steps than described above. It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machine-executable instructions, which may be used to cause a machine, such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions, to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software. While the invention has been described with respect to exemplary embodiments, one skilled in the art will recognize that numerous modifications are possible. For example, the methods and processes described herein may be implemented using hardware components, software components, and/or any combination thereof. Further, while various methods and processes described herein may be described with respect to particular structural and/or functional components for ease of description, methods of the invention are not limited to any particular structural and/or functional architecture but instead can be implemented on any suitable hardware, firmware and/or software configuration. Similarly, while various functionality is ascribed to certain system components, unless the context dictates otherwise, this functionality can be distributed among various other system components in accordance with different embodiments of the invention. Moreover, while the procedures comprised in the methods and processes described herein are described in a particular order for ease of description, unless the context dictates otherwise, various procedures may be reordered, added, and/or omitted in accordance with various embodiments of the invention. Moreover, the procedures described with respect to one method or process may be incorporated within other described methods or processes; likewise, system components described according to a particular structural architecture and/or with respect to one system may be organized in alternative structural architectures and/or incorporated within other described systems. Hence, while various embodiments are described with�or without�certain features for ease of description and to illustrate exemplary features, the various components and/or features described herein with respect to a particular embodiment can be substituted, added and/or subtracted from among other described embodiments, unless the context dictates otherwise. Consequently, although the invention has been described with respect to exemplary embodiments, it will be appreciated that the invention is intended to cover all modifications and equivalents within the scope of the following claims. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7661136 *Dec 13, 2005Feb 9, 2010At&T Intellectual Property Ii, L.P.Detecting anomalous web proxy activityUS7966553 *Jun 7, 2007Jun 21, 2011Microsoft CorporationAccessible content reputation lookupUS8117655 *Dec 14, 2009Feb 14, 2012At&T Intellectual Property Ii, LpDetecting anomalous web proxy activityUS8578166 *Aug 6, 2008Nov 5, 2013Morgamon SASystem and method for authentication, data transfer, and protection against phishingUS20110047602 *Aug 21, 2009Feb 24, 2011International Business Machines CorporationEnd-of-Session Authentication* Cited by examinerClassifications U.S. Classification726/5International ClassificationH04L9/32Cooperative ClassificationH04L63/168, H04L63/08European ClassificationH04L63/08, H04L63/16GLegal EventsDateCodeEventDescriptionJul 12, 2007ASAssignmentOwner name: MARKMONITOR INC., IDAHOFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHULL, MARK;SHRAIM, IHAB;REEL/FRAME:019548/0300;SIGNING DATES FROM 20070621 TO 20070709RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google