Browse Prior Art Database

Method and System for Protecting User Accounts

IP.com Disclosure Number: IPCOM000202403D
Publication Date: 2010-Dec-15
Document File: 3 page(s) / 93K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for protecting a user account from hacking and Denial of Service (DoS) attacks is disclosed. The user account may include, but is not limited to, an email account, an intranet account and a website account. The method and system includes the use of a private identifier, instead of the user account name, for authenticating access to the user account.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

Method and System for Protecting User Accounts

Disclosed is a method and system for protecting a user account from hacking and Denial of Service (DoS) attacks. The user account may include, but is not limited to, an email account, an intranet account and website account. In order to protect the user account, the method and system uses a private identifier, instead of the user account name, for authenticating access to the user account. The private identifier may be specified by a user of the user account. Further, the user may modify the private identifier at anytime. The private identifier specified by the user is internally mapped to the corresponding user account name at an authenticating point. As a result, the user may gain access to the user account by entering the private identifier and the corresponding password. Since the private identifier is not publicly known, a malicious entity may not be able to launch hacking or DoS attacks by knowing the user account name, which may be publicly available.

In an embodiment of the disclosed method and system, a user's email account may be protected by supplementing the email-ID and password with a private user-ID. The email-ID may be shared publicly so that other users who wish to communicate with the user may address their communications to the email-ID. For example, as illustrated in the figure, the email-ID of a user named Alice is represented as 'Apu@Aldom.com'. This publicly shareable email-ID is associated with a private user-ID 'Apr@Aldom.com' at the domain server. Similarly, another user named Bob holds an email account with public email-ID represented as 'Bpu@Bobdom.com', and a private user-ID represented as 'Bpr@Bobdom.com'. Accordingly, Alice and Bob may communicate with each other by using their respective email-IDs which may be publicly shared, namely, 'Apu@Aldom.com' and 'Bpu@Bobdom.com'. In other words, only the public email-IDs are used for addressing communications between users. For instance, Alice may send an email to Bob at the address 'Bpu@Bobdom.com'. When Bob receives the email, the address of the sender, i.e. Alice, is displayed as 'Apu@Aldom.com'. Therefore, neither Alice nor Bob are aware of the other's private user-ID.

1


Page 02 of 3

(This page contains 00 pictures or other non-text object)

Figure

The privat...