1. Field of the Invention
The present disclosure relates to user password resetting. More specifically, the present disclosure relates to automated user password resetting in an enterprise environment.
2. Related Art
In today's enterprise, each employee is often assigned a user account for emails and file storage space access. In addition, certain enterprise documents may only be viewed by authorized users. To protect enterprise information from ill-intended intruders and to ensure proper information sharing, user accounts and enterprise documents are password protected. Once in a while, an employee may forget his password and request his password to be reset. Traditionally, such an action is often accomplished by telephoning or visiting in person the enterprise's information help desk, during which a help desk clerk verifies the user's identity and resets his password.
Note that password resetting is one of the most common tasks faced by an enterprise information help desk. Statistics have shown that password resetting accounts for about one in four help desk requests. The human involvement in the password-resetting process is costly to an enterprise. Thus, it is desirable to have an automated way to authenticate a user for the purpose of password resetting in an enterprise environment.
One embodiment of the present invention provides a system for automatically authenticating a user. During operation, the system receives a user's request for authentication. The system then extracts information associated with the user from user-specific information stored in an enterprise computer. The extracted user information does not explicitly relate to a password. The system further generates one or more challenges based on the extracted user information, and receives the user's response to the challenges. Subsequently, the system compares the user's response to the extracted user information, and authenticates the user.
In a variation on this embodiment, the user is authenticated without inputting a password.
In a variation on this embodiment, the system identifies a risk indication.
In a variation on this embodiment, the system subsequently resets a password of the authenticated user.
In a variation on this embodiment, the user-specific information includes one or more of: the user's calendar entries, the user's file usage history, the user's email, the user's contact list, and the user's past activity.
In a variation on this embodiment, the system presents the challenges to the user using a web-based application.
In a variation on this embodiment, the user response is generated by humans.
In a variation on this embodiment, the user response is generated by a proxy for the user.
The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.
The data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, volatile memory, non-volatile memory, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.
Overview
Embodiments of the present invention provide a method for verifying an enterprise user's identity. During operation, an enterprise server automatically generates security questions based on user-specific information, such as documents, emails, and calendar entries, associated with the user. As a result, the user can verify his identity and reset his password without human IT support.
Automated Password Resetting
Because user-specific information often contains information only known to the user, such as his email content, enterprise server 108 can mine such user-specific information to generate a set of questions (challenges) based on the extracted information to verify the user's identity. Being able to authenticate a user based on extracted user information provides added protection to the conventional password-protected system. For example, when enterprise server 108 detects a risk factor, such as number of login attempts exceeds a predetermined number or the user is logging in from an unknown IP address, server 108 can use extracted user information to authenticate the user on top of asking the user to provide his password. In addition, server 108 can use extracted user information to authenticate a user who requests resetting his password.
In one embodiment of the present invention, once a user requests password resetting, the enterprise server accesses user-specific information stored on the server as well as on his local computer devices. Examples of user-specific information include the user's email, the user's calendar entries recording the user's meeting times, the user's contact list, and the user's work documents. In one embodiment, user-specific information stored on the enterprise server also includes files that contain a user's background information, such as his date of birth (DOB) and Social Security Number (SSN).
While mining the user-specific information, the server extracts information associated with the user, such as the user behavior information, and generates a set of questions based on extracted user information. Note that because it is the server (which is a machine) and not the help desk clerk that mines the user-specific information, the user's privacy is not compromised. Note that password related information, such as a backup password or answers to security questions, are often encrypted and in general not extractable. The question can be formulated in a way that little information is revealed by the question itself.
In one embodiment of the present invention, the enterprise server accesses the user's calendar to obtain information regarding a user's upcoming appointment and generates questions based on the appointment information. For example, the user's calendar marks a weekly meeting at 11:00 AM each Tuesday. Accordingly, the server may ask a question like “At what time do you have a weekly recurring meeting on Tuesday?” In a further embodiment of the present invention, the server obtains time stamps of computer work files, such as word-processing documents, and generates a question like “Name a file you have recently worked on.”
In one embodiment, the server monitors the user's web-browsing activity to obtain user information. For example, before requesting to reset his password, a user has searched for and bought tickets for a trip to a Caribbean island. The server may generate a question like “On your next vacation, do you want to go skiing, fishing in the mountains, or to the beach?”
After generating questions that can only be answered by the legitimate user of an account, the server presents the questions to the user, and by comparing the user's input to user information previously extracted by the server, the server can verify the user's identity. If the user's answer matches the extracted user information, the server determines that the user is legitimate and resets the user's password as requested. If the user's answer does not match the extracted user information, the server indicates information mismatch. In one embodiment, the server allows a user a predetermined number of attempts to input the correct answer before finally rejecting the user's password resetting request.
Automatic enterprise password resetting can be implemented using different techniques. In one embodiment, a user accesses a web-based application, which runs on an enterprise server, to request password resetting. The web-based application accesses the user's Microsoft™ Exchange account to obtain information from the user's email, calendar, contact list, etc. Based on obtained user information, the web-based application generates and presents a set of questions for the user to answer. By comparing the user's input with obtained user information, the web-based application authenticates the user and resets the user's password.
In addition to act as an added security feature in a password-protected system, extracted user information can also replace a conventional password. In one embodiment of the present invention, the enterprise server no longer asks a user to input a password, instead, the server authenticates the user using extracted user information each time the user attempts to access his account.
The foregoing descriptions of embodiments of the present invention have been presented only for purposes of illustration and description. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
6055512 | Dean et al. | Apr 2000 | A |
6249405 | Hoshiya et al. | Jun 2001 | B1 |
6332139 | Kaneko et al. | Dec 2001 | B1 |
6564047 | Steele et al. | May 2003 | B1 |
6697806 | Cook | Feb 2004 | B1 |
6925443 | Baggett et al. | Aug 2005 | B1 |
7085555 | Zellner et al. | Aug 2006 | B2 |
7133515 | Cook | Nov 2006 | B1 |
7289794 | Bowne et al. | Oct 2007 | B2 |
7340438 | Nordman et al. | Mar 2008 | B2 |
7373509 | Aissi et al. | May 2008 | B2 |
7433829 | Borgia et al. | Oct 2008 | B2 |
7469340 | Karamchedu et al. | Dec 2008 | B2 |
7472423 | DeCenzo et al. | Dec 2008 | B2 |
7523486 | Turner | Apr 2009 | B1 |
7546276 | Randle et al. | Jun 2009 | B2 |
7729532 | Tedesco et al. | Jun 2010 | B2 |
7853581 | Riedl et al. | Dec 2010 | B2 |
7874011 | Boss et al. | Jan 2011 | B2 |
7877791 | Childress et al. | Jan 2011 | B2 |
7975292 | Corella | Jul 2011 | B2 |
7986816 | Hoanca et al. | Jul 2011 | B1 |
8131718 | Tran | Mar 2012 | B2 |
8359278 | Domenikos et al. | Jan 2013 | B2 |
8385824 | Bakshi et al. | Feb 2013 | B2 |
8572372 | Varriale et al. | Oct 2013 | B2 |
20020040374 | Kent | Apr 2002 | A1 |
20020059202 | Hadzikadic et al. | May 2002 | A1 |
20020099942 | Gohl | Jul 2002 | A1 |
20020147766 | Vanska et al. | Oct 2002 | A1 |
20020165986 | Tarnoff | Nov 2002 | A1 |
20020169865 | Tarnoff | Nov 2002 | A1 |
20020174073 | Nordman et al. | Nov 2002 | A1 |
20030028451 | Ananian | Feb 2003 | A1 |
20030128099 | Cockerham | Jul 2003 | A1 |
20030139174 | Rao | Jul 2003 | A1 |
20030191682 | Shepard et al. | Oct 2003 | A1 |
20030229900 | Reisman | Dec 2003 | A1 |
20040128183 | Challey et al. | Jul 2004 | A1 |
20040140885 | Slicker et al. | Jul 2004 | A1 |
20040168069 | Knight | Aug 2004 | A1 |
20040187029 | Ting | Sep 2004 | A1 |
20040255140 | Margolus et al. | Dec 2004 | A1 |
20050005113 | Dillon et al. | Jan 2005 | A1 |
20050027713 | Cameron et al. | Feb 2005 | A1 |
20050039005 | Dyck et al. | Feb 2005 | A1 |
20050071643 | Moghe | Mar 2005 | A1 |
20050114527 | Hankey et al. | May 2005 | A1 |
20050114705 | Reshef et al. | May 2005 | A1 |
20050207560 | Speight | Sep 2005 | A1 |
20050246434 | Bantz et al. | Nov 2005 | A1 |
20050261062 | Lewin et al. | Nov 2005 | A1 |
20050288961 | Tabrizi | Dec 2005 | A1 |
20050289650 | Kalogridis | Dec 2005 | A1 |
20060010203 | Mrsic-Flogel et al. | Jan 2006 | A1 |
20060036868 | Cicchitto | Feb 2006 | A1 |
20060048190 | Aoki et al. | Mar 2006 | A1 |
20060095508 | Itabashi et al. | May 2006 | A1 |
20060105784 | Zellner et al. | May 2006 | A1 |
20060230461 | Hauser | Oct 2006 | A1 |
20060282660 | Varghese et al. | Dec 2006 | A1 |
20060288425 | Redlich et al. | Dec 2006 | A1 |
20070016488 | Ulenas | Jan 2007 | A1 |
20070156677 | Szabo | Jul 2007 | A1 |
20070179846 | Jain et al. | Aug 2007 | A1 |
20070186103 | Randle et al. | Aug 2007 | A1 |
20070220575 | Cooper et al. | Sep 2007 | A1 |
20070232271 | Dyck et al. | Oct 2007 | A1 |
20070250920 | Lindsay | Oct 2007 | A1 |
20070266031 | Adams et al. | Nov 2007 | A1 |
20070266258 | Brown et al. | Nov 2007 | A1 |
20070288613 | Sudame et al. | Dec 2007 | A1 |
20080066165 | Rosenoer | Mar 2008 | A1 |
20080071619 | Charlton et al. | Mar 2008 | A1 |
20080120508 | Marconi et al. | May 2008 | A1 |
20080133364 | Ullah | Jun 2008 | A1 |
20080140577 | Rahman et al. | Jun 2008 | A1 |
20080140786 | Tran | Jun 2008 | A1 |
20080141337 | Yeung et al. | Jun 2008 | A1 |
20080168540 | Agarwal et al. | Jul 2008 | A1 |
20080200168 | Jiang | Aug 2008 | A1 |
20080222734 | Redlich et al. | Sep 2008 | A1 |
20080229422 | Hudis et al. | Sep 2008 | A1 |
20080242279 | Ramer et al. | Oct 2008 | A1 |
20080262863 | Stickley et al. | Oct 2008 | A1 |
20080263652 | McMurtry et al. | Oct 2008 | A1 |
20090089869 | Varghese | Apr 2009 | A1 |
20090100047 | Jones et al. | Apr 2009 | A1 |
20090150677 | Vedula et al. | Jun 2009 | A1 |
20090150989 | Hoey et al. | Jun 2009 | A1 |
20090158406 | Jancula et al. | Jun 2009 | A1 |
20090177323 | Ziegler et al. | Jul 2009 | A1 |
20090228583 | Pocklington et al. | Sep 2009 | A1 |
20090249477 | Punera | Oct 2009 | A1 |
20090319482 | Norlander et al. | Dec 2009 | A1 |
20090320107 | Corella | Dec 2009 | A1 |
20100004004 | Browne-Swinburne et al. | Jan 2010 | A1 |
20100024037 | Grzymala-Busse et al. | Jan 2010 | A1 |
20100030905 | Fikouras et al. | Feb 2010 | A1 |
20100037047 | Varriale et al. | Feb 2010 | A1 |
20100106503 | Farrell et al. | Apr 2010 | A1 |
20100122316 | Lyon | May 2010 | A1 |
20100146263 | Das et al. | Jun 2010 | A1 |
Entry |
---|
Rabkin, “Personal knowledge questions for fallback authentication: Security questions in the era of Facebook”, 2008. |
M.Jakobsson, L. Yang, and S. Wetzel. “Quantifying the Security of Preference-Based Authentication.” DIM '08. |
M.Jakobsson, E. Stolterman, S. Wetzel, and L. Yaang “Love and Authentication”, In Proceedings of ACM Human/Computer Interaction Conf. (CHI), 2008. |
Number | Date | Country | |
---|---|---|---|
20100122340 A1 | May 2010 | US |