US 7,562,232 B2Grant
System and method for providing manageability to security information for secured items
Issue Date:2009-07-14
•32 Claims
•12 Drawing Sheets
Abstract
Improved approaches for accessing secured digital assets (e.g., secured items) are disclosed. In general, digital assets that have been secured (secured digital assets) can only be accessed by authenticated users with appropriate access rights or privileges. Each secured digital asset is provided with a header portion and a data portion, where the header portion includes a pointer to separately stored security information. The separately stored security information is used to determine whether access to associated data portions of secured digital assets is permitted. These improved approaches can facilitate the sharing of security information by various secured digital assets and thus reduce the overall storage space for the secured digital assets. These improved approaches can also facilitate efficient management of security for digital assets.
Metadata
Inventors
- Patrick Zuili
- Klimenty Vainstein
Application Information
Application Number:US 10/206,486
Filing Date:2002-07-25
Priority Date:2001-12-12
Art Unit:2431
Classifications
IPC:
G06F11/30G06F12/14G06F7/04G06F17/30H04L9/32G06K9/00G11C7/00G06F11/00G06F12/16G06F15/18
Patent Drawings (12 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation application of U.S. patent application Ser. No. 10/132,712, filed Apr. 26, 2002, and entitled “SYSTEM AND METHOD FOR PROVIDING MANAGEABILITY TO SECURITY INFORMATION FOR SECURED ITEMS,” (now abandoned) which is a continuation-in-part application of 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,” and which claims the benefit of U.S. Provisional Application No. 60/339,634 filed Dec. 12, 2001, and entitled “PERVASIVE SECURITY SYSTEM,” all of which are hereby incorporated by reference for all purposes.
Background of the Invention
[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 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 a widely open, public and international network of interconnected computers and electronic devices. Without proper security means, an unauthorized person or machine may intercept any information traveling across the Internet and even get access to proprietary information stored in computers that interconnect to the Internet, but are otherwise generally inaccessible by the public.
[0006] There are many efforts in progress aimed at protecting proprietary information traveling across the Internet and controlling access to computers carrying the proprietary information. Cryptography allows people to carry over the confidence found in the physical world to the electronic world, thus allowing people to do business electronically without worries of deceit and deception. Every day hundreds of thousands 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 lead to an increased reliance on cryptography.
[0007] One of the ongoing efforts in protecting the proprietary information traveling across the Internet is to use one or more cryptographic techniques to secure a private communication session between two communicating computers on the Internet. The 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. Using an encryption process in a cryptographic technique, one party can protect the contents of the data in transit from access by an unauthorized third party, yet the intended party can read the data using a corresponding decryption process.
[0008] A firewall is another security measure that protects the resources of a private network from users of other networks. However, it has been reported that many unauthorized accesses to proprietary information occur from the inside, as opposed to from the outside. An example of someone gaining unauthorized access from the inside is when restricted or proprietary information is accessed by someone within an organization who is not supposed to do so. Due to the open nature of the Internet, contractual information, customer data, executive communications, product specifications, and a host of other confidential and proprietary intellectual property remains available and vulnerable to improper access and usage by unauthorized users within or outside a supposedly protected perimeter.
[0009] Many businesses and organizations have been looking for effective ways to protect their proprietary information. Typically, businesses and 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 private 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. Therefore, there is a need to provide more effective ways to secure and protect resources on private networks.
Summary of the Invention
[0010] The invention relates to improved approaches for accessing secured digital assets (e.g., secured items). In general, digital assets that have been secured (secured digital assets) can only be accessed by authenticated users with appropriate access rights or privileges. Each secured digital asset is provided with a header portion and a data portion, where the header portion includes a pointer to separately stored security information. The separately stored security information is used to determine whether access to associated data portions of secured digital assets is permitted. These improved approaches can facilitate the sharing of security information by various secured digital assets and thus reduce the overall storage space for the secured digital assets. These improved approaches can also facilitate efficient management of security for the secured digital assets.
[0011] 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.
[0012] As a method for accessing a secured file, one embodiment of the invention includes at least the acts of: obtaining the secured file to be accessed, the secured file having a header portion and a data portion; retrieving a security information pointer from the header portion of the secured file; obtaining security information for the secured file using the security information pointer; and permitting access to the secured file to the extent permitted by the security information.
[0013] As a computer readable medium including at least computer program code for accessing a secured item, one embodiment of the invention includes at least: computer program code for obtaining the secured item to be accessed, the secured item having a header portion and a data portion; computer program code for retrieving a security information pointer from the header portion of the secured item; computer program code for obtaining security information for the secured item using the security information pointer; and computer program code for permitting access to the secured item to the extent permitted by the security information.
[0014] As a system for accessing a secured item, where the secured item has a header portion and an encrypted data portion, and where the header portion includes at least a pointer and an encrypted key, one embodiment of the invention includes at least: a storage device that stores security information for a plurality of different secured items, the pointer serving to locate the security information associated with secured item; a first decryption module that receives the encrypted key from the header portion of the secured item and decrypts the encrypted key to obtain a key; an access analyzer that determines whether the encrypted data portion is permitted to be accessed by a requestor based on the security information; and a second decryption module that decrypts the encrypted data portion using the key to produce an unencrypted data portion that the requestor is able to access, provided the access analyzer determines that the encrypted data portion is permitted to be accessed by a requestor.
[0015] As a data structure for a secured file, one embodiment of the invention includes at least a header portion and a data portion. The header portion contains at least a pointer to separately stored security information and a key. At least the key portion of the header portion is encrypted. The data portion contains at least encrypted data of the secured file.
[0016] 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
[0017] These and other features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims, and accompanying drawings wherein:
[0018] FIG. 1A shows a basic system configuration in which the invention may be practiced in accordance with an embodiment thereof.
[0019] FIG. 1B shows internal construction blocks of a computing device in which the invention may be implemented and executed.
[0020] FIG. 2A is a block diagram of securing a created document.
[0021] FIG. 2B is a block diagram of a secured item access system according to one embodiment of the invention.
[0022] FIG. 2C is a diagram of a representative data structure for a secured file.
[0023] FIG. 3 is a flow diagram of secured document access processing according to one embodiment of the invention.
[0024] FIG. 4A illustrates a data organization item according to one embodiment of the invention.
[0025] FIG. 4B illustrates exemplary tables for use with the data organization illustrated in FIG. 4A .
[0026] FIG. 5 is a block diagram of a file security management system according to one embodiment of the invention.
[0027] FIGS. 6A and 6B are flow diagrams of secured file portability processing according to one embodiment of the invention.
Detailed Description of the Invention
[0028] The present invention relates to improved approaches for accessing secured digital assets (e.g., secured items). In general, digital assets that have been secured (secured digital assets) can only be accessed by authenticated users with appropriate access rights or privileges. Each secured digital asset is provided with a header portion and a data portion, where the header portion includes a pointer to separately stored security information. The separately stored security information is used to determine whether access to associated data portions of secured digital assets is permitted. These improved approaches can facilitate the sharing of security information by various secured digital assets and thus reduce the overall storage space for the secured digital assets. These improved approaches can also facilitate efficient management of security for the secured digital assets.
[0029] Digital assets may include, but not be limited to, various types of documents, multimedia files, data, executable code, images and text. In the context of the present invention, digital assets may also include directories/folders as well as any OS-addressable resources (e.g. a thread to a port, or a device). The present invention is particularly suitable in an inter/intra enterprise environment.
[0030] 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 present invention may be practiced without these specific details. The description and representation 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 present 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 in the invention.
[0032] Embodiments of the present invention are discussed herein with reference to FIGS. 1A-6B . 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. 1A shows a basic system configuration in which the present invention may be practiced in accordance with one embodiment thereof. Documents or files may be created using an authoring tool executed on a client computer 100, which may be a desktop computing device, a laptop computer, or a mobile computing device. Exemplary authoring tools may include application programs such as Microsoft Office (e.g., Microsoft Word, Microsoft PowerPoint, and Microsoft Excel), Adobe FrameMaker and Adobe Photoshop.
[0034] According to one embodiment, the client computer 100 is loaded with a client module that is a linked and compiled, or interpreted, version of one embodiment of the present invention and is capable of communicating with a server 104 or 106 over a data network (e.g., the Internet or a local area network). According to another embodiment, the client computer 100 is coupled to the server 104 through a private link. As will be further explained below, a document or file created by an authoring tool can be secured by the client module. The client module, when executed, is configured to ensure that a secured document is secured at all times in a store (e.g., a hard disk or other data repository). The secured documents can only be accessed by users with proper access privileges. In general, an access privilege or access privileges for a user may include, but not be limited to, a viewing permit, a copying permit, a printing permit, an editing permit, a transferring permit, an uploading/downloading permit, and a location permit.
[0035] According to one embodiment, a created document is caused to go through an encryption process that is preferably transparent to a user. In other words, the created document is encrypted or decrypted under the authoring application so that the user is not aware of the process. A key (referred to herein as a user key) can be used to retrieve a file key to decrypt an encrypted document. Typically, the user key is associated with an access privilege for the user or a group of users. For a given secured document, only a user with a proper access privilege can access the secured document.
[0036] In one setting, a secured document may be uploaded via the network 110 from the computer 100 to a computing or storage device 102 that may serve as a central repository. Although not necessary, the network 110 can provide a private link between the computer 100 and the computing or storage device 102. Such link may be provided by an internal network in an enterprise or a secured communication protocol (e.g., VPN and HTTPS) over a public network (e.g., the Internet). Alternatively, such link may be simply provided by a TCP/IP link. As such, secured documents on the computer 100 may be remotely accessed.
[0037] In another setting, the computer 100 and the computing or storage device 102 are inseparable, in which case the computing or storage device 102 may be a local store to retain secured documents or receive secured network resources (e.g., dynamic Web contents, results of a database query, or a live multimedia feed). Regardless of where the secured documents or secured sources are actually located, a user, with proper access privilege, can access the secured documents or sources from the computer 100 or the computing or storage device 102 using an application (e.g., Internet Explorer, Microsoft Word or Acrobat Reader).
[0038] The server 104, also referred to as a local server, is a computing device coupled between a network 108 and the network 110. According to one embodiment, the server 104 executes a local version of a server module. The local version is a localized server module configured to service a group of designated users or client computers, or a location. Another server 106, also referred to as a central server, is a computing device coupled to the network 108. The server 106 executes the server module and provides centralized access control (AC) management for an entire organization or business. Accordingly, respective local modules in local servers, in coordination with the central server, form a distributed mechanism to provide distributed AC management. Such distributed access control management ensures the dependability, reliability and scalability of centralized AC management undertaken by the central server for an entire enterprise or a business location.
[0039] FIG. 1B shows internal construction blocks of a computing device 118 in which one embodiment of the present invention may be implemented and executed. The computing device 118 may correspond to a client device (e.g., computer 100, computing or storage device 102 in FIG. 1A ) or a server device (e.g., server 104, 106 in FIG. 1A ). As shown in FIG. 1B , the computing device 118 includes a central processing unit (CPU) 122 interfaced to a data bus 120 and a device interface 124. CPU 122 executes instructions to process data and perhaps manage all devices and interfaces coupled to data bus 120 for synchronized operations. The instructions being executed can, for example, pertain to drivers, operating system, utilities or applications. A device interface 124 may be coupled to an external device, such as the computing device 102 of FIG. 1A ; hence, the secured documents therefrom can be received into memory 132 or storage 136 through data bus 120. Also interfaced to data bus 120 is a display interface 126, a network interface 128, a printer interface 130 and a floppy disk drive interface 138. Generally, a client module, a local module or a server module of an executable version of one embodiment of the present invention can be stored to storage 136 through floppy disk drive interface 138, network interface 128, device interface 124 or other interfaces coupled to data bus 120. Execution of such module by CPU 122 can cause the computing device 118 to perform as desired in the present invention. In one embodiment, the device interface 124 provides an interface for communicating with a capturing device 125 (e.g., a fingerprint sensor, a smart card reader or a voice recorder) to facilitate the authentication of a user of the computing device 118.
[0040] Main memory 132, such as random access memory (RAM), is also interfaced to data bus 120 to provide CPU 122 with instructions and access to memory storage 136 for data and other instructions. In particular, when executing stored application program instructions, such as for document securing or document accessing, CPU 122 is caused to manipulate the data to achieve results contemplated by the program instructions. Read-Only Memory (ROM) 134 is provided for storing executable instructions, such as a basic input/output operation system (BIOS) for operation of keyboard 140, display 126 and pointing device 142 that may be present.
[0041] In one embodiment, the computing or storage device 102 is capable of storing secured items (e.g., secured files) in the main memory 132 or the storage 136. The main memory 132 provides non-persistent (i.e., volatile) storage for the secured items and the storage 136 provides persistent (i.e., non-volatile) storage for the secured items. Hence, the computing or storage device 102, or more particularly, the main memory 132 and/or the storage 136, can act as a storage device for the secured items.
[0042] Referring now to FIG. 2A , a block diagram of securing a created document 200 is shown according to one embodiment of the invention. After the document 200 is created with an application or authoring tool and upon an activation of a “Save,” “Save As” or “Close” command or automatic saving invoked by an operating system, the application itself or another application, the created document 200 is caused to undergo a securing process 201. The securing process 201 starts with an encryption process 202, namely, the document 200 that has been created or is being written into a store is encrypted by a cipher with a file key. In other words, the encrypted document could not be opened without the file key (i.e., a cipher key).
[0043] A set of access rules 204 for the document 200 is received and associated with a header 206. In general, the access rules 204 determine or regulate who and/or how the document 200, once secured, can be accessed. In some cases, the access rules 204 also determine or regulate when or where the document 200 can be accessed. Typically, a header is a file structure, small in size and includes, or perhaps links to, security information about a resultant secured document. Depending on an exact implementation, the security information can be entirely included in a header or pointed to by a pointer that is included in the header. According to one embodiment, the access rules 204, as part of the security information, are included in the header 206. According to another embodiment, the access rules 204, as part of the security information, are separately stored from the document 200 but referenced by one or more pointers or links therein. According to still another embodiment, the pointers in the header 206 can point to different versions of security information providing different access control depending on user's access privilege. The security information or the header 206 further includes a file key. Some or all of the header 206 can then be encrypted by a cipher with a user key associated with an authorized user to an encrypted header 210. The encrypted header 210 is attached to the encrypted document 212 to generate a secured document 208.
[0044] It is understood that a cipher may be implemented based on one of many encryption/decryption schemes. Examples of such schemes may include, but not be limited to, Data Encryption Standard algorithm (DES), Blowfish block cipher and Twofish cipher. Therefore, the operations of the present invention are not limited to a choice of those commonly-used encryption/decryption schemes. Any encryption/decryption scheme that is effective and reliable may be used. Hence, the details of encryption/decryption schemes are not further discussed herein so as to avoid obscuring aspects of the present invention.
[0045] To access the secured document 208, one needs to obtain the file key that is used to encrypt the document. To obtain the file key, one needs to be authenticated to get a user or group key and pass an access test in which the access rules in the security information are measured against the user's access privilege.
[0046] It should be noted that the header in a secured document may be configured differently than noted above without departing from the principles of the present invention. For example, a secured document may include a header with a plurality of encrypted headers, each can be accessible only by one designated user or a group users. Alternatively, a header in a secured document may include more than one set of security information or pointers thereto, each set being for one designated user or a group of users while a single file key can be used by all. Some or all of the access rules may be viewed or updated by users who can access the secured document.
[0047] In general, the encryption process and its counter process, decryption, are implemented in a filter or a software module that is activated when a secured document or item is involved. According to one embodiment in an operating system, the software module can be configured to control access to some digital assets (e.g., a port or a device) that may not be encrypted. However, an access to a secured port or device can trigger the software module to operate to control access thereto.
[0048] As will be further described below, to access a secured document, a user needs a user key or keys to decrypt the encrypted security information or at least a portion of the header first. In one embodiment, the key or keys are associated with a user's login to a local server or a central server. Appropriate access privileges associated with the user are validated if the user has been authenticated or previously registered with the server and properly logged in. Depending on the permission or the access privileges, the access rules for the secured document determine whether the contents of the document shall be revealed to the user.
[0049] According to one embodiment, the access rules are present in a markup language, such as HTML, SGML and XML. In a preferred embodiment, the markup language is Extensible Access Control Markup Language (XACML) that is essentially an XML specification for expressing policies for information access. In general, XACML can address fine-grained control of authorized activities, the effect of characteristics of the access requestor, the protocol over which the request is made, authorization based on classes of activities, and content introspection (i.e., authorization based on both the requestor and attribute values within the target where the values of the attributes may not be known to the policy writer). In addition, XACML can suggest a policy authorization model to guide implementers of the authorization mechanism.
[0050] In general, a document is encrypted with a cipher (e.g., a symmetric or asymmetric encryption scheme). Encryption is the transformation of data into a form that is impossible to read without appropriate knowledge (e.g., a key). Its purpose is to ensure privacy by keeping information hidden from anyone to whom it is not intended, even those who have access to other encrypted data. Decryption is the reverse of encryption. Encryption and decryption generally require the use of some secret information, referred to as a key. For some encryption mechanisms, the same key is used for both encryption and decryption; for other mechanisms, the keys used for encryption and decryption are different.
[0051] For the purpose of controlling the access to the document, the key or keys, referred collectively to as a file key, may be the same or different keys for encryption and decryption and are preferably included in the security information contained in or pointed to by the header and, once obtained, can be used to decrypt the encrypted document. To ensure that the key is not to be retrieved or accessible by anyone, the key itself is guarded by the access rules. If a user requesting the document has the proper access privileges that can be granted by the access rules, the key will be retrieved to proceed with the decryption of the encrypted document.
[0052] To ensure that the security information or the header is not readily revealed, at least a portion of the header itself can be encrypted with a cipher. Depending on an exact implementation, the cipher for the header may or may not be identical to the one used for the document. The key (referred to as a user key) to decrypt the encrypted header can, for example, be stored in a local store of a terminal device and activated only when the user associated with it is authenticated. As a result, only an authorized user can access the secured document.
[0053] Optionally, the two portions (i.e., the header (possibly encrypted) and the encrypted document) can be encrypted again and only decrypted by a user key. In another option, the encrypted portions (either one or all) can be error-checked by an error-checking portion, such as using a cyclical redundancy check to ensure that no errors have been incurred to the encrypted portion(s) or the secured document.
[0054] FIG. 2B is a block diagram of a secured item access system 240 according to one embodiment of the invention. The secured item access system 240 operates to process a secured item 242 on behalf of a requestor to either permit or deny access to its contents. The secured item 242 is, for example, a secured file, such as a secured document.
[0055] The secured item 242 includes a header portion 244 and an encrypted data portion 246. The header portion 244 includes at least a pointer 248. When a requestor requests access to the secured item 242, the pointer 248 from the header portion 244 is supplied to a storage device 250. The pointer 248 is used to locate security information 252 stored in the storage device 250. In this embodiment, the security information 252 is not encrypted; however, in another embodiment, the security information 252 could be further secured by encryption. Hence, the pointer 248 is used to retrieve the security information 252 from the storage device 250.
[0056] The header portion 244 also includes at least an encrypted file key 254. The encrypted file key 254 is encrypted in this embodiment to secure the file key. Hence, the encrypted file key 254 is supplied to a first decryption module 256. The first decryption module 256 also receives a user key. In one embodiment, the user key is a private key, and in another embodiment, the user key is a public key. In any case, the first decryption module 256 operates to decrypt the encrypted file key 254 using the user key and thus produces an unencrypted file key 258.
[0057] The security information 252 typically includes at least access rules for access to the encrypted data portion 246 of the secured item 242. The security information 252 is supplied to an access rules analyzer 260. The access rules analyzer 260 also receives user privileges associated with the requestor. The access rules analyzer 260 examines the user privileges and the security information 252, namely, the access rules contained therein, to determine whether the requestor has sufficient privileges to gain access to the encrypted data portion 246 of the secured item 242. The access rules analyzer 260 outputs an access decision to an access controller 262. The access controller 262 receives the access decision and the file key 258. When the access controller 262 determines that the access decision does not permit the requestor to gain access to the encrypted data portion 246 of the secured item 242, then access to the encrypted data portion 246 for the secured item 242 is denied. Alternatively, when the access controller 262 determines that the access decision does permit the requestor to gain access to the encrypted data portion 246 of the secured item 242, then the file key 258 is supplied to a second decryption module 262. In addition, the encrypted data portion 246 of the secured item 242 (i.e., the data of the secured item 242) is supplied to the second decryption module 264. The second decryption module 264 then operates to decrypt the encrypted data portion 246 using the file key 258 to produce an unencrypted data portion 266. The unencrypted data portion 266 is then made available to the requestor, thereby permitting the requestor to gain access to the data associated with the secured item 242.
[0058] According to the invention, the header portion of a secured item is able to be reduced in size due to the use of a pointer. More particularly, the pointer in the header portion points to separately stored security information. Since the size of the pointer is substantially smaller than the size of the security information pointed to, the overall size of the secured item is reduced. In one embodiment, the pointer is structured in a fixed number of bits so that the size of the pointer is constant.
[0059] Additionally, with security information being separately stored, the security information is able to be shared across different documents, thus reducing the storage burdens for storage of secured items. Changes or modifications to security rules or other security information can be more easily made because changes to the secured items themselves are not necessary. That is, changes to security information stored to a storage device are performed without alterations to the corresponding secured items.
[0060] With respect to manageability of secured items, one feature of the invention is that through use of pointers to security information (stored at a storage device separately from the secured files) different secured files are able to share the same stored security information or parts thereof. For example, multiple secured files can utilize identical pointers such that they all share the same security information stored on a local storage device. Consequently, managing the security provided to the secured files is at least in part dependent upon the security information. Hence, by being able to share common security information, not only can the amount of security information storage space being utilized be substantially reduced, but also access to the associated secured files can be managed more efficiently.
[0061] FIG. 2C is a diagram of a representative data structure 280 for a secured file. For example, the secured file can be the secured item 242 illustrated in FIG. 2B . The data structure 280 includes a header (or header portion) 282 and an encrypted data portion 284. The header 282 includes a flag bit 286, at least one pointer 288, and an encrypted file key 290. The flag bit 286 indicates whether or not the data structure pertains to a file that is secured. The at least one pointer 288 points to a remote data structure 292 stored in a storage device. The storage device is typically a local storage device. In other words, the data structure 280 and the remote data structure 292 are typically stored on a common machine (e.g., desktop or portable computer). The data structure 292 stores security information 294. The data structure 292 storing the security information 294 can vary depending upon implementation. However, as shown in FIG. 2C , the data structure 292 for the security information 294 includes a user identifier (ID) 296-1, rules (access rules) 296-2 and other 296-3. The other 296-3 is additional space for other information to be stored within the security information 294. For example, the other information 296-3 may be used to include other information facilitating secure access to the secured file, such as version number or author identifier. The encrypted file key 290 is normally itself decrypted and then used to decrypt the encrypted data portion 214 so as to access the content or data of the secured file.
[0062] FIG. 3 is a flow diagram of secured document access processing 300 according to one embodiment of the invention. The secured document access processing 300 is typically performed by a computer. The computer can be a local computer or a remote computer. Further, the computer can also be considered both a local and a remote computer that operate in a client-server fashion.
[0063] The secured document access processing 300 can be invoked when a requestor selects a document to be accessed. The document is a particular type of file (for example, design.doc). Therefore, more generally, the requestor selects a file in a folder or among other files to be accessed. Once the document has been selected, the secured document access processing 300 is invoked. Initially, the selected document to be accessed is obtained 302. Typically, the selected document will have a header portion and a data portion. Next, a security information pointer is retrieved 304 from the header portion of the selected document. Here, the header portion of the selected document includes at least the security information pointer that points to an address location where the corresponding security information is located. Next, the security information for the selected document is obtained 306 using the security information pointer.
[0064] A decision 308 then determines whether the security information permits the requested access. In this regard, the security information may or may not be encrypted so that it remains secure while stored on the local storage. If the security information is encrypted, the security information would be decrypted (e.g., through use of a user key) to gain access to the security information. The security information contains, among other things, access rules. These access rules are used by the decision 308 in determining whether the requested access is permitted. Namely, the access rules are compared to privileges associated with the requestor for the selected document. When the decision 308 determines that the security information (namely the access rules) does not permit the requested access, then an access denied message is provided 310 to the requestor. On the other hand, when the decision 308 determines that the security information does permit the requested access, then the data portion of the selected document is decrypted 312. Typically, the header portion also includes a file key. The file key is itself normally encrypted and can be decrypted with a user key. The file key can be used to decrypt the encrypted data portion of the selected document. Once the data portion has been decrypted, the data portion is provided 314 to the requestor. Here, the requestor has gained access to the selected document. Following the operation 314, as well as following the operation 310, the secured access document processing 300 is complete and ends.
[0065] The security information is stored to a storage device and located through use of a pointer that is provided with a header portion of a secured file (document). The manner in which the security information is stored within the storage device can vary depending upon implementation. In one embodiment, the pointer directly points to a storage location (i.e., memory location) within the storage device. Stored at the storage location designated by the pointer is the security information. As an example, the security information 294 pointed to by the pointer 288 shown in FIG. 2C can be located in this manner.
[0066] In another embodiment, the security information can be stored in a database-type organization. FIG. 4A illustrates a data organization 400 according to one embodiment of the invention. According to the data organization 400, the association between a secured file 402 and its associated security information as separately stored in a storage device is illustrated. The secured file 402 includes a header portion 404 and a data portion 406. The header portion 404 includes at least a pointer 408 that points to a security information table 410. The security information table 410 can then, in turn, include a pointer to a rules table 412 that can store access rules. In general, the security information table 410 is encrypted by one or more keys in a key table 414. The tables 410, 412 and 414 of the data organization 400 can be provided within a database.
[0067] FIG. 4B illustrates exemplary tables for the security information table 410, the rules table 412, and the key table 414 illustrated in FIG. 4A . The security information table 410 is a main table that is addressed through use of a memory address maintained by an operating system. The pointer 408 points to one of the rows, namely, memory addresses (e.g., operating system addresses), of the security information table 410. The rows of the security information table 410 in turn can point to other tables or include data therein. As shown in FIG. 4B , the columns of the security information table 410 include an operating system address, a policy identifier column and an owning group identifier column. The operating system address column can serve as an index to the security information table 410. The policy identifier column of the security information table 410 includes pointers to particular rows in the rule table 412. The rules within the rules table 412 can be provided within a variety of different formats. The rules table 412 shown in FIG. 4B provides the rules expressed in a markup language format (such as eXtensible Markup Language (XML)). The owning group identifier column of the security information table 410 includes pointers pertaining to group identifiers. These pointers pertaining to the group identifiers point to rows within the key table 414. As shown in FIG. 4B , each row within the key table 414 can store a public key and a private key. In other words, each of the group identifiers is associated with a pair of public and private keys. Depending on implementation and a specific stage of a secured file being accessed, one or both of the public and private keys may be encrypted or readily used to encrypt or decrypt the security information table 410. In any case, only an authenticated user (in a user group identified by one of the group identifiers) can retrieve one of the keys to access the secured file 402.
[0068] FIG. 5 is a block diagram of a file security management system 500 according to one embodiment of the invention. The file security management system 500 includes a security information manager 502 and a database 504. An administrator 506 interacts with the security information manager 502 typically through a graphical user interface (GUI). In this manner, the administrator 506 is able to store, modify or delete information in the database 504. By altering the security information stored in the database 504, the administrator is able to manage the nature of the security provided to associated files or documents. The database 504 includes the security information arranged in a plurality of tables. The tables include a security information table 508, a rules table 510 and a key table 512. For example, using the security information manager 502, the administrator 506 can provide new keys for the key table 512, such as to rotate keys for security reasons. As another example, the administrator 506 might interact with the security information manager to store new access rules (or policies) to the rules table 510. Hence, the separate and distributed storage of the security information and the user of pointers provides an efficient data arrangement that allows security information to be efficiently stored, modified and shared.
[0069] In general, a secured item (e.g., secured file) with its pointer to separately stored security information are stored relative to one another. Hence, moving the location of the secured item requires adjustment to the pointers, particularly when the movement is to another storage device. In other words, although stored in an efficient and manageable format, the secured item and its security information are not readily portable relative to one another as an association to the security information must be maintained. Processing discussed below is able to provide temporary portability for the movement of the secured item.
[0070] FIGS. 6A and 6B are flow diagrams of secured file portability processing 600 according to one embodiment of the invention. The secured file portability processing 600 pertains to processing carried out on a secured file when such file is being moved from its present storage device to a different storage device. Typically, these different storage devices are associated with different computers. The processing shown in FIG. 6A is typically performed by the computer initially storing the secured file, and the processing shown in FIG. 6B is typically performed by a different computer.
[0071] The secured file portability processing 600 begins with a decision 602 that determines whether a request to move a secured file to a different storage device has been received. When the decision 602 determines that such a request has not yet been received, the secured file portability processing 600 awaits such a request. Once the decision 602 determines that a request to move a secured file to a different storage device has been received, the secured file portability processing 600 begins its processing. Initially, a security information pointer is retrieved 604 from a header portion of the secured file. Security information for the secured file is then obtained 606 using the security information pointer. Typically, the security information is not encrypted at this point. Hence, the security information is encrypted. The security information can be encrypted using a key (e.g., public key). Next, the security information pointer in the header is replaced 608 with the encrypted security information.
[0072] After the security information pointer has been replaced with the encrypted security information, the secured file is portable and can thus be moved 610 to the different storage device. Once moved, the secured file can be stored to the different storage device in its portable format or additional processing as provided in FIG. 6B can be performed to store the secured file in a more efficient and manageable format.
[0073] When such additional processing is performed, the encrypted security information is initially retrieved 612 from the header of the secured file. The encrypted security information is then decrypted 613. Once decrypted 613, the security information is stored 614 to the different storage device. The different machine that is performing the processing shown in FIG. 6B has the security information stored therein. Next, a pointer to the stored location of the security information is generated 616. Thereafter, the encrypted security information in the header is replaced 618 with the pointer. At this point, the secured file has been altered such that it includes the pointer and not the encrypted security information. Consequently, the secured file is now more efficiently stored and more manageable. Following the operation 618, the secured file portability processing 600 is complete and ends.
[0074] The invention is preferably implemented by software, but can also be implemented in hardware or a combination of hardware and software. 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 tangible media such as read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape and optical data storage devices. Another example of the computer readable medium is 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.
[0075] 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.
[0076] 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 access rules or criteria are able to be stored separate from the corresponding secured items. Another advantage of the invention is that security information to be used with secured items is able to be readily altered by a security administrator. Still another advantage of the invention is that centralized, dynamic security management is facilitated. Yet another advantage of the invention is that the security approaches of the invention are useful for not only files but also non-file resources, even non-encryptable resources such as pipes/streams, ports and devices.
[0077] 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.
Claims
What is claimed is:
1. A computer readable storage medium having stored thereon computer program code, that if executed by a processor, causes the processor to access a secured item among a plurality of secured items by a method, the method comprising:
obtaining the secured item to be accessed, the secured item having a header portion and a data portion;
retrieving a security information pointer from the header portion of the secured item, wherein each of the plurality of secured items has the same security information pointer as the secured item, such that the plurality of secured items share common security information, wherein the security information includes at least an access rule and user privileges;
obtaining security information for the secured item using the security information pointer; and
permitting access to the secured item to the extent permitted by the security information, wherein the permitting comprises:
retrieving a file key from the header portion;
decrypting the data portion of the secured item using the file key;
retrieving at least one access rule from the security information; and
determining whether a requestor is permitted to access the secured item based on the at least one access rule and characteristics of the requestor.
2. The computer readable storage medium as recited in claim 1, wherein the requestor characteristics include at least a group association for the requestor.
3. The computer readable storage medium as recited in claim 1, wherein the at least one access rule is provided in a markup language format.
4. The computer readable storage medium as recited in claim 1, wherein a requestor desires to access the secured item, and wherein the method further comprises:
decrypting the security information after being obtained and before being used to determine whether access is permitted.
5. The computer readable storage medium as recited in claim 4, wherein the decrypting of the security information uses a key associated with the requestor.
6. The computer readable storage medium as recited in claim 5, wherein the key associated with the requestor is a user key.
7. The computer readable storage medium as recited in claim 1, wherein the security information includes at least access rules, and the header portion includes at least the security information pointer and the file key.
8. The computer readable storage medium as recited in claim 7, wherein when the permitting determines that the requestor is permitted to access the secured item, the permitting further comprises:
retrieving the file key from the header portion; and
decrypting the data portion of the secured item using the file key.
9. The computer readable storage medium as recited in claim 8, wherein the file key is an encrypted file key.
10. The computer readable storage medium as recited in claim 9, wherein a requestor desires to access the secured item, and wherein the decrypting of the encrypted file key is performed using a key associated with the requestor.
11. The computer readable storage medium as recited in claim 1, wherein the secured item is a secured file.
12. The computer readable storage medium as recited in claim 1, wherein the secured item is a secured document.
13. The computer readable storage medium as recited in claim 1, the method further comprising:
changing the security information associated with the security information pointers without having to change each of the plurality of secured items individually.
14. The computer readable storage medium as recited in claim 1, wherein the security information pointers point directly to a storage location of the security information.
15. The computer readable storage medium as recited in claim 1, wherein the security information pointers point to a security information table associated with the security information.
16. The computer readable storage medium as recited in claim 1, wherein the security information pointers point to different versions of the security information providing different levels of access control depending on a user's access privilege.
17. A system for accessing a secured item among a plurality of secured items, the secured item having a header portion and an encrypted data portion, the header portion including a security information pointer and a file key, wherein each of the plurality of secured items has the same security information pointer as the secured item, such that the plurality of secured items share common security information, the system comprising:
a storage device configured to store the security information for the plurality of secured items, wherein the security information includes at least an access rule and user privileges;
a first decryption module configured to:
receive the security information pointer from the header portion of the secured item;
receive the file key from the header portion of the secured item; and
receive at least one access rule from the security information;
an access analyzer operatively connected coupled to the storage device, the access analyzer configured to determine whether the encrypted data portion is permitted to be accessed by a requestor based on the security information, wherein the access analyzer determines whether the encrypted data portion is permitted to be accessed by the requestor based on the at least one access rule and characteristics of the requestor; and
a second decryption module coupled to the access analyzer, the second decryption module configured to decrypt the encrypted data portion using the file key to produce an unencrypted data portion that the requestor is able to access, provided the access analyzer determines that the encrypted data portion is permitted to be accessed by the requestor.
18. The system as recited in claim 17, wherein the requestor has user privileges associated therewith, and wherein the access analyzer determines whether the encrypted data portion is permitted to be accessed by the requestor based on applying the access rule and the user privileges to the requestor and the secured item.
19. The system as recited in claim 17, further comprising:
a security management system configured to change the security information associated with the pointers without having to change each of the plurality of secured items individually.
20. The system as recited in claim 17, wherein the pointers point directly to the storage device.
21. The system as recited in claim 17, wherein the pointers point to a security information table associated with the security information in the storage device.
22. The system as recited in claim 17, wherein the pointers point to different versions of the security information providing different levels of access control depending on a user's access privilege.
23. A method for accessing a secured file stored in a storage device, comprising:
obtaining the secured file to be accessed, the secured file having a header portion and a data portion, wherein the storage device is configured to store security information for a plurality of secured items, wherein the security information includes at least access rules;
retrieving a security information pointer from the header portion of the secured file, wherein the plurality of secured items have the same security information pointer as the secured file, such that the plurality of secured items share the security information;
obtaining, from the storage device, security information for the secured file using the security information pointer; and
permitting access to the secured file to the extent permitted by the security information, wherein the permitting comprises:
retrieving a file key from the header portion;
decrypting the data portion of the secured file using the file key;
retrieving at least one access rule from the security information; and
determining whether a requestor is permitted to access the secured file based on the at least one access rule and requestor characteristics.
24. The method of claim 23, wherein the requester characteristics include at least a group association for the requester.
25. The method of claim 23, wherein the at least one access rule is provided in a markup language format.
26. The method of claim 23, wherein after obtaining security information for the secured file from the storage device, but before the permitting, the method further comprises:
decrypting the security information.
27. The method of claim 26, wherein decrypting the security information is performed using a key associated with the requestor.
28. The method of claim 27, wherein the key associated with the requester is a user key.
29. The method claim 23, wherein the header portion includes at least the security information pointer and the file key.
30. The method of claim 29, wherein when access to the secured file is permitted by the requestor, the permitting further comprises:
retrieving the file key from the header portion; and
decrypting the data portion of the secured file using the file key.
31. The method of claim 30, wherein the file key is an encrypted file key.
32. The method of claim 31, wherein decrypting the data portion of the secured file using the file key is performed using a key associated with a requester requesting access to the secured file.
Patent Citations (476)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4203166(A) | 1980-05-01 | Eshram et al. | Applicant |
| US4734568(A) | 1988-03-01 | Watanabe | Applicant |
| US4757533(A) | 1988-07-01 | Allen et al. | Applicant |
| US4796220(A) | 1989-01-01 | Wolfe | Applicant |
| US4799258(A) | 1989-01-01 | Davies | Applicant |
| US4827508(A) | 1989-05-01 | Shear | Applicant |
| US4888800(A) | 1989-12-01 | Marshall et al. | Applicant |
| US4972472(A) | 1990-11-01 | Brown et al. | Applicant |
| US5032979(A) | 1991-07-01 | Hecht et al. | Applicant |
| US5052040(A) | 1991-09-01 | Preston et al. | Applicant |
| US5058164(A) | 1991-10-01 | Elmer et al. | Applicant |
| US5144660(A) | 1992-09-01 | Rose | Applicant |
| US5204897(A) | 1993-04-01 | Wyman | Applicant |
| US5220657(A) | 1993-06-01 | Bly et al. | Applicant |
| US5235641(A) | 1993-08-01 | Nozawa et al. | Applicant |
| US5247575(A) | 1993-09-01 | Sprague et al. | Applicant |
| US5276735(A) | 1994-01-01 | Boebert et al. | Applicant |
| US5301247(A) | 1994-04-01 | Rasmussen et al. | Applicant |
| US5319705(A) | 1994-06-01 | Halter et al. | Applicant |
| US5369702(A) | 1994-11-01 | Shanton | Applicant |
| US5375169(A) | 1994-12-01 | Seheidt et al. | Applicant |
| US5404404(A) | 1995-04-01 | Novorita | Applicant |
| US5406628(A) | 1995-04-01 | Beller et al. | Applicant |
| US5414852(A) | 1995-05-01 | Kramer et al. | Applicant |
| US5495533(A) | 1996-02-01 | Linehan et al. | Applicant |
| US5499297(A) | 1996-03-01 | Boebert | Applicant |
| US5502766(A) | 1996-03-01 | Boebert et al. | Applicant |
| US5535375(A) | 1996-07-01 | Eshel et al. | Applicant |
| US5557765(A) | 1996-09-01 | Lipner et al. | Applicant |
| US5570108(A) | 1996-10-01 | McLaughlin et al. | Applicant |
| US5584023(A) | 1996-12-01 | Hsu | Applicant |
| US5600722(A) | 1997-02-01 | Yamaguchi et al. | Applicant |
| US5606663(A) | 1997-02-01 | Kadooka | Applicant |
| US5655119(A) | 1997-08-01 | Davy | Applicant |
| US5661806(A) | 1997-08-01 | Nevoux et al. | Applicant |
| US5671412(A) | 1997-09-01 | Christiano | Applicant |
| US5673316(A) | 1997-09-01 | Auerbach et al. | Applicant |
| US5677953(A) | 1997-10-01 | Dolphin | Applicant |
| US5680452(A) | 1997-10-01 | Shanton | Applicant |
| US5684987(A) | 1997-11-01 | Mamiya et al. | Applicant |
| US5689718(A) | 1997-11-01 | Sakurai et al. | Applicant |
| US5699428(A) | 1997-12-01 | McDonnal et al. | Applicant |
| US5708709(A) | 1998-01-01 | Rose | Applicant |
| US5715403(A) | 1998-02-01 | Stefik | Examiner |
| US5717755(A) | 1998-02-01 | Shanton | Applicant |
| US5720033(A) | 1998-02-01 | Deo | Applicant |
| US5729734(A) | 1998-03-01 | Parker et al. | Applicant |
| US5732265(A) | 1998-03-01 | Dewitt et al. | Applicant |
| US5745573(A) | 1998-04-01 | Lipner et al. | Applicant |
| US5748736(A) | 1998-05-01 | Mittra | Applicant |
| US5751287(A) | 1998-05-01 | Hahn et al. | Applicant |
| US5757920(A) | 1998-05-01 | Misra et al. | Applicant |
| US5765152(A) | 1998-06-01 | Ericson | Applicant |
| US5778065(A) | 1998-07-01 | Hauser et al. | Applicant |
| US5787169(A) | 1998-07-01 | Eldridge et al. | Applicant |
| US5787173(A) | 1998-07-01 | Seheidt et al. | Applicant |
| US5787175(A) | 1998-07-01 | Carter | Applicant |
| US5790789(A) | 1998-08-01 | Suarez | Applicant |
| US5790790(A) | 1998-08-01 | Smith et al. | Applicant |
| US5813009(A) | 1998-09-01 | Johnson et al. | Applicant |
| US5821933(A) | 1998-10-01 | Keller et al. | Applicant |
| US5825876(A) | 1998-10-01 | Peterson | Applicant |
| US5835592(A) | 1998-11-01 | Chang et al. | Applicant |
| US5835601(A) | 1998-11-01 | Shimbo et al. | Applicant |
| US5857189(A) | 1999-01-01 | Riddle | Applicant |
| US5862325(A) | 1999-01-01 | Reed et al. | Applicant |
| US5870468(A) | 1999-02-01 | Harrison | Applicant |
| US5870477(A) | 1999-02-01 | Sasaki et al. | Applicant |
| US5881287(A) | 1999-03-01 | Mast | Applicant |
| US5892900(A) | 1999-04-01 | Ginter et al. | Applicant |
| US5893084(A) | 1999-04-01 | Morgan et al. | Applicant |
| US5898781(A) | 1999-04-01 | Shanton | Applicant |
| US5922073(A) | 1999-07-01 | Shimada | Applicant |
| US5923754(A) | 1999-07-01 | Angelo et al. | Applicant |
| US5933498(A) | 1999-08-01 | Schneck et al. | Applicant |
| US5944794(A) | 1999-08-01 | Okamoto et al. | Applicant |
| US5953419(A) | 1999-09-01 | Lohstroh et al. | Applicant |
| US5968177(A) | 1999-10-01 | Batten-Carew et al. | Applicant |
| US5970502(A) | 1999-10-01 | Salkewicz et al. | Applicant |
| US5987440(A) | 1999-11-01 | O'Neil et al. | Applicant |
| US5991879(A) | 1999-11-01 | Still | Applicant |
| US5999907(A) | 1999-12-01 | Donner | Applicant |
| US6014730(A) | 2000-01-01 | Ohtsu | Applicant |
| US6023506(A) | 2000-02-01 | Ote et al. | Applicant |
| US6032216(A) | 2000-02-01 | Schmuck et al. | Examiner |
| US6038322(A) | 2000-03-01 | Harkins | Applicant |
| US6044155(A) | 2000-03-01 | Thomlinson et al. | Applicant |
| US6055314(A) | 2000-04-01 | Spies et al. | Applicant |
| US6058424(A) | 2000-05-01 | Dixon et al. | Applicant |
| US6061790(A) | 2000-05-01 | Bodnar | Applicant |
| US6069957(A) | 2000-05-01 | Richards | Applicant |
| US6085323(A) | 2000-07-01 | Shimizu et al. | Applicant |
| US6088717(A) | 2000-07-01 | Reed et al. | Applicant |
| US6088805(A) | 2000-07-01 | Davis et al. | Applicant |
| US6098056(A) | 2000-08-01 | Rusnak et al. | Applicant |
| US6101507(A) | 2000-08-01 | Cane et al. | Applicant |
| US6105131(A) | 2000-08-01 | Carroll | Applicant |
| US6122630(A) | 2000-09-01 | Strickler et al. | Applicant |
| US6134327(A) | 2000-10-01 | Van Oorschot | Applicant |
| US6134658(A) | 2000-10-01 | Multerer et al. | Applicant |
| US6134660(A) | 2000-10-01 | Boneh et al. | Applicant |
| US6134664(A) | 2000-10-01 | Walker | Applicant |
| US6141754(A) | 2000-10-01 | Choy | Applicant |
| US6145084(A) | 2000-11-01 | Zuili | Applicant |
| US6158010(A) | 2000-12-01 | Moriconi et al. | Applicant |
| US6161139(A) | 2000-12-01 | Win et al. | Applicant |
| US6182142(B1) | 2001-01-01 | Win et al. | Applicant |
| US6185684(B1) | 2001-02-01 | Pravetz et al. | Applicant |
| US6192408(B1) | 2001-02-01 | Vahalia et al. | Applicant |
| US6205549(B1) | 2001-03-01 | Pravetz et al. | Applicant |
| US6212561(B1) | 2001-04-01 | Sitaraman et al. | Applicant |
| US6223285(B1) | 2001-04-01 | Komuro et al. | Applicant |
| US6226618(B1) | 2001-05-01 | Downs et al. | Applicant |
| US6226745(B1) | 2001-05-01 | Wiederhold et al. | Applicant |
| US6240188(B1) | 2001-05-01 | Dondeti et al. | Applicant |
| US6249873(B1) | 2001-06-01 | Richard et al. | Applicant |
| US6253193(B1) | 2001-06-01 | Ginter et al. | Applicant |
| US6260040(B1) | 2001-07-01 | Kauffman et al. | Applicant |
| US6260141(B1) | 2001-07-01 | Park | Applicant |
| US6263348(B1) | 2001-07-01 | Kathrow et al. | Applicant |
| US6272631(B1) | 2001-08-01 | Thomlinson et al. | Applicant |
| US6272632(B1) | 2001-08-01 | Carmen et al. | Applicant |
| US6282649(B1) | 2001-08-01 | Lambert et al. | Applicant |
| US6289450(B1) | 2001-09-01 | Pensak et al. | Applicant |
| US6292895(B1) | 2001-09-01 | Baltzley | Applicant |
| US6292899(B1) | 2001-09-01 | McBride | Applicant |
| US6295361(B1) | 2001-09-01 | Kadansky et al. | Applicant |
| US6301614(B1) | 2001-10-01 | Najork et al. | Applicant |
| US6308256(B1) | 2001-10-01 | Folmsbee | Applicant |
| US6308273(B1) | 2001-10-01 | Goertzel et al. | Applicant |
| US6314409(B2) | 2001-11-01 | Schneck et al. | Applicant |
| US6317777(B1) | 2001-11-01 | Skarbo et al. | Applicant |
| US6332025(B2) | 2001-12-01 | Takahashi et al. | Applicant |
| US6336114(B1) | 2002-01-01 | Garrison | Applicant |
| US6339423(B1) | 2002-01-01 | Sampson et al. | Applicant |
| US6339825(B2) | 2002-01-01 | Pensak et al. | Applicant |
| US6341164(B1) | 2002-01-01 | Dilkie et al. | Applicant |
| US6343316(B1) | 2002-01-01 | Sakata | Applicant |
| US6347374(B1) | 2002-02-01 | Drake et al. | Applicant |
| US6349337(B1) | 2002-02-01 | Parsons et al. | Applicant |
| US6351813(B1) | 2002-02-01 | Mooney et al. | Applicant |
| US6356903(B1) | 2002-03-01 | Baxter et al. | Applicant |
| US6356941(B1) | 2002-03-01 | Cohen | Applicant |
| US6357010(B1) | 2002-03-01 | Viets et al. | Applicant |
| US6363480(B1) | 2002-03-01 | Perlman | Applicant |
| US6370249(B1) | 2002-04-01 | Van Oorschot | Applicant |
| US6381698(B1) | 2002-04-01 | Devanbu et al. | Applicant |
| US6389433(B1) | 2002-05-01 | Bolosky et al. | Applicant |
| US6389538(B1) | 2002-05-01 | Gruse et al. | Applicant |
| US6393420(B1) | 2002-05-01 | Peters | Applicant |
| US6405315(B1) | 2002-06-01 | Burns et al. | Applicant |
| US6421714(B1) | 2002-07-01 | Rai et al. | Applicant |
| US6442688(B1) | 2002-08-01 | Moses et al. | Applicant |
| US6442695(B1) | 2002-08-01 | Dutcher et al. | Applicant |
| US6446090(B1) | 2002-09-01 | Hart | Applicant |
| US6449721(B1) | 2002-09-01 | Pensak et al. | Applicant |
| US6453353(B1) | 2002-09-01 | Win et al. | Applicant |
| US6466932(B1) | 2002-10-01 | Dennis et al. | Applicant |
| US6477544(B1) | 2002-11-01 | Bolosky et al. | Applicant |
| US6490680(B1) | 2002-12-01 | Scheidt et al. | Applicant |
| US6505300(B2) | 2003-01-01 | Chan et al. | Applicant |
| US6510349(B1) | 2003-01-01 | Schneck et al. | Applicant |
| US6519700(B1) | 2003-02-01 | Ram et al. | Applicant |
| US6529956(B1) | 2003-03-01 | Smith et al. | Applicant |
| US6530020(B1) | 2003-03-01 | Aoki | Applicant |
| US6530024(B1) | 2003-03-01 | Proctor | Applicant |
| US6542608(B2) | 2003-04-01 | Scheidt et al. | Applicant |
| US6549623(B1) | 2003-04-01 | Scheidt et al. | Applicant |
| US6550011(B1) | 2003-04-01 | Sims | Applicant |
| US6557039(B1) | 2003-04-01 | Leong et al. | Applicant |
| US6567914(B1) | 2003-05-01 | Just et al. | Applicant |
| US6571291(B1) | 2003-05-01 | Chow | Applicant |
| US6584466(B1) | 2003-06-01 | Serbinis et al. | Applicant |
| US6587946(B1) | 2003-07-01 | Jakobsson | Applicant |
| US6588673(B1) | 2003-07-01 | Chan et al. | Applicant |
| US6594662(B1) | 2003-07-01 | Sieffert et al. | Applicant |
| US6598161(B1) | 2003-07-01 | Kluttz et al. | Applicant |
| US6603857(B1) | 2003-08-01 | Batten-Carew et al. | Applicant |
| US6608636(B1) | 2003-08-01 | Roseman | Applicant |
| US6611599(B2) | 2003-08-01 | Natarajan | Applicant |
| US6611846(B1) | 2003-08-01 | Stoodley | Applicant |
| US6615349(B1) | 2003-09-01 | Hair | Applicant |
| US6615350(B1) | 2003-09-01 | Schell et al. | Applicant |
| US6625650(B2) | 2003-09-01 | Stelliga | Applicant |
| US6629243(B1) | 2003-09-01 | Kleinman et al. | Applicant |
| US6633311(B1) | 2003-10-01 | Douvikas et al. | Applicant |
| US6640307(B2) | 2003-10-01 | Viets et al. | Applicant |
| US6646515(B2) | 2003-11-01 | Jun et al. | Applicant |
| US6647388(B2) | 2003-11-01 | Numao et al. | Applicant |
| US6678835(B1) | 2004-01-01 | Shah et al. | Applicant |
| US6687822(B1) | 2004-02-01 | Jakobsson | Applicant |
| US6711683(B1) | 2004-03-01 | Laczko et al. | Applicant |
| US6718361(B1) | 2004-04-01 | Basani et al. | Applicant |
| US6735701(B1) | 2004-05-01 | Jacobson | Applicant |
| US6738908(B1) | 2004-05-01 | Bonn et al. | Applicant |
| US6775779(B1) | 2004-08-01 | England et al. | Applicant |
| US6782403(B1) | 2004-08-01 | Kino et al. | Applicant |
| US6801999(B1) | 2004-10-01 | Venkatesan et al. | Applicant |
| US6807534(B1) | 2004-10-01 | Erickson | Applicant |
| US6807636(B2) | 2004-10-01 | Hartman et al. | Applicant |
| US6810389(B1) | 2004-10-01 | Meyer | Applicant |
| US6810479(B1) | 2004-10-01 | Barlow et al. | Applicant |
| US6816871(B2) | 2004-11-01 | Lee | Applicant |
| US6826698(B1) | 2004-11-01 | Minkin et al. | Applicant |
| US6834333(B2) | 2004-12-01 | Yoshino et al. | Applicant |
| US6834341(B1) | 2004-12-01 | Bahl et al. | Applicant |
| US6845452(B1) | 2005-01-01 | Roddy et al. | Applicant |
| US6851050(B2) | 2005-02-01 | Singhal et al. | Applicant |
| US6865555(B2) | 2005-03-01 | Novak | Applicant |
| US6874139(B2) | 2005-03-01 | Krueger et al. | Applicant |
| US6877136(B2) | 2005-04-01 | Bess et al. | Applicant |
| US6889210(B1) | 2005-05-01 | Vainstein | Applicant |
| US6891953(B1) | 2005-05-01 | DeMello et al. | Applicant |
| US6892201(B2) | 2005-05-01 | Brown et al. | Applicant |
| US6892306(B1) | 2005-05-01 | En-Seung et al. | Applicant |
| US6907034(B1) | 2005-06-01 | Begis | Applicant |
| US6909708(B1) | 2005-06-01 | Krishnaswamy et al. | Applicant |
| US6915434(B1) | 2005-07-01 | Kuroda et al. | Applicant |
| US6920558(B2) | 2005-07-01 | Sames et al. | Applicant |
| US6931450(B2) | 2005-08-01 | Howard et al. | Applicant |
| US6931530(B2) | 2005-08-01 | Pham et al. | Applicant |
| US6931597(B1) | 2005-08-01 | Prakash | Applicant |
| US6938042(B2) | 2005-08-01 | Aboulhosn et al. | Applicant |
| US6941355(B1) | 2005-09-01 | Donaghey et al. | Applicant |
| US6941456(B2) | 2005-09-01 | Wilson | Applicant |
| US6941472(B2) | 2005-09-01 | Moriconi et al. | Applicant |
| US6944183(B1) | 2005-09-01 | Iyer et al. | Applicant |
| US6947556(B1) | 2005-09-01 | Matyas, Jr. et al. | Applicant |
| US6950818(B2) | 2005-09-01 | Dennis et al. | Applicant |
| US6950936(B2) | 2005-09-01 | Subramaniam et al. | Applicant |
| US6950941(B1) | 2005-09-01 | Lee et al. | Applicant |
| US6950943(B1) | 2005-09-01 | Bacha et al. | Applicant |
| US6952780(B2) | 2005-10-01 | Olsen et al. | Applicant |
| US6957261(B2) | 2005-10-01 | Lortz | Applicant |
| US6959308(B2) | 2005-10-01 | Gramsamer et al. | Applicant |
| US6961849(B1) | 2005-11-01 | Davis et al. | Applicant |
| US6968060(B1) | 2005-11-01 | Pinkas | Applicant |
| US6971018(B1) | 2005-11-01 | Witt et al. | Applicant |
| US6978376(B2) | 2005-12-01 | Giroux et al. | Applicant |
| US6978377(B1) | 2005-12-01 | Asano et al. | Applicant |
| US6988133(B1) | 2006-01-01 | Zavalkovsky et al. | Applicant |
| US6988199(B2) | 2006-01-01 | Toh et al. | Applicant |
| US6993135(B2) | 2006-01-01 | Ishibashi | Applicant |
| US6996718(B1) | 2006-02-01 | Henry et al. | Applicant |
| US7003117(B2) | 2006-02-01 | Kacker et al. | Applicant |
| US7003560(B1) | 2006-02-01 | Mullen et al. | Applicant |
| US7003661(B2) | 2006-02-01 | Beattie et al. | Applicant |
| US7013332(B2) | 2006-03-01 | Friedel et al. | Applicant |
| US7013485(B2) | 2006-03-01 | Brown et al. | Applicant |
| US7020645(B2) | 2006-03-01 | Bisbee et al. | Applicant |
| US7024427(B2) | 2006-04-01 | Bobbitt et al. | Applicant |
| US7035854(B2) | 2006-04-01 | Hsiao et al. | Applicant |
| US7035910(B1) | 2006-04-01 | Dutta et al. | Applicant |
| US7046807(B2) | 2006-05-01 | Hirano et al. | Applicant |
| US7051213(B1) | 2006-05-01 | Kobayashi et al. | Applicant |
| US7058696(B1) | 2006-06-01 | Phillips et al. | Applicant |
| US7058978(B2) | 2006-06-01 | Feuerstein et al. | Applicant |
| US7073063(B2) | 2006-07-01 | Peinado | Applicant |
| US7073073(B1) | 2006-07-01 | Nonaka et al. | Applicant |
| US7076067(B2) | 2006-07-01 | Raike et al. | Applicant |
| US7076312(B2) | 2006-07-01 | Law et al. | Applicant |
| US7076469(B2) | 2006-07-01 | Schreiber et al. | Applicant |
| US7076633(B2) | 2006-07-01 | Tormasov et al. | Applicant |
| US7080077(B2) | 2006-07-01 | Ramamurthy et al. | Applicant |
| US7095853(B2) | 2006-08-01 | Morishita | Applicant |
| US7096266(B2) | 2006-08-01 | Lewin et al. | Applicant |
| US7099926(B1) | 2006-08-01 | Ims et al. | Applicant |
| US7107269(B2) | 2006-09-01 | Arlein et al. | Applicant |
| US7107416(B2) | 2006-09-01 | Stuart et al. | Applicant |
| US7117322(B2) | 2006-10-01 | Hochberg et al. | Applicant |
| US7120635(B2) | 2006-10-01 | Bhide et al. | Applicant |
| US7120757(B2) | 2006-10-01 | Tsuge | Applicant |
| US7124164(B1) | 2006-10-01 | Chemtob | Applicant |
| US7130964(B2) | 2006-10-01 | Ims et al. | Applicant |
| US7131071(B2) | 2006-10-01 | Gune et al. | Applicant |
| US7134041(B2) | 2006-11-01 | Murray et al. | Applicant |
| US7136903(B1) | 2006-11-01 | Phillips et al. | Applicant |
| US7145898(B1) | 2006-12-01 | Elliott | Applicant |
| US7146388(B2) | 2006-12-01 | Stakutis et al. | Applicant |
| US7146498(B1) | 2006-12-01 | Takechi et al. | Applicant |
| US7159036(B2) | 2007-01-01 | Hinchliffe et al. | Applicant |
| US7171557(B2) | 2007-01-01 | Kallahalla et al. | Applicant |
| US7174563(B1) | 2007-02-01 | Brownlie et al. | Applicant |
| US7177427(B1) | 2007-02-01 | Komuro et al. | Applicant |
| US7178033(B1) | 2007-02-01 | Garcia | Applicant |
| US7181017(B1) | 2007-02-01 | Nagel et al. | Applicant |
| US7185364(B2) | 2007-02-01 | Knouse et al. | Applicant |
| US7187033(B2) | 2007-03-01 | Pendharkar | Applicant |
| US7188181(B1) | 2007-03-01 | Squier et al. | Applicant |
| US7194764(B2) | 2007-03-01 | Martherus et al. | Applicant |
| US7200747(B2) | 2007-04-01 | Riedel et al. | Applicant |
| US7203317(B2) | 2007-04-01 | Kallahalla et al. | Applicant |
| US7203968(B2) | 2007-04-01 | Asano et al. | Applicant |
| US7219230(B2) | 2007-05-01 | Riedel et al. | Applicant |
| US7224795(B2) | 2007-05-01 | Takada et al. | Applicant |
| US7225256(B2) | 2007-05-01 | Villavicencio | Applicant |
| US7227953(B2) | 2007-06-01 | Shida | Applicant |
| US7233948(B1) | 2007-06-01 | Shamoon et al. | Applicant |
| US7237002(B1) | 2007-06-01 | Estrada et al. | Applicant |
| US7249044(B2) | 2007-07-01 | Kumar et al. | Applicant |
| US7260555(B2) | 2007-08-01 | Rossmann et al. | Applicant |
| US7265764(B2) | 2007-09-01 | Alben et al. | Applicant |
| US7266684(B2) | 2007-09-01 | Jancula | Applicant |
| US7280658(B2) | 2007-10-01 | Amini et al. | Applicant |
| US7287055(B2) | 2007-10-01 | Smith et al. | Applicant |
| US7290148(B2) | 2007-10-01 | Tozawa et al. | Applicant |
| US7308702(B1) | 2007-12-01 | Thomsen et al. | Applicant |
| US7313824(B1) | 2007-12-01 | Bala et al. | Applicant |
| US7319752(B2) | 2008-01-01 | Asano et al. | Applicant |
| US7340600(B1) | 2008-03-01 | Corella | Applicant |
| US7380120(B1) | 2008-05-01 | Garcia | Applicant |
| US7383586(B2) | 2008-06-01 | Cross et al. | Applicant |
| US7386529(B2) | 2008-06-01 | Kiessig et al. | Applicant |
| US2001/0011254(A1) | 2001-08-01 | Clark | Applicant |
| US2001/0021255(A1) | 2001-09-01 | Ishibashi | Applicant |
| US2001/0021926(A1) | 2001-09-01 | Schneck et al. | Applicant |
| US2001/0023421(A1) | 2001-09-01 | Numao et al. | Applicant |
| US2001/0032181(A1) | 2001-10-01 | Jakstadt et al. | Applicant |
| US2001/0034839(A1) | 2001-10-01 | Karjoth et al. | Applicant |
| US2001/0044903(A1) | 2001-11-01 | Yamamoto et al. | Applicant |
| US2001/0056550(A1) | 2001-12-01 | Lee | Applicant |
| US2002/0010679(A1) | 2002-01-01 | Felsher | Applicant |
| US2002/0013772(A1) | 2002-01-01 | Peinado | Applicant |
| US2002/0016921(A1) | 2002-02-01 | Olsen et al. | Examiner |
| US2002/0016922(A1) | 2002-02-01 | Richards et al. | Examiner |
| US2002/0023208(A1) | 2002-02-01 | Jancula | Applicant |
| US2002/0029340(A1) | 2002-03-01 | Pensak et al. | Applicant |
| US2002/0031230(A1) | 2002-03-01 | Sweet et al. | Applicant |
| US2002/0035624(A1) | 2002-03-01 | Kim | Applicant |
| US2002/0042756(A1) | 2002-04-01 | Kumar et al. | Applicant |
| US2002/0046350(A1) | 2002-04-01 | Lordemann et al. | Applicant |
| US2002/0050098(A1) | 2002-05-01 | Chan | Applicant |
| US2002/0056042(A1) | 2002-05-01 | Van Der Kaay et al. | Applicant |
| US2002/0062240(A1) | 2002-05-01 | Morinville | Applicant |
| US2002/0062245(A1) | 2002-05-01 | Niu et al. | Applicant |
| US2002/0069077(A1) | 2002-06-01 | Brophy et al. | Applicant |
| US2002/0069272(A1) | 2002-06-01 | Kim et al. | Applicant |
| US2002/0069363(A1) | 2002-06-01 | Winburn | Applicant |
| US2002/0073320(A1) | 2002-06-01 | Rinkevich et al. | Applicant |
| US2002/0077986(A1) | 2002-06-01 | Kobata et al. | Applicant |
| US2002/0077988(A1) | 2002-06-01 | Sasaki et al. | Applicant |
| US2002/0078361(A1) | 2002-06-01 | Giroux et al. | Applicant |
| US2002/0087479(A1) | 2002-07-01 | Malcolm | Applicant |
| US2002/0091745(A1) | 2002-07-01 | Ramamurthy et al. | Applicant |
| US2002/0099947(A1) | 2002-07-01 | Evans | Applicant |
| US2002/0124180(A1) | 2002-09-01 | Hagman | Applicant |
| US2002/0129235(A1) | 2002-09-01 | Okamoto et al. | Applicant |
| US2002/0133699(A1) | 2002-09-01 | Pueschel | Applicant |
| US2002/0138762(A1) | 2002-09-01 | Horne | Applicant |
| US2002/0143710(A1) | 2002-10-01 | Liu | Applicant |
| US2002/0143906(A1) | 2002-10-01 | Tormasov et al. | Applicant |
| US2002/0156726(A1) | 2002-10-01 | Kleckner et al. | Applicant |
| US2002/0157016(A1) | 2002-10-01 | Russell et al. | Applicant |
| US2002/0162104(A1) | 2002-10-01 | Raike et al. | Applicant |
| US2002/0169963(A1) | 2002-11-01 | Seder et al. | Applicant |
| US2002/0169965(A1) | 2002-11-01 | Hale et al. | Applicant |
| US2002/0172367(A1) | 2002-11-01 | Mulder et al. | Applicant |
| US2002/0174109(A1) | 2002-11-01 | Chandy et al. | Applicant |
| US2002/0176572(A1) | 2002-11-01 | Ananth | Applicant |
| US2002/0178271(A1) | 2002-11-01 | Graham et al. | Applicant |
| US2002/0194484(A1) | 2002-12-01 | Bolosky et al. | Applicant |
| US2002/0198798(A1) | 2002-12-01 | Ludwig et al. | Applicant |
| US2003/0009685(A1) | 2003-01-01 | Choo et al. | Applicant |
| US2003/0014391(A1) | 2003-01-01 | Evans et al. | Applicant |
| US2003/0023559(A1) | 2003-01-01 | Choi et al. | Applicant |
| US2003/0028610(A1) | 2003-02-01 | Pearson | Applicant |
| US2003/0033528(A1) | 2003-02-01 | Ozog et al. | Applicant |
| US2003/0037133(A1) | 2003-02-01 | Owens | Applicant |
| US2003/0037237(A1) | 2003-02-01 | Abgrall et al. | Applicant |
| US2003/0037253(A1) | 2003-02-01 | Blank et al. | Applicant |
| US2003/0046238(A1) | 2003-03-01 | Nonaka et al. | Applicant |
| US2003/0050919(A1) | 2003-03-01 | Brown et al. | Examiner |
| US2003/0051039(A1) | 2003-03-01 | Brown et al. | Applicant |
| US2003/0056139(A1) | 2003-03-01 | Murray et al. | Applicant |
| US2003/0074580(A1) | 2003-04-01 | Knouse et al. | Applicant |
| US2003/0078959(A1) | 2003-04-01 | Yeung et al. | Applicant |
| US2003/0079175(A1) | 2003-04-01 | Limantsev | Applicant |
| US2003/0081784(A1) | 2003-05-01 | Kallahalla et al. | Applicant |
| US2003/0081787(A1) | 2003-05-01 | Kallahalla et al. | Applicant |
| US2003/0088517(A1) | 2003-05-01 | Medoff | Applicant |
| US2003/0088783(A1) | 2003-05-01 | DiPierro | Applicant |
| US2003/0101072(A1) | 2003-05-01 | Dick et al. | Applicant |
| US2003/0110169(A1) | 2003-06-01 | Zuili | Applicant |
| US2003/0110266(A1) | 2003-06-01 | Rollins et al. | Applicant |
| US2003/0110397(A1) | 2003-06-01 | Supramaniam | Applicant |
| US2003/0115146(A1) | 2003-06-01 | Lee et al. | Applicant |
| US2003/0115218(A1) | 2003-06-01 | Bobbitt et al. | Applicant |
| US2003/0115570(A1) | 2003-06-01 | Bisceglia | Applicant |
| US2003/0120601(A1) | 2003-06-01 | Ouye | Applicant |
| US2003/0120684(A1) | 2003-06-01 | Zuili et al. | Applicant |
| US2003/0126434(A1) | 2003-07-01 | Lim et al. | Applicant |
| US2003/0154381(A1) | 2003-08-01 | Ouye | Applicant |
| US2003/0159066(A1) | 2003-08-01 | Staw et al. | Applicant |
| US2003/0172280(A1) | 2003-09-01 | Scheidt et al. | Applicant |
| US2003/0177070(A1) | 2003-09-01 | Viswanath et al. | Applicant |
| US2003/0177378(A1) | 2003-09-01 | Wittkotter | Applicant |
| US2003/0182579(A1) | 2003-09-01 | Leporini et al. | Applicant |
| US2003/0196096(A1) | 2003-10-01 | Sutton | Applicant |
| US2003/0197729(A1) | 2003-10-01 | Denoue et al. | Applicant |
| US2003/0200202(A1) | 2003-10-01 | Hsiao et al. | Applicant |
| US2003/0217264(A1) | 2003-11-01 | Martin et al. | Applicant |
| US2003/0217333(A1) | 2003-11-01 | Smith et al. | Applicant |
| US2003/0226013(A1) | 2003-12-01 | Dutertre | Applicant |
| US2003/0233650(A1) | 2003-12-01 | Zaner et al. | Applicant |
| US2004/0022390(A1) | 2004-02-01 | McDonald et al. | Applicant |
| US2004/0025037(A1) | 2004-02-01 | Hair | Applicant |
| US2004/0039781(A1) | 2004-02-01 | LaVallee et al. | Applicant |
| US2004/0064710(A1) | 2004-04-01 | Vainstein | Applicant |
| US2004/0068524(A1) | 2004-04-01 | Aboulhosn et al. | Applicant |
| US2004/0068664(A1) | 2004-04-01 | Nachenberg et al. | Applicant |
| US2004/0073660(A1) | 2004-04-01 | Toomey | Applicant |
| US2004/0073718(A1) | 2004-04-01 | Johannessen et al. | Applicant |
| US2004/0088548(A1) | 2004-05-01 | Smetters et al. | Applicant |
| US2004/0098580(A1) | 2004-05-01 | DeTreville | Applicant |
| US2004/0103202(A1) | 2004-05-01 | Hildebrand et al. | Applicant |
| US2004/0103280(A1) | 2004-05-01 | Balfanz et al. | Applicant |
| US2004/0133544(A1) | 2004-07-01 | Kiessig et al. | Applicant |
| US2004/0158586(A1) | 2004-08-01 | Tsai | Applicant |
| US2004/0193602(A1) | 2004-09-01 | Liu et al. | Applicant |
| US2004/0193905(A1) | 2004-09-01 | Lirov et al. | Applicant |
| US2004/0193912(A1) | 2004-09-01 | Li et al. | Applicant |
| US2004/0199514(A1) | 2004-10-01 | Rosenblatt et al. | Applicant |
| US2004/0215956(A1) | 2004-10-01 | Venkatachary et al. | Applicant |
| US2004/0215962(A1) | 2004-10-01 | Douceur et al. | Applicant |
| US2004/0243853(A1) | 2004-12-01 | Swander et al. | Applicant |
| US2005/0021467(A1) | 2005-01-01 | Franzdonk | Applicant |
| US2005/0021629(A1) | 2005-01-01 | Cannata et al. | Applicant |
| US2005/0028006(A1) | 2005-02-01 | Leser et al. | Applicant |
| US2005/0039034(A1) | 2005-02-01 | Doyle et al. | Applicant |
| US2005/0071275(A1) | 2005-03-01 | Vainstein et al. | Applicant |
| US2005/0071657(A1) | 2005-03-01 | Ryan | Applicant |
| US2005/0071658(A1) | 2005-03-01 | Nath et al. | Applicant |
| US2005/0081029(A1) | 2005-04-01 | Thornton et al. | Applicant |
| US2005/0086531(A1) | 2005-04-01 | Kenrich | Applicant |
| US2005/0091484(A1) | 2005-04-01 | Thornton et al. | Applicant |
| US2005/0120199(A1) | 2005-06-01 | Carter | Applicant |
| US2005/0138371(A1) | 2005-06-01 | Supramaniam | Applicant |
| US2005/0138383(A1) | 2005-06-01 | Vainstein | Applicant |
| US2005/0177716(A1) | 2005-08-01 | Ginter et al. | Applicant |
| US2005/0177858(A1) | 2005-08-01 | Ueda | Applicant |
| US2005/0198326(A1) | 2005-09-01 | Schlimmer et al. | Applicant |
| US2005/0223242(A1) | 2005-10-01 | Nath | Applicant |
| US2005/0223414(A1) | 2005-10-01 | Kenrich et al. | Applicant |
| US2005/0235154(A1) | 2005-10-01 | Serret-Avila | Applicant |
| US2005/0256909(A1) | 2005-11-01 | Aboulhosn et al. | Applicant |
| US2005/0273600(A1) | 2005-12-01 | Seeman | Applicant |
| US2005/0283610(A1) | 2005-12-01 | Serret-Avila et al. | Applicant |
| US2005/0288961(A1) | 2005-12-01 | Tabrizi | Applicant |
| US2006/0005021(A1) | 2006-01-01 | Torrubia-Saez | Applicant |
| US2006/0075465(A1) | 2006-04-01 | Ramanathan et al. | Applicant |
| US2006/0093150(A1) | 2006-05-01 | Reddy et al. | Applicant |
| US2006/0168147(A1) | 2006-07-01 | Inoue et al. | Applicant |
| US2006/0230437(A1) | 2006-10-01 | Boyer et al. | Applicant |
| US2007/0006214(A1) | 2007-01-01 | Dubal et al. | Applicant |
| US2007/0067837(A1) | 2007-03-01 | Schuster | Applicant |
| EP672991(A2) | 1995-09-01 | Applicant | |
| EP674253(A1) | 1995-09-01 | Applicant | |
| EP809170(A1) | 1997-11-01 | Applicant | |
| EP913966(A2) | 1999-05-01 | Applicant | |
| EP913967(A2) | 1999-05-01 | Applicant | |
| EP950941(A2) | 1999-10-01 | Applicant | |
| EP950941(A3) | 1999-10-01 | Applicant | |
| EP1107504(B1) | 2001-06-01 | Applicant | |
| EP1107504(A2) | 2001-06-01 | Applicant | |
| EP1130492(A2) | 2001-09-01 | Applicant | |
| EP1154348(A2) | 2001-11-01 | Applicant | |
| EP1324565(A1) | 2003-07-01 | Applicant | |
| GB2328047(A) | 1999-02-01 | Applicant | |
| JP2001-036517 | 2001-02-01 | Applicant | |
| WO96/41288(A1) | 1996-12-01 | Applicant | |
| WO/56028 | 2000-09-01 | Applicant | |
| WO1/61438(A2) | 2001-08-01 | Applicant | |
| WO1/63387(A3) | 2001-08-01 | Applicant | |
| WO1/77783(A2) | 2001-10-01 | Applicant | |
| WO1/78285(A1) | 2001-10-01 | Applicant | |
| WO1/84271(A2) | 2001-11-01 | Applicant |
Non-Patent Literature (64)
- “Inside Encrypting File System,” Part 1, from MSDN Oct. 2001 version, exact publication date is unknown but believed prior to Dec. 12, 2001.Applicant
- “Inside Encrypting File System,” Part 2, from MSDN Oct. 2001 version, exact publication date is unknown but believed prior to Dec. 12, 2001.Applicant
- “Security with Encrypting File System,” from MSDN Oct. 2001 version, exact publication date is unknown but believed prior to Dec. 12, 2001.Applicant
- “How EFS Works,” from MSDN Oct. 2001 version, exact publication date is unknown but believed prior to Dec. 12, 2001.Applicant
- “Encrypting File System,” from MSDN Oct. 2001 version, exact publication date is unknown but believed prior to Dec. 12, 2001.Applicant
- “Features of EFS,” from MSDN Oct. 2001 version, exact publication date is unknown but believed prior to Dec. 12, 2001.Applicant
- “Windows 2000 EFS,” in the April 1999 issue of Windows NT Magazine.Applicant
- “Expiration Mechanism for Chipcards,” IBM Technical Disclosure Bulletin, Oct. 1, 2001, UK.Applicant
- McDaniel et al., “Antigone: A Flexible Framework for Secure Group Communication,” Proceedings of the 8th USENIX Security Symposium, Aug. 23, 1999.Applicant
- Stallings, William, “Cryptography and Network Security: Principles and Practice,” 1999, pp. 333-337, Second Edition, Prentice Hall, Upper Saddle River, New Jersey.Applicant
- Microsoft Windows 2000 Server. Windows 2000 Group Policy White Paper, 2000.Applicant
- Symantec. Norton Antivirus Corporate Edition Implementation Guide, 1999.Applicant
- “Affect,” The American Heritage Dictionary of the English Language, Fourth Edition, Houghton Mifflin Company, 2002. Retrieved May 4, 2006 from http://dictionary.reference.com/search?q=affect.Applicant
- Crocker, Steven Toye, “Multi-level cryptographic transformations for securing digital assets,” U.S. Appl. No. 10/404,566, filed Mar. 31, 2003.Applicant
- Crocker, Steven Toye, “Effectuating access policy changes to designated places for secured files,” U.S. Appl. No. 10/259,075, filed Sep. 27, 2002.Applicant
- Kenrich, Michael Frederick, “Multi-Level File Digest”, U.S. Appl. No. 10/894,493, filed Jul. 19, 2004.Applicant
- Kinghorn, Gary Mark, “Method and system for protecting electronic data in enterprise environment,” U.S. Appl. No. 10/159,220, filed May 31, 2002.Applicant
- Nath, Satyajit, “Method and system for securing digital assets using content type designations,” U.S. Appl. No. 10/405,587, filed Apr. 1, 2003.Applicant
- Prakash, Nalini J., “Method and apparatus for securing/unsecuring files by file crawling,” U.S. Appl. No. 10/325,102, filed Dec. 20, 2002.Applicant
- Rossmann, Alain, “Hybrid systems for securing digital assets,” U.S. Appl. No. 10/325,013, filed Dec. 20, 2002.Applicant
- A Real-Time Push-Pull Communications Model for Distributed Real-Time and Multimedia Systems, Jan. 1999, School of Computer Sciences Carnegie Mellon University, Kanaka Juvva, Raj Rajkumar.Applicant
- U.S. Appl. No. 10/889,685, entitled “Method and Apparatus for Controlling the Speed Ranges of a Machine” inventor Thomas, Jul. 13, 2004, 18 pgs.Applicant
- U.S. Appl. No. 10/028,397, entitled “Method and system for restricting use of a clipboard application,” inventor Zuili, Dec. 21, 2001. 38 pgs.Applicant
- U.S. Appl. No. 10/368,277, entitled “Method and apparatus for uniquely identifying files,” inventor Ouye, Feb. 18, 2003, 25 pgs.Applicant
- U.S. Appl. No. 10/327,320, entitled “Security system with staging capabilities” inventor Vainstein, Dec. 20, 2002, 39 pgs.Applicant
- U.S. Appl. No. 10/286,524, entitled “Security system that uses indirect password-based encryption,” inventor Gutnik, Nov. 1, 2002, 38 pgs.Applicant
- U.S. Appl. No. 10/242,185, entitled “Method and system for protecting encrypted files transmitted over a network” inventor Ryan, Sep. 11, 2002, 33 pgs.Applicant
- U.S. Appl. No. 10/642,041, entitled “Method and system for fault-tolerant transfer of files across a network” inventor Kenrich, Aug. 15, 2003, 32 pgs.Applicant
- U.S. Appl. No. 10/610,832, entitled “Method and system for enabling users of a group shared across multiple file security systems to access secured files” inventor Ryan, Jun. 30, 2003, 33 pgs.Applicant
- U.S. Appl. No. 10/448,806, entitled “Method and System for Using Remote Headers to Secure Electronic Files” inventor Ryan, May 30, 2003, 35 pgs.Applicant
- U.S. Appl. No. 10/074,194, entitled “Methods for idnetifying compounds that inhibit or reduce PTPIB expressions” inventor Rondinone, Feb. 12, 2002, 69 pgs.Applicant
- U.S. Appl. No. 10/074,804, entitled “Secured Data Format for Access Control,” inventor Garcia, Feb. 12, 2002, 108 pgs.Applicant
- U.S. Appl. No. 10/075,194, entitled “System and Method for Providing Multi-location Access Management to Secured Items,” inventor Vainstein et al., Feb. 12, 2002, 110 pgs.Applicant
- U.S. Appl. No. 10/074,996, entitled “Method and Apparatus for Securing Electronic Data,” inventor Lee et al., Feb. 12, 2002, 111 pgs.Applicant
- U.S. Appl. No. 10/074,825, entitled “Method and Apparatus for Accessing Secured Electronic Data Off-line,” inventor Lee et al., Feb. 12, 2002, 108 pgs.Applicant
- U.S. Appl. No. 10/105,532, entitled “System and Method for Providing Different Levels of Key Security for Controlling Access to Secured Items,” inventor Hildebrand et al., Mar. 20, 2002, 86 pgs.Applicant
- U.S. Appl. No. 10/186,203, entitled “Method and System for Implementing Changes to Security Policies in a Distributed Security System,” inventor Huang, Jun. 26, 2002, 65 pgs.Applicant
- U.S. Appl. No. 10/201,756, entitled “Managing Secured Files in Designated Locations,” inventor Alain, Jul. 22, 2002, 121 pgs.Applicant
- U.S. Appl. No. 10/206,737, entitled “Method and System for Updating Keys in a Distributed Security System,” inventor Hildebrand, Jul. 26, 2002, 60 pgs.Applicant
- U.S. Appl. No. 10/246,079, entitled “Security System for Generating Keys from Access rules in a Decentralized Manner and Methods Therefor,” inventor Hildebrand, Sep. 17, 2002, 78 pgs.Applicant
- U.S. Appl. No. 10/259,075, entitled “Effectuating Access Policy Changes to Designated Places for Secured Files,” inventor Crocker, Sep. 27, 2002, 60 pgs.Applicant
- U.S. Appl. No. 10/286,575, entitled “Method and Architecture for Providing Access to Secured Data from Non-Secured Clients,” inventor Vainstein, Nov. 1, 2002, 46 pgs.Applicant
- U.S. Appl. No. 10/295,363, entitled “Security System Using Indirect Key Generation from Access Rules and Methods Therefor,” inventor Vainstein, Nov. 15, 2002, 70 pgs.Applicant
- U.S. Appl. No. 11/889,310, entitled “Method and Systems for Providing Access Control to Electronic Data,” inventor Rossmann, Aug. 10, 2007, 90 pgs.Applicant
- U.S. Appl. No. 11/797,367, entitled “Method and System for Managing Security Tiers,” inventor Vainstein, May 2, 2007, 11 pgs.Applicant
- Adobe Acrobat 5.0 Classroom in a Book, Adobe Press, Jun. 26, 2001, pp. 1-4.Applicant
- Adobe Acrobat Security Settings, Acrobat 7.0, Nov. 15, 2004, pp. 1-4.Applicant
- “Security Options”. Dec. 20, 2001. DC & Co. pp. 1-2.Applicant
- Microsoft Press Computer Dictionary, 1997, Microsoft Press, Third Edition, p. 426.Applicant
- Search Report, completion date May 8, 2003, for European Patent Application No. EP 02 25 8530, 2 pages.Applicant
- Search Report, completion date Oct. 2, 2003, for European Patent Application No. EP 02 25 8531, 2 pages.Applicant
- Search Report, completion date Apr. 14, 2005, for European Patent Application No. EP 02 25 8533, 2 pages.Applicant
- Search Report, completion date Mar. 16, 2005, for European Patent Application No. EP 02 25 8534, 2 pages.Applicant
- Search Report, completion date Mar. 2, 2005, for European Patent Application No. EP 02 25 8535, 2 pages.Applicant
- Search Report, completion date Mar. 3, 2005, for European Patent Application No. EP 02 25 8537, 2 pages.Applicant
- Search Report, completion date May 12, 2005, for European Patent Application No. EP 02 25 8539, 2 pages.Applicant
- Search Report, completion date Jul. 6, 2005, for European Patent Application No. EP 02 25 8529, 4 pages.Applicant
- Search Report, completion date Oct. 8, 2003, for European Patent Application No. EP 02 25 8536, 2 pages.Applicant
- Search Report, completion date May 8, 2003, for European Patent Application No. EP 02 25 8540, 2 pages.Applicant
- Examination Report, completion date Jun. 18, 2008, for European Patent Application No. EP 02 258 532.7-1244, 6 pgs.Applicant
- Office Action, dated May 10, 2005, for European Patent Application No. 02258532.7, 5 pgs.Applicant
- Office Action, dated Dec. 5, 2006, for European Patent Application No. 02258532.7, 5 pgs.Applicant
- Boneh et al., “Hierarchical Identity Based Encryption with Constant Size Ciphertext,” Advances in Cryptology-Eurocrypt 2005, vol. 3493, Jun. 20, 2005, pp. 440-456.Applicant
- Boneh et al., “IBE Secure E-mail,” Stanford University, Apr. 8, 2002, http://crypto.stanford.edu/ibe/.Applicant