|Publication number||USRE41186 E1|
|Application number||US 10/936,829|
|Publication date||30 Mar 2010|
|Filing date||9 Sep 2004|
|Priority date||28 May 1999|
|Also published as||US6289450, US6339825, US6449721, US20010052074, US20020029340, USRE44364, WO2000074299A1|
|Publication number||10936829, 936829, US RE41186 E1, US RE41186E1, US-E1-RE41186, USRE41186 E1, USRE41186E1|
|Inventors||David A. Pensak, John J. Cristy, Steven J. Singles|
|Original Assignee||Emc Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (49), Referenced by (6), Classifications (15), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a division of U.S. patent application Ser. No. 09/906,811, filed Jul. 18, 2001, which is a division of U.S. patent application Ser. No. 09/321,839, filed May 28, 1999, now U.S. Pat. No. 6,289,450.
This application is a reissue of application Ser. No. 09/985,096, filed on Nov. 1, 2001, now U.S. Pat. No. 6,449,721, which application is a division of application Ser. No. 09/906,811, filed on Jul. 18, 2001, now U.S. Pat. No. 6,339,825, which is a division of application Ser. No. 09/321,839, filed on May 28, 1999, now U.S. Pat. No. 6,289,450.
This invention relates to an electronic security system for electronic objects such as documents, video and audio clips and other objects that can be transmitted via a network.
Electronic security systems have been proposed for managing access to electronic information and electronic documents so that only authorized users may open protected information and documents. Several software tools have been developed to work with particular document readers such as Adobe Acrobat Exchange and Adobe Acrobat Reader.
A need still exists for improved systems for providing access to encrypted information by authorized users and which prevent unauthorized users from gaining access to the encrypted information. The present invention allows the authoring user or other controlling party to maintain access control over the electronic information.
The preferred embodiment(s) of the invention are summarized here to highlight and introduce some aspects of the present invention. Simplifications and omissions may be made in this summary. Such simplifications and omissions are not intended to limit the scope of the invention.
The object of the present invention is to provide a system and method for encrypting electronic information so that access to the information can be controlled by the author or other controlling party.
A further object of the present invention is to provide an electronic encryption/decryption system and method in which a central server maintains control over the electronic encryption and decryption keys.
A further object of the present invention is to provide an electronic encryption/decryption system and method in which electronic encryption and decryption keys are not retained by an encrypting or decrypting party.
A further object of the present invention is to provide a system and method for encrypting electronic information so that access to the information can be dynamically changed from a single location without the necessity of collecting or redistributing the encrypted information.
A further object of the present invention is to provide an electronic encryption/decryption system and method in which access to electronic information can be permanently revoked by destroying the association of a decryption key to the electronic information.
These and other objects will become apparent from the figures and written description contained herein.
Preferred embodiment(s) of the invention will be discussed below with reference to attached drawings in which:
Referring now to the Figures wherein like reference numerals indicate like elements, in
The authoring tool 102 allows an authoring user 108 to convert a text document 110 to unreadable form 112 using a strong encryption algorithm and an encryption key, or set of encryption keys, provided by the remote server 106. The authoring tool 102 also registers the electronic document or information with the remote server 106 and associates a set of access policies with the encryption key so that only selected viewing users 116 under selected circumstances may view the document in clear text. The document or information may also be broken down into segments using the authoring tool 102, so that certain segments within a document may have different access policies. For example, a set of users may be allowed to view pages 1-5 of a 10 page document in clear text, while a subset of those users may be allowed to view all 10 pages of the document. The authoring tool 102 also allows the authoring user 108 to block certain functions normally accessible by the viewing user 116. For example, the authoring user 108 may deny a viewing user 116 privileges such as printing and copying of the clear text.
The viewing tool 104 allows a viewing user 116 to decrypt the document 112 an authoring user 108 has encrypted, provided the authoring user 108 has associated an access policy with the decryption key which grants access to the clear text to the viewing user 116. The viewing tool 104 retrieves the decryption key 118 associated with the document segment 112 from the remote server 106, decrypts the document into clear text, renders the document segment, and destroys the decryption key and the clear text version of the document segment. The viewing tool 104 prevents the saving of the decryption key or the clear text version of the document. The viewing tool 104 also blocks the viewing user's machine from performing certain functions, such as printing or copying, as directed by the authoring user 108 during registration of the document 110.
The secure remote server 106 performs several functions. The remote server 106 generates encryption keys 114 for each document segment, maintains decryption keys 118 for registered encrypted documents 112, authenticates requests for viewing a document segment, grants access to registered documents 112 by providing decryption keys 118 and associated access policies to authorized viewing users 116, and maintains an encrypted secure central database which provides association between registered authoring users, registered documents, associated decryption keys, associated policies for each document, options for each user and document, and associated registered viewing users. The remote server 106 does not store or receive the actual document, either encrypted or unencrypted.
The authoring tool 102 and the viewing tool 104 each use essentially the same suite of software tools. As shown in
The secure remote server 206 is a server which is remote from an authoring or viewing user 208, 216. The server 206 maintains a database 236 of encryption keys and associated decryption keys for distribution to registered or authorized users. The remote server 206 also maintains a database which associates registered document segments, which are identified by unique segment IDs, with authoring users, user access profiles, document access policies and options, and associated encryption/decryption keys. The remote server 206 does not actually store registered documents or segments, but instead relates identifying information about a document to the associated information.
The remote server 206 also tracks and maintains records of requests to view documents and to obtain document decryption keys 238. The records may be used to monitor the system for suspicious activity. For example, a single user requesting the decryption key for a document several times during a specific time period might be an indication of suspicious activity. The server can then provide an alert message to a pager, e-mail or fax, thus allowing timely investigation of the activity. The request information may also be used for the purposes of non-repudiation or as a basis for billing in situations where access to the system or access to protected information is being sold.
All communication between the remote server 206 and a user's computer 222, 224 is encrypted using Secure Socket Layer (SSL) protocols. Once an SSL tunnel has been negotiated between a user's machine 222, 224 and the secure server 206, a session key is negotiated. Thus, communications to and from the secure server 206 and a user's computer 222, 224 are doubly encrypted.
Registration with the remote server 206 of a user or automated system wishing to use the system is done separately from any communication for registering a document or viewing a document. A user wishing to register documents for viewing by other users, or viewing registered document registered by other users, must contact the server independently, possibly through a separate human Coordinator 240 or separate network link which can collect payment for the authoring, viewing, and other services, can verify the identity of the user and provide the server with user identification information and user authorization profiles.
The server may be a single server, a set of synchronized servers, or dual servers with a shared database.
The Configuration Utility 226 defines a local user (authoring or viewing) on the user's computer 222, 224. The Configuration Utility 226 establishes the communication parameters for a local user and the remote server 206. For example, the Configuration Utility 226 will query the user to define a local user profile, to include name, password and other identifying information. This local user profile must match the information provided by a user to the Coordinator 240 at the remote server 206.
The Configuration Utility 226 is also responsible for maintaining information regarding the authentication and secure communication method used by the local user, for example, certificate, secret passphrase, smart card, etc. The Configuration Utility 226 maintains information about the local user's secure communication method, for example, the certificate and certification authority for a certificate based secure communication system.
The Administrator Utility 226 is a network client application used by the human Coordinator 240 and other users to control access to documents selected for encryption by defining policies associated with a document. The Administrator Utility 228 is a software program residing on the user's computer 222, 224. The Coordinator 240 or authoring user 208 uses the Administrator Utility 228 to define policies related to a particular user. For example, the Coordinator 240 can use the Administrator Utility 228 to control the functions available to a particular authoring user 208, which might depend on the fees paid by the authoring user 208, or the Coordinator 240 can control the amount of access an authoring user 208 can allow to viewing users 216. Other policies that an individual can define using the Administrator Utility 228 are site policies, group policies, and default policies.
The Administrator Utility 228 allows the Coordinator 240 or authoring or viewing user 208, 216 to determine what documents have been registered by a particular user by accessing the registered user database 236. The Administrator Utility 228 also allows an authoring user to permanently disable the viewing of documents by deleting the associated decryption key from the server. The Administrator Utility 228 also allows an authoring user 208 to initially define the policies related to his documents and to change the policies after the documents have initially been registered.
The Administrator Utility 228 allows a normal authoring user 208 to create, edit, and delete time windows, network specifications and policy templates; view the list of registered documents; and view and edit the policies of documents that are registered. The Administrator Utility 228 allows the Coordinator 240 to create, edit, and delete users and user policies; create, edit, and delete groups of users and group polices; create, edit, and delete document groups and document group policies; define and modify the Site and Default polices; create, edit, and delete document override policies; and view the activity log and set up notification policies
The Application Interface 230 of the preferred embodiment is a standard “Plug-In” to Adobe Acrobat Exchange using SDK and Plug-In Standard Interface. The Plug-In 230 provides a user screen interface to allow the user to access the particular functions associated with registering and viewing documents and communicating with the server. The Plug-In Screen may be integral to the Adobe User Interface Window or may be a separate window. In the preferred embodiment, the Plug-In 230 modifies the Adobe User Interface Window by adding functional “buttons” such as register, create policies, tag, encrypt, view and decrypt.
The Plug-In 230 allows encryption and decryption of PDF files using encryption keys from the remote server 206. The Plug-In 230 connects to the server 206, authenticates the user to the server, registers documents with the server, selects policies at the server as they have been defined -by the authoring user 208 using the Administrator Utility 228.
In addition, the Plug-In 230 blocks certain functions at the viewing user's computer 224 that are otherwise available in Adobe Acrobat Exchange. For example, if the authoring user 208 has limited access to a document so that a viewing user 216 is prohibited from printing a viewed document, the Plug-In 230 temporarily disables the print function of Adobe Acrobat Exchange. Among the functions that the Plug-In 230 can disable are print, copy, cut, paste, save, and other functions. Other functions may be disabled or limited as appropriate for the type of file viewed and the access level. The Application Interface 230 is designed in such a way that it does not disclose either the decryption key or the clear text or unencrypted representation of the protected information content in electronic form.
The Graphical User Interface (“GUI”)supports standard user interface objects such as push buttons, text input fields, lists, menus, and message boxes. The GUI is controlled by the mouse and keypad. The GUI has multiple windows that allow real time setup of server configuration such as who may register a document, who may view a document, when a document may be viewed and on which host the document key and viewing information resides.
A user who wishes to register or to access information must first register and be recognized by the server 206, as represented by reference numeral 1042, 1044 in FIG. 2. The user 208, 216 contacts the server 206 independently, possibly through a separate human Coordinator 240 or separate network link which can collect payment for the authoring, viewing and other services; verify the identity of the user; and provide the server with user identification information and user authorization profiles. Once the user 208, 216 is registered with the server 206, the suite of software tools is provided to the user.
The user must have installed the base software 230, such as Adobe Acrobat Exchange, on his computer. The user then installs the Application Interface 230 provided by the Coordinator 240, as well as the Administrator and Configuration Utilities 228, 226. In one embodiment, upon running the Application Interface 230, the Application Interface 230 will install the Administrator and Configuration Utilities 228, 226 on the user's machine. There is no network activity involved in the installation of the Application Interface 230, Administrator, or Configuration Utilities 228, 226.
Once a user 208, 216 is registered and the Configuration Utility 226 has set up identification and encryption information for the user 208, 216, the user authorized to do so can use the Administrator Utility 228 to create policies associated with a specific document. An authoring user 208 wishing to register a document creates policies to define who, when and how a document may be viewed or otherwise accessed.
The authoring user 208 runs the Administrator Utility 228 which has been installed on his machine 222 and instructs the Administrator Utility 228 to create policies for a document. The Administrator Utility 228 will request the information provided during set up to the Configuration Utility 226 such as username, passphrase, and method of authentication to verify the user's identity. The Administrator Utility 228 will also ask on which server the authoring user 208 wishes to register his document. The Administrator Utility 228 will then establish a connection to the remote server through the Application Interface 230.
The remote server 206 and the authoring or viewing user's computer 222, 224 communicating with the server 206 will negotiate a standard Secure Socket Layet (SSL) encryption tunnel, as represented in
Once the SSL tunnel is established, the user's computer 222, 224 and the server 206 negotiate a secondary session key, as represented in
Once the doubly encrypted communication link is established between the authoring user's computer 222 and the server 206, the authoring user's computer 222 provides login and authentication information to the server 206, 1050. The server 206 authenticates the authoring user's 208 identity and verifies that the authoring user 208 has authority to use the system by checking a database of registered users 236 maintained on the server. The information provided by the authoring user 208 to the Configuration Utility 226 is compared to the information provided by the user to the Coordinator 240 during the independent user registration process 1042, 1044. The database 234 contains all of the access controls related to a particular user, so that if a user is only authorized to view documents, he will not be allowed to use the system to register or encrypt documents.
After the server 206 authenticates the authoring user 208 and verifies that the authoring user 208 is authorized to register documents, the Administrator Utility 228 allows the authoring use 208 to create policies applicable to a particular viewing user 216, a group of viewing users, or a default policy for all other users. The policies are then communicated to the server 206, 1051. Policies define who may view a document, when, and under what conditions. Policies are created by combining a set of constraints including allowable or denied users and groups, time ranges, and Internet Protocol (IP) addresses. Access to a document by a viewing user 216 is determined by combining the user policy, document policy, as well as possibly the group policy and document group policy. If the Coordinator 240 has created a document override policy for a document, then the override takes precedence over the regular document policy defined by the authoring user. Policies include limiting who may view a document or portion of a document and the time frame during which a user may view the document.
The Administrator Utility 228 also allows the authoring user 208 to create options. Options specify what functions of the base software 232 are temporarily disabled so that the viewing user 216 is prohibited from accessing them while viewing the document. An option can also enforce a watermark on printing. For example, the authoring user 208 can prohibit a particular viewing user 216 from printing, saving, or copying a particular document or portion of a document. These Options are defined by the authoring user 208 using the Administrator Utility 228, but the options are enforced by the Application Interface 230.
An authoring user 208 wishing to encrypt a document will open the document on his computer 222. The Application Interface 230 must also be loaded before the document or information can be encrypted. In the preferred embodiment, the Plug-In 230 adds menu items to the menu bar in Adobe Acrobat Exchange such as “tag” and “encrypt” “Tag” allows the authoring user 208 to select segments of the document to be encrypted. The authoring user 208 can assign different policies to different tagged segments of a single document, i.e., policies are associated with segments. A segment may consist of any subset of the entire document or the entire document. Once the document has been segmented or “tagged,” the authoring user selects “encrypt” from the menu bar. If the authoring user 208 has not already logged into the remote server 206, the Plug-In 230 will force a log in to the remote server 206 through the Administrator Utility 228. A log-in screen is provided and the authoring user 208 must log-in to the server 206. The server 206 authenticates the authoring user 208 and verifies that the authoring user 208 is authorized to register documents.
Once the authoring user has been authenticated, the authoring user is asked to associate the overall document with a policy, and this information is communicated to the remote server 1052. This policy becomes the default policy for any portions of the document which are not tagged and associated with a specific policy. The Plug-In 230 assigns a unique segment ID for each tagged segment after the authoring user has tagged all segments and has instructed the Plug-In 230 to go ahead with the encryption. The PlugIn 230 transmits the segment IDs to the server 206. The server 206 generates a random encryption key for each segment ID and communicates the encryption key to the authoring user's computer 222, 1054. The server 206 stores the segment ID, the key associated with the particular segment ID, and the policy associated with a particular segment ID in the central database 234, and then transmits the key to the Plug-In 230 at the authoring user's computer 222. The Plug-In 230 at the authoring user's computer 222 encrypts the segment, immediately destroys or removes the key from the authoring user's machine 222, and then deletes the clear text for the segment from the Plug-In 230. Thus, key lifetime is very short on the authoring user's machine. The encryption key is never stored on the authoring user's machine where it is accessible, such as the hard disk. The key can even be obfuscated while in the memory of the authoring user's machine. The duration of the key's existence depends on the speed of the computer which actually performs the encryption, since the key is destroyed immediately after the encryption. In the preferred embodiment, 128-bit RC4 is used for document and segment encryption.
Once all segments have been encrypted, the Plug-In 230 produces a hash of the entire document and sends the hash to the server as document identification, 1055. The server 206 stores the hash with the keys associated with the document. Thus, the document is never transmitted to the server 206, only the segment IDs and hash.
A pop-up window asks the authoring user 208 where he wishes to store the encrypted document. By default, the encrypted document overwrites the clear text document on the authoring user's machine 222.
A user wishing to view a document must have installed the Configuration Utility 226, Administrator Utility 228, and the Application Interface 230 on his computer 224. The viewing user 216 must be independently registered with the Coordinator 240 as a user. The viewing user 216 must also have installed the base software application 232 for viewing the document, such as Adobe Acrobat Exchange. The viewing user 216 must enter the Configuration Utility 226 and provide user set up information.
If the viewing user 216 has not opened the Configuration Utility 226, the Administrator Utility 228 and the Application Interface 230, these programs will automatically be opened once the information to be accessed has been selected, and the system has recognized that the information is encrypted.
Once the Configuration Utility 226 has opened, it will request the user to provide information defining both the viewing user 216 and the viewing user's computer 224. If the viewing user 216 is a new user, the viewing user 216 will select a button on the Configuration Utility's interface window indicating that a new user profile needs to be provided. The Configuration Utility 226 will provide a query screen to the user and the user will input identification information, such as a user name. The identification information will be checked against the information provided to the server 206 or Coordinator 240 during the independent user registration process.
The Application Interface 230 will check to see if the user is logged onto the remote server 206. If the viewing user 216 has not logged onto the remote server, the Application Interface 230 provides a pop-up window so that the user can log in to the server. An SSL tunnel and session key are negotiated, 1056, 1058. The viewing user's computer 224 provides login and authentication information to the server 206, 1060. Once logged into the server 206, the Application Interface 230 requests access to the document or information 1062 by asking the server 206 for the decryption key for the first segment of the document or information to be accessed. The server 206 uses the segment ID to check the database to find the policies associated with the segment and thus to determine whether the viewing user 216 is authorized to access this segment or the document as a whole.
If the viewing user 216 is not authorized to access the segment, the viewing user 216 is so informed. If the user 216 is authorized to access the segment, the server 206 sends the decryption key and options for that segment to the Application Interface 230 at the viewing user's computer 224 and the Application Interface 230 decrypts the segment using the decryption key. After decrypting the segment, the Application Interface 230 immediately discards/destroys the key, renders the decrypted segment to the screen, and then destroys the decrypted version of the segment. When the viewing user moves to a different segment, the process is repeated.
The Application Interface 230 enforces the options which were assigned by the authoring user 230 to the segment viewed by the viewing user 216. For example, if the authoring user 208 assigned that the viewing user 216 cannot print the clear text document or segment, then the Plug-In 230 disables the print function of Adobe Acrobat Exchange while the clear text document or segment is available to the viewing user 216. Other functions which can be controlled or disabled by the Plug-In 230 are save, copy, paste, and print with watermark. For other base software packages such as audio 230, the functions controlled by the Application Interface 230 could be play, copy, and save unencrypted. Thus, using the options, the viewing user 216 has no ability to permanently acquire the clear text document or data.
The secure central database 234 resides on the remote server 206. It may be a distributed or shared database residing on multiple remote servers 206. In the preferred embodiment the database 234 is maintained in Berkley DB software. All records maintained in the central database 234 are encrypted and the database is password protected. The Coordinator 240 controls the database 234 and has access to the database 234 using the password.
All keys for encryption and decryption are maintained in the database 234. The database 234 provides a structure for associating segment IDs with an associated decryption key, policies for accessing that segment, and options for accessing that segment. The authoring user 208 may change a policy associated with a segment ID through the Administrator Utility 228 on his computer. The change in policy is communicated to the remote server 206 and the database 234 is updated accordingly. The update policy function allows an authoring user 208 to revoke access to a segment or document by a user or group of users.
The authoring user 208 can destroy the decryption key or the association of a decryption key to a segment or document on the database 234 using the Administrator Utility 228. By destroying the decryption key or the association of the decryption key with a Segment or Document, the authoring user 208 destroys the ability to decrypt the information, effectively shredding all copies of the information.
Regular backups of the database 234 are made without shutting down the whole database 234.
One or more preferred embodiments have been described to illustrate the invention(s). Additions, modifications, and/or omissions may be made to the preferred embodiment(s) without departing from the scope or spirit of the invention(s). It is the intent that the following claims encompass all such additions, modifications, and/or variations to the fullest extent permitted by law.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4605820 *||10 Nov 1983||12 Aug 1986||Visa U.S.A. Inc.||Key management system for on-line communication|
|US4803108||1 May 1987||7 Feb 1989||Essex Specialty Products, Inc.||Honeycomb reinforcing sheet for the reinforcement of panels and method of reinforcing panels|
|US4937863 *||7 Mar 1988||26 Jun 1990||Digital Equipment Corporation||Software licensing management system|
|US5058164 *||3 May 1990||15 Oct 1991||National Semiconductor Corp.||Encryption of streams of addressed information to be used for program code protection|
|US5098124||6 Sep 1990||24 Mar 1992||Automotive Technologies International Inc.||Padding to reduce injuries in automobile accidents|
|US5263157 *||15 Feb 1990||16 Nov 1993||International Business Machines Corporation||Method and system for providing user access control within a distributed data processing system by the exchange of access control profiles|
|US5349893||20 Feb 1992||27 Sep 1994||Dunn Eric S||Impact absorbing armor|
|US5356177||25 Jun 1993||18 Oct 1994||Davidson Textron Inc.||Side impact protection apparatus|
|US5410598 *||27 Sep 1994||25 Apr 1995||Electronic Publishing Resources, Inc.||Database usage metering and protection system and method|
|US5410602 *||27 Sep 1993||25 Apr 1995||Motorola, Inc.||Method for key management of point-to-point communications|
|US5432849 *||10 Aug 1993||11 Jul 1995||International Business Machines Corporation||Secure cryptographic operations using control vectors generated inside a cryptographic facility|
|US5438508 *||12 Sep 1994||1 Aug 1995||Digital Equipment Corporation||License document interchange format for license management system|
|US5440631 *||26 Apr 1993||8 Aug 1995||Fijitsu Limited||Information distribution system wherein storage medium storing ciphered information is distributed|
|US5509070 *||15 Dec 1992||16 Apr 1996||Softlock Services Inc.||Method for encouraging purchase of executable and non-executable software|
|US5586186 *||15 Jul 1994||17 Dec 1996||Microsoft Corporation||Method and system for controlling unauthorized access to information distributed to users|
|US5604801 *||3 Feb 1995||18 Feb 1997||International Business Machines Corporation||Public key data communications system under control of a portable security device|
|US5629980 *||23 Nov 1994||13 May 1997||Xerox Corporation||System for controlling the distribution and use of digital works|
|US5673316 *||29 Mar 1996||30 Sep 1997||International Business Machines Corporation||Creation and distribution of cryptographic envelope|
|US5689560 *||25 Apr 1994||18 Nov 1997||International Business Machines Corporation||Method and apparatus for enabling trial period use of software products: method and apparatus for allowing a try-and-buy user interaction|
|US5708709 *||8 Dec 1995||13 Jan 1998||Sun Microsystems, Inc.||System and method for managing try-and-buy usage of application programs|
|US5727065 *||2 Jun 1997||10 Mar 1998||Hughes Electronics||Deferred billing, broadcast, electronic document distribution system and method|
|US5754646 *||19 Jul 1995||19 May 1998||Cable Television Laboratories, Inc.||Method for protecting publicly distributed software|
|US5765152 *||13 Oct 1995||9 Jun 1998||Trustees Of Dartmouth College||System and method for managing copyrighted electronic media|
|US5796825 *||6 Oct 1997||18 Aug 1998||Symantec Corporation||System for automatic decryption of file data on a per-use basis and automatic re-encryption within context of multi-threaded operating system under which applications run in real-time|
|US5809145 *||28 Jun 1996||15 Sep 1998||Paradata Systems Inc.||System for distributing digital information|
|US5818936 *||15 Mar 1996||6 Oct 1998||Novell, Inc.||System and method for automically authenticating a user in a distributed network system|
|US5822524||21 Jul 1995||13 Oct 1998||Infovalue Computing, Inc.||System for just-in-time retrieval of multimedia files over computer networks by transmitting data packets at transmission rate determined by frame size|
|US5883955 *||7 Jun 1995||16 Mar 1999||Digital River, Inc.||On-line try before you buy software distribution system|
|US5892900 *||30 Aug 1996||6 Apr 1999||Intertrust Technologies Corp.||Systems and methods for secure transaction management and electronic rights protection|
|US5933498 *||5 Nov 1997||3 Aug 1999||Mrj, Inc.||System for controlling access and distribution of digital property|
|US5956034 *||13 Aug 1996||21 Sep 1999||Softbook Press, Inc.||Method and apparatus for viewing electronic reading materials|
|US5978475 *||18 Jul 1997||2 Nov 1999||Counterpane Internet Security, Inc.||Event auditing system|
|US5997077||18 Aug 1998||7 Dec 1999||Volkswagen Ag||Deformable structure for protection of vehicle occupants|
|US6002772 *||2 Apr 1997||14 Dec 1999||Mitsubishi Corporation||Data management system|
|US6064736||15 Sep 1997||16 May 2000||International Business Machines Corporation||Systems, methods and computer program products that use an encrypted session for additional password verification|
|US6182220||30 Mar 1998||30 Jan 2001||International Business Machines Corporation||System and method for building and exchanging encrypted passwords between a client and server|
|US6245408||19 May 1999||12 Jun 2001||Hexcel Corporation||Honeycomb core with controlled crush properties|
|US6289450 *||28 May 1999||11 Sep 2001||Authentica, Inc.||Information security architecture for encrypting documents for remote access while maintaining access control|
|US6308256||18 Aug 1999||23 Oct 2001||Sun Microsystems, Inc.||Secure execution of program instructions provided by network interactions with processor|
|US6339825 *||18 Jul 2001||15 Jan 2002||Authentica, Inc.||Method of encrypting information for remote access while maintaining access control|
|US6401204 *||16 May 1997||4 Jun 2002||Siemens Aktiengesellschaft||Process for cryptographic code management between a first computer unit and a second computer unit|
|US6449721 *||1 Nov 2001||10 Sep 2002||Authentica Security Technologies, Inc.||Method of encrypting information for remote access while maintaining access control|
|US6499106||15 Jan 1999||24 Dec 2002||Sony Corporation||Method and apparatus for secure distribution of information recorded of fixed media|
|US6547280||11 Nov 1999||15 Apr 2003||Cellbond Limited||Energy-absorbing structures|
|US6658566 *||12 Mar 1998||2 Dec 2003||Bull Cp8||Process for storage and use of sensitive information in a security module and the associated security module|
|US6682128||19 Jun 2001||27 Jan 2004||Oakwood Energy Management, Inc.||Composite energy absorber|
|US6711553||6 Jun 2000||23 Mar 2004||Kent Ridge Digital Labs||Method and apparatus for digital content copy protection|
|US6732106||8 Dec 2000||4 May 2004||Matsushita Electric Industrial Co., Ltd.||Digital data distribution system|
|US20010055396||26 Feb 2001||27 Dec 2001||David Jevans||Mechanism for efficient private bulk messaging|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7916870 *||3 Nov 2006||29 Mar 2011||Verizon Patent And Licensing Inc.||Systems and methods for document control using public key encryption|
|US8170213 *||27 Dec 2007||1 May 2012||Emc Corporation||Methodology for coordinating centralized key management and encryption keys cached through proxied elements|
|US8555342||23 Dec 2009||8 Oct 2013||Emc Corporation||Providing secure access to a set of credentials within a data security mechanism of a data storage system|
|US8681994 *||15 Mar 2011||25 Mar 2014||Verizon Patent And Licensing Inc.||Systems and methods for document control using public key encryption|
|US20080107271 *||3 Nov 2006||8 May 2008||Verizon Services Organization Inc.||Systems and Methods for Document Control Using Public Key Encryption|
|US20110167266 *||15 Mar 2011||7 Jul 2011||Verizon Patent And Licensing, Inc.||Systems and methods for document control using public key encryption|
|U.S. Classification||713/171, 713/172|
|International Classification||H04L29/06, H04L9/32|
|Cooperative Classification||H04L63/10, H04L63/062, H04L2463/101, H04L63/166, H04L63/0428, H04L63/0442|
|European Classification||H04L63/04B, H04L63/04B2, H04L63/06B, H04L63/16D, H04L63/10|
|25 Apr 2006||AS||Assignment|
Owner name: EMC CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AUTHENTICA, INC.;REEL/FRAME:017821/0737
Effective date: 20060227
Owner name: EMC CORPORATION,CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AUTHENTICA, INC.;REEL/FRAME:017821/0737
Effective date: 20060227
|21 Sep 2016||AS||Assignment|
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT
Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001
Effective date: 20160907
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A
Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001
Effective date: 20160907
|27 Sep 2016||AS||Assignment|
Owner name: AUTHENTICA SECURITY TECHNOLOGIES, INC., MASSACHUSE
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PENSAK, DAVID A;CRISTY, JOHN J;SINGLES, STEVEN J;REEL/FRAME:039863/0152
Effective date: 19990712
Owner name: AUTHENTICA, INC., MASSACHUSETTS
Free format text: CHANGE OF NAME;ASSIGNOR:AUTHENTICA SECURITY TECHNOLOGIES, INC.;REEL/FRAME:040164/0911
Effective date: 19990721
|13 Oct 2016||AS||Assignment|
Owner name: AUTHENTICA, INC., MASSACHUSETTS
Free format text: CHANGE OF NAME;ASSIGNOR:AUTHENTICA SECURITY TECHNOLOGIES, INC.;REEL/FRAME:040337/0393
Effective date: 19990729