1. Field of the Invention
The present invention relates to restricting a user's access to emails by requiring multiple levels of user authentication while using a recipient's email account. More specifically, the present invention relates to granting/denying access to emails of a recipient's email account based on an authentication level obtained by a user of the recipient's email account.
2. Description of the Related Art
In a situation where a user delegates access to their computer account to another person, the user typically leaves their email application open, allowing the other person to access the user's emails. In addition, in a situation where a user grants another user access to their email application for the purpose of allowing the other user to send/receive emails from the user's email application, the other user will typically have access to every email in the user's email application.
However, in both scenarios, as described above, the user may wish to restrict the other user's access to particular emails that may contain sensitive or highly classified information (e.g., payroll information).
In order to address the above-mentioned problem wherein the other user has the ability to access sensitive or highly classified emails belonging to the user, a method of utilizing multiple levels of user authentication for accessing emails from an email account/application is described below.
In view of the above-mentioned problems, an embodiment of this invention provides a method of restricting access to emails of a recipient's email account by providing multiple levels of user authentication such that a user of the recipient's email account is only granted access to view emails for which the user has obtained proper authentication based on a designated security level.
An embodiment of this invention may include sending an email, from a sender to the recipient's email account, such that the security level of the email sent by the sender is designated by the sender. Subsequently, the sent email will be received by the recipient's email account.
Further, an embodiment of this invention may include accessing the recipient's email account at a normal authentication level by entering a normal security level authentication (e.g., password). This allows the user of the recipient's email account to only view emails that are designated as having a normal security level.
In addition, another embodiment of this invention may require stepping up the authentication level of the user of the recipient's email account by entering, when prompted, a high security level authentication (e.g., password). This allows the user of the recipient's email account to view emails designated as having a high security level and view the emails designated as having the normal security level.
Moreover, according to an embodiment of this invention, if the user of the recipient's email account is prompted to step-up the authentication level and the user decides not to enter any authentication (e.g., password), then the user will not be granted permission to view any email designated as a high security level email.
According to another embodiment of this invention, if the user of the recipient's email account is prompted to step-up the authentication level and the user enters an incorrect authentication (e.g., password), then the user will not be granted permission to view any email designated as a high security level email.
Furthermore, an embodiment of this invention provides that a properly authenticated user has the ability to designate any email as being a high security level email.
Also, according to an embodiment of this invention a properly authenticated user may have the ability to determine whether or not an existence of an email designated as a high security level email will be made known to the user of the recipient's email account.
Furthermore, additional embodiments of the present invention can be directed to an apparatus for restricting access to emails of a recipient's email account. Moreover, the present invention can be directed to a system including the above-mentioned apparatus for restricting access. In addition, the present invention can also be implemented as a program causing a computer to execute the above-described steps. The program can be distributed via a computer-readable storage medium such as a CD-ROM.
Additional features and advantages are described herein, and will be apparent from, the following Detailed Description and the figures.
The following detailed description refers to the accompanying drawings. Although the description includes exemplary implementations, other implementations are possible and changes may be made to the implementations described without departing from the spirit and scope of the invention. The following detailed description and the accompanying drawings do not limit the invention.
As illustrated in
In order for a user of the recipients email account/application to view the email received by the recipient's email account/application, the user must access the recipient's email account/application by entering a normal security level authentication (e.g., password) (S20). This normal level security authentication (e.g., password) will only allow the user of the recipient's email account/application to view the contents of an email identified as having a normal level of security (S20).
Next, the method may provide the user of the recipient's email account/application the option to step-up the level of authentication (S30). If the user does not want to step-up the level of authentication (NO at S30), then the user will only be allowed to view contents of emails identified as having a normal level of security (S40). However, if the user wants to step-up the level of authentication (YES at S30), then the user will be prompted to enter a high security level authentication (e.g., password) (S50).
If the user does not enter an authentication (e.g., the user realizes that the high level security authentication is unknown) (NO at S60), then the user will only be allowed to view contents of emails identified as having a normal level of security (S40). Similarly, if the user enters a authentication (e.g., password) (YES at S60), but the authentication (e.g., password) is incorrect (NO at S70), then, as mentioned above, the user will only be able to view contents of emails identified as having a normal level of security (S40).
On the other hand, if the authentication (e.g., password) input by the user matches the high security level authentication (e.g., password) (YES at S70) then the user will be able to view the contents of emails both identified as having a normal level of security and a high level of security (S80).
This method may also provide the user an opportunity to initiate the step-up process (YES at S90), even after the user (i) has opted to not step up the security (NO at S30), (ii) has opted to not enter a authentication (e.g., password) (NO at S60), or (iii) has entered an incorrect authentication (e.g., password) (NO at S70). Once the user initiates the step-up process (YES at S90) the user will be prompted to enter the high security level authentication (e.g., password) (S50) and continue through the step-up process, as described above (S60-S80). This high security level authentication (e.g., password) may also be replace by alternative methods of authentication, such as, but not limited to, a fingerprint scan or a retinal scan.
In addition, a properly authenticated user of the recipient's email account may have the option to (i) identify any email in the email account/application as being a normal security level email or a high security level email or (ii) set up specific rules to designate emails as being normal security level emails or high security level emails at the time or after receipt thereof (not illustrated).
Furthermore, a properly authenticated user may also have the option to “lock” their mail application by initializing a locking function so that high security level emails are no longer visible or accessible to the user. This locking function may be initialized by, for example, a sequence of keys of the users' keyboard or a menu function selected by the user.
Moreover, a properly authenticated user of the recipient's email account may have the option of hiding the existence of any emails having a high level of security, such that the user of the recipient's email account/application will not be able to view the subject or existence of any email that has a high level of security (not illustrated). This will eliminate the possibility of a non-authenticated user viewing confidential or highly sensitive information contained in the subject line of a high security level email. Only by stepping up the authentication level will the user be able to recognize the existence of the high security level emails.
Furthermore, if an existing email or an email sent by a sender does not have a designated security level associated therewith, the recipient's email account/application may, by default, designate a normal level of security, a high level of security, or even a low level of security that is lower than the normal level of security.
Also, as an alternative to the above-mentioned embodiment, the user of the recipient's email account/application may not automatically be given the option to step-up the authentication level (S30), wherein the authentication level may only be stepped up when requested by the user (S40).
An embodiment of this invention may provide a properly authenticated user the ability to designate a particular email folder as being a high security level email folder. As an example, a properly authenticated user may want to place all pay stub related emails in a particular folder that requires a high level of authentication.
It should be understood that various changes and modifications to the presently preferred embodiments described herein will be apparent to those skilled in the art. Such changes and modifications can be made without departing from the spirit and scope of the present subject matter and without diminishing its intended advantages. It is therefore intended that such changes and modifications be covered by the appended claim.
Number | Name | Date | Kind |
---|---|---|---|
6192396 | Kohler | Feb 2001 | B1 |
6636965 | Beyda et al. | Oct 2003 | B1 |
6643684 | Malkin et al. | Nov 2003 | B1 |
6804336 | Chiu | Oct 2004 | B2 |
6920564 | Decuir | Jul 2005 | B2 |
7017181 | Spies et al. | Mar 2006 | B2 |
7039951 | Chaudhari et al. | May 2006 | B1 |
7174368 | Ross, Jr. | Feb 2007 | B2 |
7287271 | Riggins | Oct 2007 | B1 |
7333956 | Malcolm | Feb 2008 | B2 |
7334267 | Engstrom | Feb 2008 | B2 |
7346769 | Forlenza et al. | Mar 2008 | B2 |
7401356 | Bandini et al. | Jul 2008 | B2 |
7421472 | Ross, Jr. | Sep 2008 | B1 |
7424543 | Rice, III | Sep 2008 | B2 |
7447903 | Sandhu et al. | Nov 2008 | B2 |
20020059144 | Meffert et al. | May 2002 | A1 |
20020087479 | Malcolm | Jul 2002 | A1 |
20020112015 | Haynes | Aug 2002 | A1 |
20020120869 | Engstrom | Aug 2002 | A1 |
20020124052 | Brown et al. | Sep 2002 | A1 |
20020169954 | Bandini et al. | Nov 2002 | A1 |
20040078334 | Malcolm et al. | Apr 2004 | A1 |
20040136513 | Chiu | Jul 2004 | A1 |
20040243856 | Shatford | Dec 2004 | A1 |
20050010801 | Spies et al. | Jan 2005 | A1 |
20050039004 | Adams et al. | Feb 2005 | A1 |
20050203855 | Malcolm | Sep 2005 | A1 |
20050204172 | Malcolm | Sep 2005 | A1 |
20050216771 | Malcolm | Sep 2005 | A1 |
20050267939 | Davidson et al. | Dec 2005 | A1 |
20060037055 | Hashimoto et al. | Feb 2006 | A1 |
20060248333 | Sandhu et al. | Nov 2006 | A1 |
20070067402 | Sugii et al. | Mar 2007 | A1 |
20070116281 | Brown et al. | May 2007 | A1 |
20070124400 | Lee | May 2007 | A1 |
20070169176 | Cook et al. | Jul 2007 | A1 |
20070174455 | Sugimoto | Jul 2007 | A1 |
20070204145 | Bunn et al. | Aug 2007 | A1 |
20070204331 | O'Brien | Aug 2007 | A1 |
20070233794 | Singh | Oct 2007 | A1 |
20070255790 | Weksler et al. | Nov 2007 | A1 |
20070271348 | Yang | Nov 2007 | A1 |
20080162346 | Aaron et al. | Jul 2008 | A1 |
20080168135 | Redlich et al. | Jul 2008 | A1 |
20080172717 | Malcolm | Jul 2008 | A1 |
20080172730 | Sandhu et al. | Jul 2008 | A1 |
20080194296 | Roundtree | Aug 2008 | A1 |
20080270789 | Bandini et al. | Oct 2008 | A1 |
20080300904 | Malcolm | Dec 2008 | A1 |
20080301297 | Malcolm et al. | Dec 2008 | A1 |
20080301454 | Malcolm et al. | Dec 2008 | A1 |
20080301761 | Malcolm | Dec 2008 | A1 |
20080301762 | Malcolm | Dec 2008 | A1 |
Number | Date | Country |
---|---|---|
6276221 | Sep 1994 | JP |
2006211029 | Aug 2006 | JP |