An improved system and approaches for protecting passwords are disclosed. A file security system for an organization operates to protect the files of the organization and thus prevents or limits users from accessing some or all of the files (e.g., documents) associated with the organization. According...http://www.google.ca/patents/US7836310?utm_source=gb-gplus-sharePatent US7836310 - Security system that uses indirect password-based encryption

An improved system and approaches for protecting passwords are disclosed. A file security system for an organization operates to protect the files of the organization and thus prevents or limits users from accessing some or all of the files (e.g., documents) associated with the organization. According to one aspect, a password entered by a user is used, provided it is authenticated, to obtain a respective authentication string (a relatively longer string of numbers or characters). The retrieved authentication string is then used to enable the user to enter the file security system and/or to access secured files therein. According to another aspect, user passwords are not stored in the file security system to avoid security breaches due to unauthorized capture of user passwords.

Images(11)

Claims(45)

1. A method for authenticating a user to a file security system, the method comprising:

receiving notification of a login request that includes at least a password associated with the user;

decrypting an encrypted authentication string with the password received with the login request to produce a decrypted authentication string, the encrypted authentication string having been created using a random number of a predetermined length and encrypted using a previously-received password associated with the user; and

determining whether the user is authenticated based on the decrypting.

2. The method as recited in claim 1, wherein the received password is never stored in a file by or for the file security system.

3. The method as recited in claim 1, wherein the received password is never stored in a non-volatile manner.

4. The method as recited in claim 1, further comprising:

permitting access to files protected by the file security system in response to determining that the user is authenticated.

5. The method as recited in claim 1, further comprising:

denying access to files protected by the file security system in response to determining that the user is not authenticated.

6. A method for authenticating a user to a file security system, the method comprising:

receiving a password associated with the user;

accessing an encrypted authentication string from a server machine associated with the file security system, the encrypted authentication string having been created using a random number of a predetermined length and encrypted using a previously-received password, wherein the encrypted authentication string is associated with the user;

decrypting the encrypted authentication string with the received password to produce a decrypted authentication string; and

determining whether the user is authenticated based on the decrypting.

7. The method as recited in claim 6, further comprising removing the received password from memory after the decrypting.

8. The method as recited in claim 6, wherein the file security system is provided on at least one computer, the computer having non-volatile storage and volatile storage,

the method further comprising:

removing the received password from the volatile storage after the decrypting, and

wherein following receiving the password and before removing the received password after the decrypting, the received password is only stored in the volatile storage.

9. The method as recited in claim 6, the determining further comprising determining whether decryption of the encrypted authentication string was successful.

10. The method as recited in claim 6, further comprising:

permitting access to files protected by the file security system in response to determining that the user is authenticated.

11. The method as recited in claim 6, further comprising:

denying access to files protected by the file security system in response to determining that the user is not authenticated.

12. A method for re-authenticating a user to a file security system, where the user was previously authenticated to the file security system, comprising:

determining whether a re-authorization condition exists; and

re-authenticating the user to the file security system in response to determining that the re-authorization condition exists, said re-authenticating includes at least:

receiving a password associated with the user;

accessing an encrypted authentication string from a server machine associated with the file security system;

decrypting the encrypted authentication string with the received password to produce an authentication string; and

determining whether the user is re-authenticated based on said decrypting.

13. The method as recited in claim 12, wherein determining whether a re-authorization condition exists includes determining that the user is attempting to perform an operation with respect to the file security system that is deemed to be highly guarded.

14. The method as recited in claim 12, wherein determining whether a re-authorization condition exists includes determining that the user is attempting to export a certificate.

15. The method as recited in claim 12, wherein the re-authentication further includes the act of removing the received password from memory after the decrypting.

16. The method as recited in claim 12, wherein the file security system is provided on at least one computer, the computer having non-volatile storage and volatile storage,

wherein the re-authentication further includes the act of:

removing the received password from the volatile storage after the decrypting, and

wherein following the receiving of the password and before the removing, the received password is only stored in the volatile storage.

17. The method as recited in claim 12, the determining further comprising determining whether decryption of the encrypted authentication string was successful.

18. The method as recited in claim 12, further comprising:

permitting access to the file security system in response to determining that the user is re-authenticated.

19. The method as recited in claim 12, further comprising:

denying access to the file security system in response to determining that the user is not re-authenticated.

20. A method for changing a password of a user, wherein the password is associated with a file security system, the method comprising:

retrieving a stored, existing password associated with the user;

accessing an encrypted authentication string from a server machine associated with the file security system, the encrypted authentication string having been created by:

generating a random number of a predetermined length;

converting the random number into the authentication string; and

encrypting the authentication string using the existing password, so as to associate the encrypted authentication string with the user;

decrypting the encrypted authentication string with the existing password to produce a decrypted authentication string; and

determining whether the user is authenticated based on the decrypting.

21. The method as recited in claim 20, wherein the method does not require any of the files protected by the file security system to be modified if a password is changed for the user.

22. The method as recited in claim 20, further comprising:

denying the user from changing the password from the existing password to a new password in response to determining that the user is not authenticated.

23. The method as recited in claim 20, further comprising:

permitting a password to be changed from the existing password to the new password in response to determining that the user is authenticated.

24. The method as recited in claim 23, wherein the permitting comprises:

encrypting the authentication string using the new password to produce a new encrypted authentication string; and

storing the new encrypted authentication string in the server machine for subsequent usage.

25. An article of manufacture including a computer readable medium having instructions stored thereon, that, in response to execution by a computing device, cause the computing device to perform operations for authenticating a user to a file security system, the operations comprising:

receiving a file access request including at least a password associated with the user;

decrypting an encrypted authentication string with the password received with the file access request to produce a decrypted authentication string, the encrypted authentication string having been created using a random number of a predetermined length and encrypted using a previously-received password associated with the user; and

determining whether the user is authenticated based on the decrypting.

26. The article of manufacture as recited in claim 25, the operations further comprising:

permitting access to files protected by the file security system in response to determining that the user is authenticated.

27. The article of manufacture as recited in claim 25, the operations further comprising:

denying access to files protected by the file security system in response to determining that the user is not authenticated.

28. A computer readable medium having stored thereon, computer program code that, in response to execution by a computer, causes the computer to authenticate a user to a file security system by a method comprising:

receiving a password associated with the user;

accessing an encrypted authentication string from a server machine associated with the file security system, the encrypted authentication string having been created using a random number of a predetermined length and encrypted using a previously-received password, wherein the encrypted authentication string is associated with the user;

wherein the encrypted authentication string is associated with the user;

decrypting the encrypted authentication string with the received password to produce an authentication string; and

determining whether the user is authenticated based on the decrypting by the computer code for decrypting.

29. The computer readable medium as recited in claim 28, the method further comprising:

permitting access to files protected by the file security system in response to determining that the user is authenticated.

30. The computer readable medium as recited in claim 28, the method further comprising:

denying access to files protected by the file security system in response to determining that the user is not authenticated.

31. A computer readable medium having stored thereon, computer program code that, in response to execution by a computer, causes the computer to re-authenticate a user to a file security system by a method, where the user was previously authenticated to the file security system, the method comprising:

accessing an encrypted authentication string from a server machine associated with the file security system, wherein the encrypted authentication string is associated with the user;

determining whether a re-authorization condition exists; and

re-authenticating the user to the file security system when the re-authorization condition exists, the re-authenticating comprising:

receiving a password associated with the user;

accessing an encrypted authentication string from a server machine associated with the file security system;

decrypting the encrypted authentication string with the received password to produce an authentication string; and

determining whether the user is re-authenticated based on the decrypting by the computer code for decrypting.

32. The computer readable medium as recited in claim 31, the method further comprising:

permitting access to the file security system in response to determining that the user is re-authenticated.

33. The computer readable medium as recited in claim 31, the method further comprising:

denying access to the file security system determining determines that the user is not re-authenticated.

34. A tangible computer readable medium having instructions stored thereon to change a password associated with a file security system, the instructions comprising:

instructions to receive a new password;

instructions to retrieve a stored, existing password associated with the user;

instructions to access an encrypted authentication string from a server machine associated with the file security system, the encrypted authentication string having been created by:

generating a random number of a predetermined length;

converting the random number into the authentication string; and

encrypting the authentication string using the existing password,

wherein the encrypted authentication string is associated with a user;

instructions to decrypt the encrypted authentication string with the existing password to produce a decrypted authentication string; and

instructions to determine whether the user is authenticated based on the decrypting.

35. The tangible computer readable medium as recited in claim 34, the instructions further comprising:

instructions to deny the password to be changed from the existing password to the new password in response to determining that the user is not authenticated.

36. The tangible computer readable medium as recited in claim 34, the instructions further comprising:

instructions to permit the password to be changed from the existing user password to the new password in response to determining that the user is authenticated.

37. A method for authenticating a user to a file security system, wherein the file security system includes a server portion and at least one client portion, the server portion residing in a server machine, and the client portion residing in a client machine, the method comprising:

receiving a login request including at least a password associated with the user;

decrypting an encrypted authentication string with the password received with the login request to produce a decrypted authentication string, the encrypted authentication string having been created using a random number of a predetermined length and encrypted using a previously-received password associated with the user; and

determining whether the user is authenticated based on the decrypting.

38. The method as recited in claim 37, further comprising:

permitting access to files protected by the file security system in response to determining that the user is authenticated.

39. The method as recited in claim 37, further comprising:

denying access to files protected by the file security system in response to determining that the user is not authenticated.

40. A method for authenticating a user to a file security system, the method comprising:

generating a random number of a predetermined length;

converting the random number into an authentication string;

encrypting the authentication string using a previously-received password to produce an encrypted authentication string, wherein the encrypted authentication string and the previously-received password are associated with the user; and

storing the encrypted authentication string in a server machine associated with the file security system for subsequent usage.

41. The method as recited in claim 40, wherein the file security system includes a server portion and at least one client portion, the server portion residing in a server machine, and the client portion residing in a client machine associated with the user, and

further comprising causing the client machine to store the encrypted authentication string associated with the user.

42. The method as recited in claim 40, further comprising storing the encrypted authentication string in the server machine.

43. The method as recited in claim 40, wherein the method is performed on a client machine operating on a client portion of the file security system, and

further comprising causing deletion of the received password after the authentication string is encrypted from memory of the client machine.

44. An article of manufacture including a computer readable medium having instructions stored thereon, that, in response to execution by a computing device, cause the computing device to perform operations for authenticating a user to a file security system, the operations comprising:

generating a random number of a predetermined length;

converting the random number into an authentication string;

encrypting the authentication string using a previously-the received password to produce an encrypted authentication string, wherein the encrypted authentication string and the previously-received password are is associated with the user; and

storing the encrypted authentication string in a server machine associated with the file security system for subsequent usage.

45. A method for authenticating a user to a file security system, wherein the file security system includes a server portion and at least one client portion, the server portion residing in a server machine, and the client portion residing in a client machine, the method comprising:

generating a random number of a predetermined length;

converting the random number into an authentication string;

encrypting the authentication string using a previously-received password associated with a user to produce an encrypted authentication string; and

storing the encrypted authentication string in the file security system to the server machine for subsequent usage.

Description

CROSS-REFERENCE TO RELATED APPLICATION

This application is related to U.S. patent application Ser. No. 10/075,194, filed Feb. 12, 2002, and entitled “SYSTEM AND METHOD FOR PROVIDING MULTI-LOCATION ACCESS MANAGEMENT TO SECURED ITEMS,” which is hereby incorporated by reference for all purposes.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to security systems for data and, more particularly, to security systems that protect data in an inter/intra enterprise environment.

2. Description of Related Art

As organizations become more dependent on networks for business transactions, data sharing and everyday communications, their networks have to be increasingly accessible to customers, employees, suppliers, partners, contractors and telecommuters. Unfortunately, as the accessibility increases, so does the exposure of critical data that is stored on the network. Hackers can threaten all kinds of valuable corporate information resources including intellectual property (e.g., trade secrets, software code and competitive data), sensitive employee information (e.g., payroll figures and HR records), and classified information (e.g., passwords, databases, customer records, product information and financial data).

In protecting the proprietary information traveling across networks, one or more cryptographic techniques are often used to secure a private communication session between two communicating computers on the network. Cryptographic techniques provide a way to transmit information across an unsecure communication channel without disclosing the contents of the information to anyone who may be eavesdropping on the communication channel. An encryption process is a cryptographic technique whereby one party can protect the contents of data in transit from access by an unauthorized third party, yet the intended party can read the data using a corresponding decryption process.

Electronic data is often secured through use of passwords. The passwords can be document level, operating system level or system level. While passwords do provide some security to the electronic data, users tend to mismanage their passwords. For example, users may use short passwords which are easier for an attacker to crack, resulting in possible security breaches of a system. To facilitate the use of passwords, a system has to maintain somewhere information pertaining to the passwords. However, by doing so, the passwords are put in jeopardy of being discovered by an attacker.

Moreover, security policies often request passwords be periodically changed to improve security of a system. Also, in a security system that encrypts data based on user passwords, changing user passwords can be very complicated and result in time consuming updating of all affected encrypted data in the system.

Thus, there is a need for improved approaches to utilize passwords in a security system.

SUMMARY OF THE INVENTION

The invention relates to an improved system and approaches for protecting passwords. A security system for an organization operates to protect the files of the organization and thus prevents or limits users from accessing some or all of the files (e.g., various data and documents) associated with the organization. Passwords are normally required by users seeking to access the files protected by the security system. According to one aspect of the invention, a password entered by a user is used, provided it is authenticated, to obtain a respective authentication string (a relatively longer string of numbers or characters). The retrieved authentication string is then used to enable the user to enter the security system and/or to access secured files therein. According to another aspect of the invention, user passwords are not stored in the security system to avoid security breaches due to unauthorized capture of user passwords.

The present invention may be used in many types of security systems. To facilitate the description of the present invention, unless specifically stated, a security system or a file security system is interchangeably used herein. The invention can be implemented in numerous ways, including as a method, system, device, and computer readable medium. Several embodiments of the invention are discussed below.

As a method for authenticating a user to a file security system, one embodiment of the invention includes at least the acts of: receiving a user-entered password to gain access to files protected by the file security system; generating a random number of a predetermined length; converting the random number into an authentication string; encrypting the authentication string using the user-entered password to produce an encrypted authentication string; and storing the encrypted authentication string in the file security system for subsequent usage.

As a method for authenticating a user to a file security system, another embodiment of the invention includes at least the acts of: receiving a user-entered password to gain access to files protected by the file security system; accessing an encrypted authentication string from the file security system; decrypting the encrypted authentication string with the user-entered password to produce an authentication string; determining whether the user is authenticated; permitting access to the file security system when the determining determines that the user is authenticated; and denying access to the file security system when the determining determines that the user is not authenticated.

As a method for re-authenticating a user to a file security system where the user was previously authenticated to the file security system, one embodiment of the invention includes at least the acts of: determining whether a re-authorization condition exists; and re-authenticating the user to the file security system when the re-authorization condition exists. Further, according to the embodiment, the re-authenticating includes at least the acts of: receiving a user-entered password; accessing an encrypted authentication string from the file security system; decrypting the encrypted authentication string with the user-entered password to produce an authentication string; determining whether the user is re-authenticated; permitting access to the file security system when the determining determines that the user is re-authenticated; and denying access to the file security system when the determining determines that the user is not re-authenticated.

As a method for changing a password of a user, the password being associated with a file security system, one embodiment of the invention includes at least the acts of: receiving a new user-entered password to gain access to files protected by the file security system; receiving an existing user password; accessing an encrypted authentication string from the file security system; decrypting the encrypted authentication string with the existing user password to produce an authentication string; determining whether the user is authenticated; denying the user from changing the password from the existing user password to the new user-entered password when the determining determines that the user is not authenticated; and permitting the user to change the password from the existing user password to the new user-entered password when the determining determines that the user is authenticated. Additionally, the method can further include the act of encrypting the authentication string with the new user-entered password.

As a computer readable medium including at least computer program code for authenticating a user to a file security system, one embodiment of the invention includes at least: computer program code for receiving a user-entered password to gain access to files protected by the file security system; computer program code for generating a random number of a predetermined length; computer program code for converting the random number into an authentication string; computer program code for encrypting the authentication string using the user-entered password to produce an encrypted authentication string; and computer program code for storing the encrypted authentication string in the file security system for subsequent usage.

As a computer readable medium including at least computer program code for authenticating a user to a file security system, another embodiment of the invention includes at least: computer program code for receiving a user-entered password to gain access to files protected by the file security system; computer program code for accessing an encrypted authentication string from the file security system; computer program code for decrypting the encrypted authentication string with the user-entered password to produce an authentication string; computer program code for determining whether the user is authenticated; computer program code for permitting access to the file security system when the computer program code for determining determines that the user is authenticated; and computer program code for denying access to the file security system when the computer program code for determining determines that the user is not authenticated.

As a computer readable medium including at least computer program code for re-authenticating a user to a file security system, where the user was previously authenticated to the file security system, one embodiment of the invention includes at least: computer program code for determining whether a re-authorization condition exists, and computer program code for re-authenticating the user to the file security system when the re-authorization condition exists. Further, according to one embodiment, the computer program code for re-authenticating includes at least: computer program code for receiving a user-entered password; computer program code for accessing an encrypted authentication string from the file security system; computer program code for decrypting the encrypted authentication string with the user-entered password to produce an authentication string; computer program code for determining whether the user is re-authenticated; computer program code for permitting access to the file security system when the computer program code for determining determines that the user is re-authenticated; and computer program code for denying access to the file security system when the computer program code for determining determines that the user is not re-authenticated.

As a computer readable medium including at least computer program code for changing a password of a user, the password being associated with a file security system, one embodiment of the invention includes at least: computer program code for receiving a new user-entered password to gain access to files protected by the file security system; computer program code for receiving an existing user password; computer program code for accessing an encrypted authentication string from the file security system; computer program code for decrypting the encrypted authentication string with the existing user password to produce an authentication string; computer program code for determining whether the user is authenticated; computer program code for denying the user from changing the password from the existing user password to the new user-entered password when the computer program code for determining determines that the user is not authenticated; and computer program code for permitting the user to change the password from the existing user password to the new user-entered password when the computer program code for determining determines that the user is authenticated. Additionally, the computer readable medium can further include computer program code for encrypting the authentication string with the new user-entered password.

Other objects, features, and advantages of the present invention will become apparent upon examining the following detailed description of an embodiment thereof, taken in conjunction with the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:

FIG. 1 is a file security system according to one embodiment of the invention.

FIGS. 2A and 2B are flow diagrams of security system processing according to one embodiment of the invention.

FIG. 3 is a flow diagram of user password setup processing according to one embodiment of the invention.

FIG. 4 is a flow diagram of user authentication processing according to one embodiment of the invention.

FIGS. 5A and 5B are flow diagrams of change password processing according to one embodiment of the invention.

FIG. 6 is a flow diagram of re-authentication processing according to one embodiment of the invention.

FIG. 7 shows a basic security system in which the invention may be practiced in accordance with one embodiment thereof.

FIG. 8 shows an exemplary data structure of a secured file that may be used in one embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

The invention relates to an improved system and approaches for protecting passwords. A file security system for an organization operates to protect the files of the organization and thus prevents or limits users from accessing some or all of the files (e.g., documents) associated with the organization. Passwords are normally required by users seeking to access the files protected by the file security system. According to one aspect of the invention, a password entered by a user is used, provided it is authenticated, to obtain a respective authentication string (a relatively longer string of numbers or characters). The retrieved authentication string is then used to enable the user to enter the file security system and/or to access secured files therein. According to another aspect of the invention, user passwords are not stored in the file security system to avoid security breaches due to unauthorized capture of user passwords. The invention is suitable for use in an enterprise file security system.

A file security system (or document security system) serves to limit access to files (documents) only to authorized users. Often, an organization, such as a company, would use a file security system to limit access to its files (documents). For example, users of a group might be able to access files (documents) pertaining to the group, whereas other users not within the group would not be able to access such files (documents). Such access, when permitted, would allow a user of the group to retrieve a copy of the file (document) via a data network.

Secured files are files that require one or more keys, passwords, access privileges, etc. to gain access to their content. In one embodiment, the security is provided through encryption and access rules. The files, for example, can pertain to documents, multimedia files, data, executable code, images and text. In general, a secured file can only be accessed by authenticated users with appropriate access rights or privileges. In one embodiment, each secured file is provided with a header portion and a data portion, where the header portion contains or points to security information. The security information is used to determine whether access to associated data portions of secured files is permitted.

As used herein, a user may mean a human user, a software agent, a group of users, a member of a group of users, a device and/or application. Besides a human user who needs to access a secured document, a software application or agent sometimes needs to access secured files in order to proceed. Accordingly, unless specifically stated, the “user” as used herein does not necessarily pertain to a human being.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will become obvious to those skilled in the art that the invention may be practiced without these specific details. The description and representation herein are the common meanings used by those experienced or skilled in the art to most effectively convey the substance of their work to others skilled in the art. In other instances, well-known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the present invention.

Reference herein to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Further, the order of blocks in process flowcharts or diagrams representing one or more embodiments of the invention do not inherently indicate any particular order nor imply any limitations in the invention.

Embodiments of the present invention are discussed herein with reference to FIGS. 1-8. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments.

FIG. 1 is a file security system 100 according to one embodiment of the invention. The file security system 100 includes a central server 102 that provides access control to various files (e.g., documents). The access control ensures that only authorized users are able to access the files. Users can interact with the central server 102 through client machines 104, 106 and 108.

The file security system 100 can also make use of one or more local servers 110. The local server 110 illustrated in FIG. 1 serves to locally process some of the access control operations that would otherwise be performed by the central server 102. The presence of the local server 110 allows the client machines 106 and 108 to obtain more reliable and faster service with respect to access control provided by the file security system 100. Hence, the local server 110 is not a necessity but, if provided, can serve to enhance the responsiveness and reliability of the system.

Files are typically secured through encryption and stored in a storage device. For example, files (secured files) can be stored to a storage device 112 that is accessible by any of the client machines 104, 106 and 108 via the central server 102. Additionally, each of the client machines 104, 106 and 108 can provide their own local storage for files (secured files). For example, a user of the client machine 104 may store files pertaining to the user at the client machine 104 as well as at the storage device 112. Regardless of where the secured files are stored, for a user to be permitted access to the secured files, the file security system 100 requires that the user enter a user password at the client machine 104. The user password is then processed to determine whether the user is able to be authenticated. Thereafter, when properly authenticated, the user is thereafter able to access the secured files stored locally or remotely.

The file security system 100 is configured to utilize the user password indirectly. In other words, access to secured files in the file security system 100 is not granted based on a user password provided by an authorized user; instead, access is based on an authenticated string. The authentication string can take various forms. In one embodiment, the authentication string can be 128-bits in length and consist of numbers or characters which can be converted to 32-bytes (256 bits). For example, a user at a client machine would utilize her user password to log into a client machine (e.g., client machine 106). However, the client machine would only temporarily retain the user password in volatile memory (e.g., random access memory (RAM)) and would not use the user password to proceed with the entry to the file security system 100. Instead, the client machine is configured to use an authenticated string that is encrypted using the user password. The encrypted authentication string is stored in non-volatile memory (e.g., a file stored to a disk drive) of the client machine. After the user successfully logs into the client machine, the authenticated string is retrieved (e.g., decrypted with the provided user password) and then used to access the file security system 100 or the secured files therein.

Often, for ease of remembering, a user password pertains to some features related to its user and is relatively short, typically not more than 20 characters. In contrast, an authentication string can be made artificially long and random, such as 101101 . . . 10111 (binary) or AB01F98 . . . 001 (hexadecimal). Cracking an authentication string is much more difficult, if not possible, than cracking a user password. Consequently, access based on an authentication string to the file security system 100 is a lot more secure. Attacks to the file security system 100 by unauthorized users are thus made more difficult because user passwords are only indirectly used. Still further, the file security system 100 is able to easily perform password modifications (or changes) because the authentication string is not altered, though the encrypted authentication string would be altered given a new user password. Moreover, producing the new encrypted authenticated string is computationally easy to perform and thus can be performed quickly, even at run-time if so desired.

FIGS. 2A and 2B are flow diagrams of security system processing 200 according to one embodiment of the invention. The security system processing 200 can be performed locally on a client machine or remotely on a server machine, or partially at the client machine and partially at the server machine. As an example, the client machine can be any of the client machines 104, 106 and 108 illustrated in FIG. 1, and the server machine can be either the central server 102 or the local server 110 illustrated in FIG. 1.

The security system processing 200 initially presents 202 a login window requesting that the user enter a user password. A decision 204 then determines whether a login request has been received. A login request is received when the user has entered the user password into the login window and requested login. When the decision 204 determines that a login request has not yet been received, the security system processing 200 awaits such a request. Once the decision 204 determines that a login request has been received, then a decision 206 determines whether the user is a new user. For example, the login window might also ask for a user identifier or user name, and a mismatch of any data identifying the user would signal that the user is a new user.

In any case, when the decision 206 determines that the user is a new user, then user password setup processing is performed 208 so as to set up the user as an authorized user of the file security system. It is assumed herein that the user (e.g., a new employee) has been authorized to access the file security system. The user password setup processing 208 can be achieved by an administrator or the user him/herself. Following the operation 208, the security system processing 200 returns to the beginning of the security system processing 200 so that the user may then log into the file security system.

On the other hand, when the decision 206 determines that the user is not a new user, then user authentication processing is performed 210 to determine whether the user is able to be successfully authenticated. A decision 212 then determines whether the user has been authenticated. When the decision 212 determines that the user has been successfully authenticated, then the user password is used to obtain a corresponding authentication string. The authentication string is stored or distributed in a secured manner and can only be recovered for use when a correct password is provided. According to one embodiment, the authentication string is encrypted in a file (e.g., xyz.aes when AES is used) and can only be recovered when a correct user password (e.g., passphrase) is provided. Here, the user password, when received via the login request, is temporarily stored in volatile memory (e.g., RAM). Hence, at operation 214, the previously temporarily stored user password is removed (e.g., deleted) from the volatile memory. Next, access to the file security system is permitted 216 since the user has been authenticated and thus is able to be logged into the file security system with the authentication string.

Alternatively, when the decision 212 determines that the user has not been properly authenticated, then access to the file security system is thus denied 220. Following the operation 220, the security system processing 200 ends with access to the file security system being denied.

Following the operation 216, various different operations can be performed by the security system processing 200. Two of various security related operations that are able to be performed before, during or after other operations that the file security system might perform, include password changes and user re-authentication. More particularly, a decision 222 can determine whether a password change is being requested. When the decision 222 determines that a password change is being requested, then change password processing can be performed 224. Alternatively, a decision 226 determines whether user re-authentication is requested. When the decision 226 determines that user re-authentication is requested, then user re-authentication processing is performed 228. Following the operation 228, the security system processing 200 returns to repeat the decision 212 and subsequent operations. Eventually, if no other operations are to be performed, including password change and user re-authentication, the security system processing 200 ends.

FIG. 3 is a flow diagram of user password setup processing 300 according to one embodiment of the invention. The user password setup processing 300 is typically performed when a new user desires to set up a user password and thus be permitted to gain access to certain files within a file security system using the user password.

The user password setup processing 300 generates 302 a random number. Typically, the random number is generated by a random number generator provided by a computing device (e.g., client machine). Normally, the random number would be of a predetermined length. For example, the random number can be 1024 bits. Next, the random number is converted 304 to an authentication string. For example, the random number is a binary numerical value and its conversion into the authentication string involves converting the binary number to a hexadecimal value. As a result, the random number is converted into a string, which itself is a random string. The authentication string is then encrypted 306 using the user password to produce an encrypted authentication string. The user password used in encrypting 306 the authentication string was previously entered by the user. For example, the user might have entered the user password in response to the login window presented 202 during the security system processing 200 shown in FIG. 2A. The encrypted authentication string can also be considered a cipher-text. After the encrypted authentication string has been produced, the encrypted authentication string is stored 308 in a computing system so that the encrypted authentication string can later be retrieved and decrypted with a correct user password. Typically, the file security system is distributed between one or more client machines and one or more server machines. Hence, in one embodiment, the encrypted authentication string is stored 308 to the client machine. For example, the encrypted authentication string can be stored to a file at the client machine. In general, the encrypted authentication string can be stored to a client machine and/or a server machine. Following the operation 308, the user password setup processing 300 is complete and ends.

In effect, the authentication string serves as a password that is rather long and random. Such password can be considered as an indirect password and be used to enter (e.g., log into) the file security system to access secured files, secure files, and other operations involving security (e.g., certificates imports and exports).

FIG. 4 is a flow diagram of user authentication processing 400 according to one embodiment of the invention. The user authentication processing 400 represents processing that can be performed to carry out the operation 210 illustrated in FIG. 2A.

The user authentication processing 400 initially opens 402 a security system file pertaining to the user. The security system file is a file maintained by the file security system that includes the encrypted authentication string associated with the user. For example, the security system file can store the encrypted authentication string due to operation 308 of the user password setup processing 300. Here, the security system file is opened 402 at least when user authentication is to be performed.

After the security system file has been opened 402, an encrypted authentication string associated with the user is retrieved 404 from the security system file. Next, the encrypted authentication string is decrypted 406 using the user password. Note that the user password was previously entered (e.g., during a login request) and can be held in non-volatile memory until the user authentication processing 400 is performed. The result of the decryption 406 of the encrypted authentication string produces an authentication string. A decision 408 then determines whether the decryption 406 of the encrypted authentication string was successful. In other words, the authentication string is used to determine whether the user is able to be properly and correctly authenticated based upon the decryption 406 of the encrypted authentication string with the user password supplied by the user. When the decision 408 determines that decryption of the encrypted authentication string was not successful (i.e., fails) then authentication is deemed 410 to be unsuccessful. On the other hand, when the decision 408 determines that decryption of the encrypted authentication string was successful then authentication is deemed 412 to be successful. Following the operations 410 and 412, the user authentication processing 400 is complete and ends.

FIGS. 5A and 5B are flow diagrams of change password processing 500 according to one embodiment of the invention. The change password processing 500 is, for example, processing performed by the change password processing associated with the operation 224 illustrated in FIG. 2B.

The change password processing 500 initially presents 502 a password change window that requests a new user password (and perhaps an existing password). Typically, the password change window would be presented 502 at a client machine associated with the user. Next, a decision 504 determines whether the password(s) has/have been submitted. When the decision 504 determines that the password(s) have not yet been submitted, then the change password processing 500 awaits such password(s). On the other hand, when the decision 504 determines that the password(s) have been submitted, then the security system file pertaining to the user is opened 506. Next, an encrypted authentication string is retrieved 508 from the security system file. After the encrypted authentication string has been retrieved 508, the encrypted authentication string is then decrypted 510 with the existing user password. The result of the decryption 510 is that an authentication string is produced. A decision 512 then determines whether decryption was successful. Typically, the decryption is successful if the authentication string can be successfully recovered from the security system file with the old password. However, other authentication procedures or system access privileges may additionally be enforced to ensure that the user is permitted to change his/her password. When the decision 512 determines that the decryption was not successful, then the password change request is denied 514 and the change password processing 500 ends.

On the other hand, when the decision 512 determines that decryption was successful, then the authentication string is encrypted 516 using the new user password. The encryption of the authentication string produces a new encrypted authentication string. The new encrypted authentication string is then stored 518. Typically, the new encrypted authentication string would be stored where the old encrypted authentication string was previously stored. In one embodiment, the file containing at least the encrypted authentication string is referred to as a security system file. In one implementation, the storage 518 of the new encrypted authentication string would overwrite the previous encrypted authentication string. Following the operation 518, the change password processing 500 is complete and ends with the password change request having been performed.

FIG. 6 is a flow diagram of re-authentication processing 600 according to one embodiment of the invention. As noted above with respect to FIG. 2B, at times, a file security system may desire to re-authenticate a user. Re-authentication can provide the file security system with additional assurances that the user at the client machine is still the user that was previously authenticated and permitted access to the file security system. Typically, the re-authentication would be required by a file security system prior to performing important security tasks. One example of an important task is exporting a certificate associated with a user to another machine. As another example, a file security system can cause re-authentication to be periodically performed. In any case, when re-authentication is required, the re-authentication processing 600 can represent one embodiment of the user re-authentication processing that is performed at operation 228 of FIG. 2B.

The re-authentication processing 600 initially presents 602 a password re-enter window that requests a user to re-enter their password. A decision 604 then determines whether a user password has been submitted. When the decision 604 determines that a user password has not yet been submitted, the re-authentication processing 600 awaits such a submission. On the other hand, when the decision 604 determines that a password has been submitted, then the security system file pertaining to the user is opened 606. An encrypted authentication string is then retrieved 608 from the security system file. Here, the security system file is a file maintained by the file security system that includes at least an encrypted authentication string. In one embodiment, the security system file includes only the encrypted authentication string. In another embodiment, the security system file includes other information besides the encrypted authentication string and thus the retrieval can involve parsing the security system file to acquire the encrypted authentication string. Next, the authentication string is decrypted 610 from the security system file with the user password. The result of the decryption 610 is an authentication string that is used to authenticate the user, and allow the user to continue access to the secured files in the file security system.

FIG. 7 shows a basic security system 700 in which the invention may be practiced in accordance with one embodiment thereof. The security system 700 may be employed in an enterprise or inter-enterprise environment having a network A 708 and a network B 710. It includes a first server 706 (also referred to as a central server) providing centralized access management for the enterprise. The first server 706 can control restrictive access to files secured by the security system 700. To provide dependability, reliability and scalability of the system, one or more second servers 704 (also referred to as local servers, of which one is shown) may be employed to provide backup or distributed access management for users of client machines serviced locally. For illustration purposes, there are two client machines 701 and 702 being serviced by a local server 704. Alternatively, one of the client machines 701 and 702 may be considered as a networked storage device.

Secured files may be stored in either one of the devices 701, 702, 704, 706 and 712. When a user of the client machine 701 attempts to exchange a secured file with a remote destination 712 being used by an external user, one or more of the processing 200, 300, 400, 500, and 600 discussed above can be activated and be performed by the security system 700.

FIG. 8 shows an exemplary data structure 820 of a secured file that may be used in one embodiment of the invention. The data structure 820 includes two portions: a header (or header portion) 822 and encrypted data (or an encrypted data portion) 824. The header 822 can be generated in various forms depending on implementation. In one embodiment, the header 822 includes security information 826 that may further include a number of access rules 829 and a file key 830 and thus provides restrictive access to the data portion 824 which is an encrypted version of a plain file. Optionally, the data structure 820 may also include an error-checking portion 825 that stores one or more error-checking codes, for example, a separate error-checking code for each block of encrypted data 824. These error-checking codes may also be associated with a Cyclical Redundancy Check (CRC) for the header 822 and/or the encrypted data 824. The header 822 includes a flag bit or signature 827 and security information 826 that is in accordance with the security template for the store.

The security information 826 can vary depending upon implementation. However, as shown in FIG. 8, the security information 826 includes a user identifier (ID) 828, access policy (access rules) 829, a file key 830 and other information 831. Although multiple user identifiers may be used, a user identifier 828 is used to identify a user or a group that is permitted to access the secured file. The access rules 829 provide restrictive access to the encrypted data portion 824. The file key 830 is a cipher key that, once obtained, can be used to decrypt the encrypted data portion 824 and thus, in general, is protected. In one implementation of the data structure 820, the file key 830 is encrypted in conjunction with the access rules 829. In another implementation of the data structure 820, the file key 830 is double encrypted with a protection key and further protected by the access rules 829. The other information 831 is an additional space for other information to be stored within the security information 826. For example, the other information 831 may be used to include other information facilitating secure access to the secured file, such as version number or author identifier.

According to one embodiment, the above-noted encrypted authentication strings can be provided on a per-user or a per-group of users basis. With the appropriate user or group password, the encrypted authentication string can be successfully decrypted and utilized internal to the file security system as a password. In other words, the authentication string is used as a password for access to the file security system or the secured files therein.

Additional details on a security system can be found in U.S. patent application Ser. No. 10/075,194, filed Feb. 12, 2002, and entitled “SYSTEM AND METHOD FOR PROVIDING MULTI-LOCATION ACCESS MANAGEMENT TO SECURED ITEMS,” which is hereby incorporated by reference for all purposes.

The invention is preferably implemented by software or a combination of hardware and software, but can also be implemented in hardware. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of tangible computer readable media include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, and optical data storage devices. Examples of transmission media include carrier waves. Computer readable code from the tangible computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

The various embodiments, implementations and features of the invention noted above can be combined in various ways or used separately. Those skilled in the art will understand from the description that the invention can be equally applied to or used in other various different settings with respect to various combinations, embodiments, implementations or features provided in the description herein.

The advantages of the invention are numerous. Different embodiments or implementations may yield one or more of the following advantages. One advantage of the invention is that user passwords are only stored in a transient manner, thus minimizing opportunities for unauthorized persons to crack the user passwords. Another advantage of the invention is that indirect passwords are used in place of passwords. The indirect passwords are normally be longer and more random, thus making an attack on passwords much more difficult. Still another advantage of the invention is that password modifications are able to be easily achieved by file security systems that protect secured files (e.g., documents) using indirect passwords. Yet still another advantage of the invention is that open software can be given an indirect password so as not to compromise a user password.

The many features and advantages of the present invention are apparent from the written description, and thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.

Maintaining a first session on a first computing device and subsequently connecting to the first session via different computing devices and adapting the first session to conform to the different computing devices system configurations