Jump to content

Self-service password reset: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
rm spam
Shohami (talk | contribs)
Line 28: Line 28:


In September 2008, the [[Yahoo]] e-mail account of [[Governor of Alaska]] and [[Vice President of the United States]] nominee [[Sarah Palin]] was accessed without authorization by someone who was able to research answers to two of her security questions, her zip code and date of birth and was able to guess the third, where she met her husband.[http://news.yahoo.com/s/ap/20080918/ap_on_el_pr/palin_hacked]
In September 2008, the [[Yahoo]] e-mail account of [[Governor of Alaska]] and [[Vice President of the United States]] nominee [[Sarah Palin]] was accessed without authorization by someone who was able to research answers to two of her security questions, her zip code and date of birth and was able to guess the third, where she met her husband.[http://news.yahoo.com/s/ap/20080918/ap_on_el_pr/palin_hacked]
This incident clearly highlighted that the choice of security questions is very important to prevent
[[social engineering]] attacks on password systems.


==Preference-based Authentication==
==Preference-based Authentication==

Revision as of 21:07, 8 February 2010

Self-service password reset is defined as any process or technology that allows users who have either forgotten their password or triggered an intruder lockout to authenticate with an alternate factor, and repair their own problem, without calling the help desk. It is a common feature in identity management software and often bundled in the same software package as a password synchronization capability.

Typically users who have forgotten their password launch a self-service application from an extension to their workstation login prompt, using their own or another user's web browser, or through a telephone call. Users establish their identity, without using their forgotten or disabled password, by answering a series of personal questions, using a hardware authentication token, responding to a password notification e-mail or, less often, by providing a biometric sample. Users can then either specify a new, unlocked password, or ask that a randomly generated one be provided.

Self-service password reset expedites problem resolution for users "after the fact," and thus reduces help desk call volume. It can also be used to ensure that password problems are only resolved after adequate user authentication, eliminating an important weakness of many help desks: social engineering attacks, where an intruder calls the help desk, pretends to be the intended victim user, claims that he has forgotten his password, and asks for a new password.

There are many software products available to allow employees to self-reset passwords.

Vulnerability

On the other hand, self-service password reset that relies solely on answers to personal questions can introduce new vulnerabilities [1] [2] , since the answers to such questions can often be obtained by social engineering, phishing techniques or simple research. While users are frequently reminded never to reveal their password, they are less likely to treat as sensitive the answers to many commonly used security questions, such as pet names, place of birth or favorite movie. Much of this information may be publicly available on some users' personal home pages. Other answers can be elicited by someone pretending to conduct an opinion survey or offering a free dating service. Since many organizations have standard ways of determining login names from real names, an attacker who knows the names of several employees at such an organization can choose one whose security answers are most readily obtained.

This vulnerability is not strictly due to self-service password reset -- it often exists in the help desk prior to deployment of automation. Self-service password reset technology is often used to reduce this type of vulnerability, by introducing stronger caller authentication factors than the human-operated help desk had been using prior to deployment of automation.

In September 2008, the Yahoo e-mail account of Governor of Alaska and Vice President of the United States nominee Sarah Palin was accessed without authorization by someone who was able to research answers to two of her security questions, her zip code and date of birth and was able to guess the third, where she met her husband.[1] This incident clearly highlighted that the choice of security questions is very important to prevent social engineering attacks on password systems.

Preference-based Authentication

Jakobsson, Stolterman, Wetzel, and Yang proposed to use preferences to authenticate users for password reset[3] [4] . The underlying insights are that preferences are stable over a long period of time [5] , and are not publicly recorded. Their approach includes two phases---setup and authentication. During the setup, a user is asked to select items that they either like or dislike from several categories of items which are dynamically selected from a big candidate set and are presented to the user in a random order. During the authentication phase, a user is asked to classify his preferences (like or dislike) for the selected items displayed to him in a random order. See [2] for a live system. They evaluated the security of their approach by user experiments, user emulations, and attacker simulations.

Accessibility

A major problem with self-service password reset inside corporations and similar organizations is enabling users to access the system if they forgot their primary password. Since SSPR systems are typically web-based, a user must launch a web browser to fix his problem -- but the user cannot log into his workstation until the problem is solved. There are various approaches to addressing this Catch-22, all of which are compromises (e.g., desktop software deployment, domain-wide password reset account, telephone access, visiting a neighbour, continuing to call the help desk, etc.).

The vouching option

In conjunction with preference-based authentication, self-service password reset procedures could also rely on the network of existing human relations among users. In this scenario, the user who forgot his password asks a colleague for assistance. The "helper" colleague authenticates with the password reset application and vouches for user's identity. [6] [7]


References

  1. ^ Griffith, Virgil. "Messin' with Texas, Deriving Mother's Maiden Names Using Public Records" (PDF).
  2. ^ Rabkin, Ariel. "Personal Knowledge Questions for Fallback Authentication: Security Questions in the Era of Facebook" (PDF).
  3. ^ Jakobsson, Markus; et al. "Love and Authentication" (PDF). {{cite web}}: Explicit use of et al. in: |first= (help)
  4. ^ Jakobsson, Markus; et al. "Quantifying the Security of preference-based Authentication" (PDF). {{cite web}}: Explicit use of et al. in: |first= (help)
  5. ^ Crawford, Duane; et al. (1986). "The Stability of Leisure Preferences". Journal of Leisure Research,. 18. {{cite journal}}: Explicit use of et al. in: |first= (help)CS1 maint: extra punctuation (link)
  6. ^ Finetti, Mario. "Self service password reset in large organisations".
  7. ^ RSA Laboratories. "Fourth-factor authentication: somebody you know".