Method and system for enabling users of a group shared across multiple file security systems to access secured files

[0001] This application is related to U.S. patent application Ser. No. 10/262,218, filed Sep. 30, 2002, and entitled “DOCUMENT SECURITY SYSTEM THAT PERMITS EXTERNAL USERS TO GAIN ACCESS TO SECURED FILES,” which is hereby incorporated by reference for all purposes. This application is also 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.

[0002] 1. Field of the Invention

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

[0004] 2. Description of Related Art

[0005] The Internet is the fastest growing telecommunications medium in history. This growth and the easy access it affords have significantly enhanced the opportunity to use advanced information technology for both the public and private sectors. It provides unprecedented opportunities for interaction and data sharing among businesses and individuals. However, the advantages provided by the Internet come with a significantly greater element of risk to the confidentiality and integrity of information. The Internet is an open, public and international network of interconnected computers and electronic devices. Without proper security measures, an unauthorized person or machine may intercept any information traveling across the Internet, and may even get access to proprietary information stored in computers that interconnect to the Internet, but are otherwise generally inaccessible by the public.

[0006] 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 prerelease 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). Thus data security is becoming increasingly mission-critical.

[0007] There are many efforts in progress aimed at protecting proprietary information traveling across the Internet and controlling access to computers carrying the proprietary information. Every day hundreds of millions of people interact electronically, whether it is through e-mail, e-commerce (business conducted over the Internet), ATM machines or cellular phones. The perpetual increase of information transmitted electronically has led to an increased reliance on cryptography.

[0008] In protecting the proprietary information traveling across the Internet, one or more cryptographic techniques are often used to secure a private communication session between two communicating computers on the Internet. Cryptographic techniques provide a way to transmit information across an unsecure communication channel without disclosing the contents of the information to anyone 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.

[0009] Many organizations have deployed firewalls, Virtual Private Networks (VPNs), and Intrusion Detection Systems (IDS) to provide protection. Unfortunately, these various security means have been proven insufficient to reliably protect proprietary information residing on their internal networks. For example, depending on passwords to access sensitive documents from within often causes security breaches when the password of a few characters long is leaked or detected.

[0010] Enterprise security solutions secure data within an enterprise premise (e.g., internal networks). Some enterprise security solutions prohibit external users (clients) to have any access to secured data. However, users of different enterprises often need to access the same set of electronic files. Unfortunately, each enterprise security solution conventionally only permits its own authorized users to access its secured files. Hence, users of different enterprises are not able to be members of a shared group of users and thus cannot easily share secured files.

[0011] Thus, there is a need for improved approaches to enable file security systems to permit users of different enterprise security systems to access secured data without compromising the integrity of the enterprise security systems.

[0012] Generally speaking, the invention relates to an improved system and approaches for permitting users of different organizations to access secured files (e.g., documents). These users can be part of a group that is shared across a plurality of file security systems. For example, at a first file security system, a user of the shared group can secure a file for restricted access by those users within the shared group. Subsequently, at a different file security system, another user of the shared group is able to access the contents of the secured file.

[0013] 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.

[0014] As a security system that restricts access to electronic files, one embodiment of the invention includes at least: a first file security system of a first business entity that secures electronic files for restricted access by those users within a shared group; and a second file security system of a second business entity that secures electronic files for restricted access by those users within the shared group. The users within the shared group include at least one user from the first business entity and at least one user from the second business entity.

[0015] As a method for interacting between file security systems, one embodiment of the invention includes at least: creating a shared group at a first file security system; adding a second file security system to the shared group; permitting one or more users of the first file security system to be within the shared group; and permitting one or more users of the second file security system to be within the shared group.

[0016] As a computer readable medium including at least computer program code for interacting between file security systems, one embodiment of the invention includes at least: computer program code for creating a shared group at a first file security system; computer program code for adding a second file security system to the shared group; computer program code for permitting one or more users of the first file security system to be within the shared group; and computer program code for permitting one or more users of the second file security system to be within the shared group.

[0017] 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.

[0027] The invention relates to an improved system and approaches for permitting users of different organizations to access secured files (e.g., documents). These users can be part of a group that is shared across a plurality of file security systems. For example, at a first file security system, a user of the shared group can secure a file for restricted access by those users within the shared group. Subsequently, at a different file security system, another user of the shared group is able to access the contents of the secured file. The different organizations typically represent different enterprises (e.g., companies).

[0028] In general, a file security system (or document security system) serves to limit access to files (documents) 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. According to one aspect of the invention, the users of the group can be associated with different file security systems.

[0029] Secured files are files that require one or more keys, passwords, access privileges, etc. to gain access to their content. According to one aspect of the invention, the security is provided through encryption and access rules. The files, for example, can pertain to documents, multimedia files, data, executable code, images 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.

[0030] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the 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 representations used herein are the common means 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 invention.

[0031] 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 of the invention.

[0032] 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.

[0033] FIG. 1 is a block diagram of an arrangement 100 of file security systems according to one embodiment of the invention. The arrangement 100 includes a first file security system 102, a second file security system 104 and a third file security system 106. The file security systems 102, 104 and 106 are connected or connectable to a data network 108. In one implementation, the different file security systems are associated with different business entities.

[0034] Each of the file security systems 102, 104 and 106 operate to secure electronic files (e.g., electronic documents) and then restrict access to the secured electronic files. Further, each of the file security systems 102, 104 and 106 supports use by multiple users and may provide at least a central server for each file security system and potentially other servers within the respective file security system. However, instead of central servers, the file security systems 102, 104 and 106 can communicate in a peer-to-peer manner. In other words, each file security system 102, 104 and 106 operates primarily independently to secure its domain of electronic files. Nevertheless, according to the invention, to facilitate sharing of certain electronic files between the different file security systems, a shared group is utilized. Any electronic file that has been secured for use by members of the shared group can access the secured electronic file, regardless of which of the different file security systems the users are associated with.

[0035] More particularly, the first file security system 102 includes a shared group 110. The shared group 110 has certain users SG_A 112 that are members of the shared group 110. These users SG_A 112 are affiliated with the first file security system 102. Hence, it is these users SG_A 112 that are able to access the electronic files that are made available to members of the shared group. In doing so, the users SG_A 112 that are members of the shared group are able to receive certain keys 114 that are utilized by the users SG_A 112 to encrypt and decrypt electronic files for access only by members of the shared group. The first file security system 102 also includes a shared group administrator module 116. The shared group administrator module 116 operates to enable an administrator of the first file security system 102 to manage creation of the shared group, admission of a file security system into the shared group, removal of a file security system from the shared group, or transfer of the administrative tasks to another of the file security systems within the shared group.

[0036] The second file security system 104 includes a shared group 118. The shared group 118 has certain users SG_B 120 that are affiliated with the second file security system 104. These users SG_B 120 are, in effect, members of the same group as the users SG_A 112. That is, the shared groups 110 and 118 are portions of the same shared group. Further, the second file security system 104 includes certain keys 122 that are utilized by the users SG_B 120 to encrypt and/or decrypt electronic files for access only by the members of the shared group.

[0037] The third file security system 106 includes a shared group 124. The shared group 124 has certain users SG_C 126 that are members of the shared group 124. These users SG_C 126 are affiliated with the third file security system 106. The shared group 124 is the same shared group as the shared group 110 and the shared group 118. Also, the third file security system 106 includes certain keys 128 that are utilized by the users SG_C 126 in order to encrypt and/or decrypt electronic files for access only by the members of the shared group. The keys 114, 118, and 128 used by the shared group are normally identical.

[0038] FIG. 2 is a block diagram of a pair of file security systems 200 according to one embodiment of the invention. The pair of file security systems 200 includes a first file security system 202 and a second file security system 204. In general, the file security systems 202 and 204 operate to restrict access to electronic files. For example, the first file security system 202 can, for example, be configured as the first file security system 102 illustrated in FIG. 1, and the second file security system 204 can, for example, be configured as the second file security system 104 illustrated in FIG. 1. Typically the first file security system 202 and the second file security system 204 operate independently. However, 202 and 204 can perform limited communication. This limited communication can be used to manage the utilization of one or more shared groups between the file security systems 202 and 204. To ensure secure communication between 202 and 204, which are typically in different companies, trust can be established bilaterally or through a trusted third party 206 using authentication methods well known to those in the art. The various management activities with respect to shared groups are discussed in more detail below with respect to FIGS. 3-6 but can, for example, generally include one or more of: setting up a shared group, adding members to a shared group, removing member from a shared group, and setting up or transferring a shared group administrator.

[0039] Further, as illustrated in FIG. 2, the first file security system 202 can couple to a key store 208 that stores a plurality of cryptographic keys that are utilized by the first file security system 202. The keys can be symmetric or public-private key pairs. The first file security system 202 allows a plurality of users 210 to interact therewith to secure electronic files for restricting access or to unsecure previously secured electronic files for gaining access. As an example, users 210 can have accounts with the first file security system 202 such that they can secure electronic files using the first file security system or access secured electronic files as appropriate given the access restrictions placed on electronic files.

[0040] The second file security system 204 also couples to a key store 212 that stores a plurality of cryptographic keys that are utilized by the second file security system. Again, the keys can be symmetric or public-private key pairs. Also, the second file security system 204 permits a plurality of users 214 to have user accounts with the second file security system 204 and thus access secure electronic files as appropriate given the access restrictions placed on electronic files. Electronic files having their access restricted to those users within the shared group can be accessed by any of the users within the shared group, regardless of whether they are users affiliated with the first file security system 202 or the second file security system 204. For example, if user 1-A and user 2-C shown in FIG. 2 are members of the same shared group, then user 2-C could access the content of (decrypt) an electronic file previously secured (encrypted) by user 1-A.

[0041] FIG. 3 is a flow diagram of shared group setup processing 300 according to one embodiment of the invention. The shared group setup processing 300 is performed by a file security system. In one example, the shared group setup processing 300 is performed by the first file security system 102 illustrated in FIG. 1. Namely, the shared group setup processing 300 can be performed by the shared group administrator module 116 as illustrated in FIG. 1.

[0042] The shared group setup processing 300 initially creates 302 a shared group. A shared group is a group of one or more users affiliated with one or more different file security systems. Typically, a shared group is a group that is shared across multiple file security systems. Each of the one or more different file security systems can permit one or more of its own users to be within the shared group.

[0043] Once the shared group has been created 302, another file security system (that is to be included within the shared group) is invited 304 to join the shared group. The invitation offers the other file security system the opportunity to join the shared group. Here, in general, one or more file security systems can be invited 304 to join the shared group. After the other file security system has been invited 304 to join the shared group, a decision 306 determines whether the other file security system that has been invited has accepted the invitation to join the shared group. In other words, the decision 306 determines whether an acceptance of the invitation has been received. When the decision 306 determines that an acceptance has not yet been received, then a decision 308 determines whether a denial (i.e., non-acceptance) or a time-out has occurred. When the decision 308 determines that a denial has not been received and that a time-out has not yet been reached, then the shared group setup processing 300 returns to repeat the decision 306 to continue to wait for a response to the invitation. The response to the invitation can be either an acceptance or a denial. When the decision 308 determines that a denial has been received or that a time-out has occurred, then the shared group setup processing 300 is complete and ends because the other file security system that has been invited to join the shared group has either denied (i.e., refused) the invitation or not timely responded to the invitation.

[0044] On the other hand, when the decision 306 determines that an acceptance has been received from the other file security system, then one or more cryptographic keys are provided 310 to the other file security system. The cryptographic keys are eventually used by the users of the other file security system that are members of the shared group when securing or accessing the content of electronic files to be accessible by the shared group. Following the operation 310, the shared group setup processing 300 is complete and ends.

[0045] FIG. 4 is a flow diagram of termination processing 400 according to one embodiment of the invention. The termination processing 400 is performed by a file security system having shared group administrative operations for the shared group. The termination processing 400 can, for example, be performed by the first file security system 102 illustrated in FIG. 1. Namely, the termination processing 400 can be performed by the shared group administrator module 116 as illustrated in FIG. 1.

[0046] The termination processing 400 initially identifies 402 a participant file security system to be removed from the shared group. For whatever reason, the identified participant file security system is to be removed from the shared group. Hence, the identified participant file security system is notified 404 of their imminent removal from the shared group.

[0047] Next, a decision 406 determines whether the identified participant file security system has indicated acceptance of their removal from the shared group. When the decision 406 determines that such acceptance has not yet been received, then a decision 408 determines whether a delay period has been exceeded. When the decision 408 determines that the delay period has not been exceeded, then the termination processing 400 returns to repeat the decision 406 and subsequent operations.

[0048] On the other hand, when the decision 406 indicates that such acceptance has been received from the identified participant file security system, as well as following the decision 408 when the delay period has been exceeded, the identified participant file security system is removed 410 from the shared group. In other words, the shared group has been modified at this point such that any users of the identified participant file security system that were previously entitled to access electronic files associated with the shared group are no longer able to access any newly created electronic files secured by such means. As a result, the users of the identified participant file security system that were associated with the shared group are no longer members of the shared group. In one embodiment, these users, however, remain eligible to access previously created and secured electronic files that were so created and secured while the users of the participant file security system were members of the shared group.

[0049] Following or concurrent with the removal 410 of the identified participant file security system from the shared group, new cryptographic keys for the shared group are acquired 412. The remaining participant file security systems are informed and provided 414 with the new cryptographic keys. In other words, the cryptographic keys used by the file security systems affiliated with the shared group are changed (e.g., rotated), such that, going forward, new cryptographic keys are utilized to secure and subsequently unsecure electronic documents affiliated with the shared group. Following the operation 414, the termination processing 400 is complete and ends.

[0050] FIGS. 5A and 5B are flow diagrams of administrative transfer processing 500 according to one embodiment of the invention. The administrative transfer processing 500 transfers shared group administrative responsibilities from one file security system to another. The administrative transfer processing 500 can, for example, be performed by the first file security system 102 illustrated in FIG. 1. Namely, the administrative transfer processing 500 can be performed by the shared group administrator module 116 as illustrated in FIG. 1.

[0051] The administrative transfer processing 500 initially identifies 502 a participant file security system to host a shared group administrator. Typically, a shared group has a plurality of participant file security systems. At any given point in time, one of the participant file security systems hosts the administrator for the shared group, namely, the shared group administrator. With respect to the arrangement 100 of the file security systems shown in FIG. 1, the shared group administrator is, for example, the shared group administrator 116 the first file security system 102. With respect to FIG. 1, the participant file security system being identified 502 would be the second file security system 104 or the third file security system 106.

[0052] Next, a decision 504 determines whether there are any actions pending with respect to the shared group administrator. As long as there are actions that are pending, the administrative transfer processing 500 awaits completion of such actions. Once the decision 504 determines that there are no pending actions, then an administrator transfer request is sent 506 to the identified participant file security system. Here, the file security system to be the recipient of the administrative responsibilities for the shared group is sent 506 the administrator transfer request. Typically, the administrator transfer request is sent 506 by the shared group administrator at the host file security system to the identified participant file security system. For example, the shared group administrator 116 of the first file security system 102 shown in FIG. 1 can send 506 the request.

[0053] Next a decision 508 determines whether the identified participant file security system that has been sent 506 the administrator transfer request has accepted the administrator transfer request. Typically, an administrator for the identified participant file security system that has received the administrator transfer request determines whether or not to accept the transfer. When the decision 508 determines that the identified participant file security system declines to host the shared group administrator, then the administrative transfer processing 500 is complete and ends because the requested administrative transfer has been declined by the recipient file security system.

[0054] On the other hand, when the decision 508 determines that the identified participant file security system has accepted the administrative transfer request of the shared group administrator, the administrative transfer processing 500 continues. In this regard, other participant file security systems are notified 510 of the new shared group administrator. Next, a decision 512 determines whether the other participant file security systems have acknowledged receiving the notifications. Here, in one embodiment, the administrative transfer processing 500 requires all of the other participant file security systems to acknowledge their receipt of the notification of the new shared group administrator. Hence, when the decision 512 determines that all acknowledgements have not been received, a decision 514 determines whether a delay period has been exceeded. When the decision 514 determines that a delay period has been exceeded, then the administrative transfer processing 500 notifies 516 the other participant file security systems that the administrative transfer attempt has failed, and thus the current administrator remains. Following the operation 516, the administrative transfer processing 500 is complete and ends without implementing the requested administrative transfer because the other participant file security systems did not acknowledge the change. On the other hand, when the decision 514 determines that the delay period has not been exceeded, then the administrative transfer processing 500 returns to repeat the decision 512 and subsequent operations.

[0055] Alternatively, once the decision 512 determines that all of the acknowledgements from the other participant file security systems have been received, the administrator transfer to the new shared group administrator is invoked 516. In this regard, the new shared group administrator (or shared group administrative module) is activated in the identified participant file security system, while the previous shared group administrator (or shared group administrative module) from a different file security system is deactivated. Then, a confirmation of the administrative transfer to the identified participant file security system is sent 518. Following the operation 518, the administrative transfer processing 500 is complete and ends.

[0056] FIG. 6 is a flow diagram of withdrawal processing 600 according to one embodiment of the invention. The withdrawal processing 600 enables a participant file security system to withdraw from its group membership. The withdrawal processing 600 can, for example, be performed by the first file security system 102 illustrated in FIG. 1. Namely, the termination processing 400 can be performed by the shared group administrator module 116 as illustrated in FIG. 1.

[0057] The withdrawal processing 600 initially receives 602 a request to withdraw from the shared group. Here, the request to withdraw from the shared group is received at the file security system hosting the shared group administrator from a different file security system that is currently within the shared group. After the request to withdraw from the shared group has been received 602, the requesting file security system is removed 604 from the shared group. Here, in one embodiment, it is assumed that when the request to withdraw from the shared group is received, that the shared group administrator at the host file security system will accept such request and promptly process such. In other words, the removal 604 causes the shared group to be modified such that any users of the requesting participant file security system that were previously entitled to access electronic files associated with the shared group are no longer able to access any newly created and secured electronic files associated with the shared group. As a result, the users of the requesting file security system that were associated with the shared group are no longer members of the shared group. In one embodiment, these users, however, remain eligible to access previously created and secured electronic files that were so created and secured while the users of the requesting file security system were members of the shared group.

[0058] Further, once the request to withdraw is accepted and processed, the file security system being withdrawn can modify its configuration such that the shared group being withdrawn from is no longer available as a selectable item at the remaining participant file security systems of the shared group. In other words, the users of the withdrawn file security system can no longer encrypt electronic files for use by the shared group. However, in some embodiments, previously encrypted files associated with the shared group are still able to be accessed by prior users/members of the shared group via the withdrawn file security system.

[0059] Following or concurrent with the removal 604 of the withdrawing file security system from the shared group, new cryptographic keys for the shared group are acquired 606. The remaining participant file security systems are informed and provided 608 with the new cryptographic keys. In other words, the cryptographic keys used by the file security systems affiliated with the shared group are changed (e.g., rotated), such that, going forward, new cryptographic keys are utilized to secure and subsequently access content of electronic files affiliated with the shared group.

[0060] Here, since a file security system is being removed/withdrawn from the shared group, the security or cryptographic keys utilized to encrypt and decrypt electronic files for use by the shared group are altered (e.g., rotated) such that all remaining participant file security systems receive the new keys. Hence, the withdrawn file security system does not receive the new cryptographic keys, and thus is prevented from thereafter encrypting or decrypting any additional electronic files with respect to the shared group. Finally, an acknowledgement of withdrawal from the shared group can be sent 610 to the withdrawing file security system. Following the operation 610, the withdrawal processing 600 is complete and ends.

[0061] 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. 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 or 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.

[0062] Secured files may be stored in any 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 300, 400, 500 and 600 discussed above are activated to ensure that the requested secure file is delivered without compromising the security imposed on the secured file.

[0063] 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 accordance with a security template associated with a data store 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. According to one embodiment, the security information 826 is encrypted and can be decrypted with a user key associated with an authenticated user (or requestor).

[0064] 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.

[0065] 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 the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, optical data storage devices, and carrier waves. The 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.

[0066] 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.

[0067] 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 file security systems are able to protect secured files (e.g., documents) that are able to be shared by members of different file security systems. Another advantage of the invention is that a file security system can permit groups of users across different file security systems to access certain secured files (e.g., secured documents) associated with the group. In one embodiment, access to the secured files by any user of the group is transparent to the user. Still another advantage of the invention is that a group of users across different file security systems can be administrated from one of the file security systems.

[0068] The foregoing description of embodiments is illustrative of various aspects/embodiments of the present invention. Various modifications to the present invention can be made to the preferred embodiments by those skilled in the art without departing from the true spirit and scope of the invention as defined by the appended claims. Accordingly, the scope of the present invention is defined by the appended claims rather than the foregoing description of embodiments.