# Patent

## Title
System and method for customer authentication of an item

## Abstract

A system, apparatus and method is provided for authentication of an item or a label by storing unique random serial numbers or codes in a remote secure storage that can be used to authenticate the item or the label, generating a pointer to each stored unique random serial number/code and storing the generated pointer(s) in a client data storage. During or prior to a production run of the item(s) or label(s): the generated point(s) are sent from the client data storage to one or more media devices, the generated pointer(s) are obtained from the media device using a post-content manager, the unique random serial number(s)/code(s) are obtained from the server via the post-content manager using the generated pointer(s), the obtained unique random serial number(s)/code(s) are sent to the media device, and the received unique random serial number(s)/code(s) are imprinted on the item(s) or the label(s) using the media device.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS
This patent application is: (a) a non-provisional patent application of U.S. patent application 61/102,814 filed on Oct. 3, 2008 and entitled “System and Method for Customer Authentication of an Item”; (b) a continuation-in-part patent application of U.S. patent application Ser. No. 12/495,789 filed on Jun. 30, 2009 and entitled “System, Method and Apparatus for Electronically Protecting Data and Digital Content”, which is: (i) a non-provisional patent application of “U.S. provisional patent application 61/077,156 filed on Jun. 30, 2008 and entitled “System, Method and Apparatus for Electronically Protecting Data and Digital Content”; and (ii) a continuation-in-part patent application of U.S. patent application Ser. No. 11/378,549 filed on Mar. 16, 2006 and entitled “System, Method and Apparatus for Electronically Protecting Data and Digital Content”, which is a non-provisional patent application of U.S. provisional patent application 60/662,562 filed on Mar. 16, 2005 and entitled “Managing Personally Identifiable Information” and U.S. provisional patent application 60/773,518 filed on Feb. 15, 2006 and entitled “Managing Personally Identifiable Information”. All of the foregoing patent applications are hereby incorporated by reference in their entirety.


FIELD OF THE INVENTION
The present invention relates generally to the field of computerized certification and, more particularly, to a system and method for customer authentication of an item.
BACKGROUND OF THE INVENTION
The counterfeit and diversion of products and services is a global problem. One of the leading types of counterfeit products is pharmaceutical drugs that are falsely-labeled, have expired, have active ingredients that are diluted, adulterated, substituted, completely misrepresented, or is sold under a false brand name. A person who uses a counterfeit drug may experience a number of dangerous consequences, including death.
Many counterfeit drugs came from countries that make legal drugs. In one country, for example, it is illegal to sell counterfeit drugs for domestic use, but not illegal to manufacture and export them. As a result, it is estimated that 75% of counterfeit drugs come from this country. At the same time, this country also is a leading supplier of high quality drugs sold by legitimate drug manufacturers, including most leading brand name drugs sold in the US and Europe.
The full extent of the problem is unknown. It is estimated that as much as 10% of drugs sold worldwide are counterfeit, and in some countries, this number may exceed 50%. In 2003, the World Health Organization estimated that the annual cost of counterfeit drugs exceeded US$32 billion.
There are several technologies that attempt to combat these problems. One is based on RFID tags and requires special equipment. Another is called ePedigree and is being promoted by the U.S. Food and Drug Administration. ePedigree tracks drugs from manufacturers to pharmacies and is designed to prevent the counterfeiting or diversion of drugs by allowing wholesalers and pharmacists to determine the identity and dosage of individual products. The 2006 Compliance Policy Guide for the Prescription Drug Marketing Act stated that “a drug pedigree is a statement of origin that identifies each prior sale, purchase, or trade of a drug, including the date of those transactions and the names and addresses of all parties to them.”
As of 2008, most U.S. states had some sort of ePedigree requirement. However, these are little more than requiring pharmaceutical supply chain companies to provide audit reports. ePedigree laws continue to change rapidly and some states are pushing out deadlines by many years.
While ePedigree looks promising, it has many serious flaws as illustrated by its implementation by a major U.S. software provider:

    
    
        ePedigree systems require an industrial-strength supply chain infrastructure. Deployment requires things like SAP-based ERP systems requiring millions of dollars and years of deployment. ePedigree is an expensive sledge hammer to crack millions of little peanuts.
        ePedigree focuses on pallets and packages and not on bottles or even individual pills in bottles.
        ePedigree does not police bad actors in the entire supply chain. For example, any retailer can still substitute counterfeit products if it makes economic sense.
        ePedigree requires special equipment like barcode and RFID readers to read serial numbers.
        Software providers are waiting to deploy RFID technology because the costs for secure tags remain too high for wide adoption.
        Another ePedigree flaw may be the numbering scheme—in spite of the huge infrastructure costs, France is already running out of serial numbers.
        ePedigree does nothing to protect the information systems that protect the products and services. This invites bad actors to circumvent ePedigree by breaking into tracking systems in order to manipulate the information related to manufacturers, distributers, retailers, doctors, and patients.
        ePedigree does not have baked-in controls and incentives. For example, it does not permit a consumer to rate the integrity a retailer, which would put huge pressure on the retailer to sell legitimate products. There is also no tie-in with law-enforcement when things go obviously wrong.
        Finally, ePedigree is only tuned for pharmaceutical drug products.
    
    


As a result, many firms are opposed to ePedigree. One called deployment costs “overwhelming” and has put the entire project on hold. In fact, the deadline to meet California's requirements may be delayed back to 2015 due to pressure from the pharmaceutical industry. ePedigree is an expensive, complex extension to current supply-chain systems for large corporations. It offers virtually nothing for counterfeit or diversion problems outside North America, nor the problems facing the vast majority of businesses in the global marketplace.
As a result, there is a need for a simpler, less expensive way to combat counterfeit and diversion problems for all products and services.
SUMMARY OF THE INVENTION
The present invention provides a system and method permitting anyone with Web, instant messaging, or phone access to immediately certify that a product or service is authentic. This can be done by any consumer before any purchase is made. Certification can fail for any number of reasons, including the item's serial number being unknown, an identical item has been previously sold, an item's expiration date has expired, an item is being sold at the wrong location, or an item's batch has been rejected. As a result, the present invention provides a simpler, less expensive way to combat counterfeit and diversion problems for all products and services. The present invention may provide one or more of the following benefits:

    
    
        Where deployment is measured in months rather than years, and does not require government standards or support.
        That can economically track bottles or individual pills in bottles.
        That polices bad actors in the supply chain so that no one retailer or rogue employee can substitute counterfeit products when it makes economic sense.
        That does not require special equipment like barcode and RFID readers and can be used anywhere by anyone at any time.
        That is economical with current RFID technologies rather than having to wait for new RFID technologies and manufacturing volumes to lower costs.
        That does not run out of numbers.
        That protects the information systems that support and manage ePedigree.
        That has baked-in controls and incentives, such as the ability for consumer to rate the integrity of retailer to only sell legitimate products, and real-time tie-ins with law-enforcement when things go wrong.
        That is economic for any product or service, not just pharmaceuticals
    
    


The present invention provides a system and method for electronically storing globally unique serial numbers in a way that protects individual products and services so that they can be protected, monitored, controlled, paid for, or even destroyed, as determined by the primary manufacturer or owner. It does not require, but may be further enhanced by existing technologies, including access control systems, encryption, SSL, and VPNs. The present invention is based on the separation of duties and seamless integration at a later time with the proper authentication. The present invention is unique because it puts the quality of all products and services in a supply chain directly into the hands of any individual, particularly consumers. While certain components of the present invention, such as its use of serial numbers, appear to be obvious and common, these components are used in a new and unique way to solve global problems that currently remain unsolved by far more complex inventions.
The present invention provides a system for authentication of an item or a label that includes one or more clients and a server communicably coupled to the one or more clients. Each client has a data storage, a post-content manager and one or more media devices communicably coupled to the data storage and the post-content manager. The server stores one or more unique random serial numbers or codes in a secure storage that can be used to authenticate the item or the label, generates a pointer to each stored unique random serial number or code stored in the secure storage, and sends at least one of the generated pointer(s) to at least one of the clients. During or prior to a production run of the item(s) or label(s): (a) the post-content manager obtains the generated pointer(s) from the media device, obtains the unique random serial number(s) or code(s) from the server using the generated pointer(s), and transmits the obtained unique random serial number(s) or code(s) to the one or more media devices, and (b) the media device imprint the received unique random serial number(s) or code(s) on the item(s) or the label(s).
In addition, the present invention provides an apparatus for authentication of an item or a label that includes a communications interface to a remote server having a secure storage, a client data storage, one or more media devices communicably coupled to the data storage, and a post-content manager communicably coupled with the server via the communications interface and the media device. The remote server stores one or more unique random serial numbers or codes in the secure storage that can be used to authenticate the item or the label and generates a pointer to each stored unique random serial number or code. The generated pointer(s) are stored on the client data storage. During or prior to a production run of the item(s) or label(s): (a) the post-content manager obtains the generated pointer(s) from the media device, obtains the unique random serial number(s) or code(s) from the server using the generated pointer(s), and transmits the obtained unique random serial number(s) or code(s) to the one or more media devices, and (b) the media device imprint the received unique random serial number(s) or code(s) on the item(s) or the label(s).
Moreover, the present invention provides a method for authentication of an item or a label by storing one or more unique random serial numbers or codes in a remote secure storage that can be used to authenticate the item or the label, generating a pointer to each stored unique random serial number or code and storing the generated pointer(s) in a data storage of a client. During or prior to a production run of the item(s) or label(s): (a) the generated point(s) are sent from the data storage of the client to one or more media devices, (b) the generated pointer(s) are obtained from the media device using a post-content manager, (c) the unique random serial number(s) or code(s) are obtained from the server via the post-content manager using the generated pointer(s), (d) the obtained unique random serial number(s) or code(s) are sent to the media device, and (e) the received unique random serial number(s) or code(s) are imprinted on the item(s) or the label(s) using the media device. The method can be implemented by a computer program embodied on a computer readable medium wherein the method steps are executed by one or code segments.
The present invention is described in detail below with reference to the accompanying drawings.



BRIEF DESCRIPTION OF THE DRAWINGS
The above and further advantages of the invention may be better understood by referring to the following description in conjunction with the accompanying drawings, in which:
FIGS. 1A and 1B are block diagrams of a method for protecting sensitive data in accordance with one embodiment of the present invention;
FIG. 2 is a block diagram of a server-client system in accordance with one embodiment of the present invention;
FIG. 3 is an example of sensitive fields in client storage in accordance with one embodiment of the present invention;
FIG. 4 illustrates a screen that accepts the definitions of the system, table, and fields in client storage that contain sensitive data in accordance with one embodiment of the present invention;
FIG. 5 illustrates an example of FIG. 3 in client storage after conversion in accordance with one embodiment of the present invention;
FIG. 6 illustrates the conversion process in accordance with one embodiment of the present invention;
FIG. 7 illustrates the authentication process in accordance with one embodiment of the present invention;
FIG. 8 illustrates how stolen data or a stolen device does not contain any sensitive data in accordance with one embodiment of the present invention;
FIG. 9 illustrates a Password Manager application in accordance with one embodiment of the present invention;
FIG. 10 illustrates how plug-ins are used to examine and control content manager requests in accordance with one embodiment of the invention;
FIG. 11 illustrates how the content manager processes a request to get a record from client storage in accordance with one embodiment of the invention;
FIG. 12 illustrates how each content manager request to get sensitive data is processed on the secure server in accordance with one embodiment of the invention;
FIG. 13 illustrates how content manager processes a request to put a record in client storage in accordance with one embodiment of the invention;
FIG. 14 illustrates how each content manager request to put sensitive data is processed on secure server in accordance with one embodiment of the invention;
FIG. 15 illustrates how the storage manager uses random pointer and index to locate the sensitive data in secure storage in accordance with one embodiment of the invention;
FIG. 16 illustrates how the index takes a random pointer from storage manager and uses it to locate an address in index in accordance with one embodiment of the invention;
FIG. 17 illustrates two event types received or detected by the events manager in accordance with one embodiment of the invention;
FIG. 18 illustrates how the present invention can be used by a manufacturing client to remove critical components of, say, a DVD so that the DVD may be previewed but not played in full;
FIG. 19 illustrates tracking data to enable a unique type of forensic analysis in accordance with the present invention;
FIG. 20 illustrates how the compliance problems with governmental regulations and how outsourcing problems are solved in accordance with the present invention;
FIG. 21 illustrates a typical screen that accesses data in accordance with the present invention;
FIG. 22 illustrate how the present invention protects sensitive data in a way that is transparent and seamless to the enterprise database applications;
FIGS. 23, 24A and 24B illustrate protecting sensitive data in Microsoft® Excel® files in accordance with the present invention;
FIGS. 25A, 25B and 25C illustrate looking for one or more links in a digital content file being protected in accordance with the present invention;
FIGS. 26-32 illustrate protecting sensitive data in a data broker or firm client environment in accordance with one embodiment of the present invention;
FIG. 33 is a block diagram of a server-client system in accordance with one embodiment of the present invention;
FIG. 34 is a flowchart illustrating the decision process of the device processing sensitive information in one embodiment of the present invention;
FIG. 35 is a block diagram of a server-client system in accordance with another embodiment of the present invention;
FIG. 36 is a screen layout of a program used to control the present invention;
FIG. 37 is a report layout produced by the present invention;
FIG. 38 is a block diagram that illustrates how multiple client applications may access the same information in secure storage;
FIG. 39 illustrates how a single root document in secure storage may be used by multiple client applications;
FIG. 40 is a schematic diagram of one embodiment of the present invention;
FIG. 41 is a screen and printout of a message in accordance with one embodiment of the present invention;
FIG. 42 is a screen layout used to control one embodiment of the present invention;
FIG. 43 is a block diagram of the protection coverage in accordance with one embodiment of the present invention; and
FIG. 44 is one embodiment of a GIF image file that is loaded when an Excel® file is loaded without the plug-in.
FIG. 45 is a block diagram of a server-client system for authenticating an item or label in accordance with one embodiment of the present invention;
FIG. 46 is a block diagram of a server-client system for authenticating an item or label in accordance with another embodiment of the present invention;
FIGS. 47A-C illustrate three labels that may be attached to a product or service in accordance with one embodiment of the present invention;
FIG. 48A illustrates how counterfeit or diverted products are identified in accordance with one embodiment of the present invention;
FIG. 48B illustrates how counterfeit or diverted services are identified in accordance with one embodiment of the present invention;
FIG. 49 is a flowchart that illustrates the sequence of questions and actions taken during a phone call from a person trying to certify the validity of a product or service in accordance with one embodiment of the invention; and
FIG. 50 illustrates the database tables managing one embodiment of the present invention.



DETAILED DESCRIPTION OF THE INVENTION
While the making and using of various embodiments of the present invention are discussed in detail below, it should be appreciated that the present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed herein are merely illustrative of specific ways to make and use the invention and do not delimit the scope of the invention. The discussion herein relates primarily to the protection of products and services, but it will be understood that the concepts of the present invention are applicable to any system where products or services are at risk.
The present invention provides a system and method for electronically storing globally unique serial numbers in a way that protects individual products and services so that they can be protected, monitored, controlled, paid for, or even destroyed, as determined by the primary manufacturer or owner. It does not require, but may be further enhanced by existing technologies, including access control systems, encryption, SSL, and VPNs. The present invention is based on the separation of duties and seamless integration at a later time with the proper authentication. The present invention is unique because it puts the quality of all products and services in a supply chain directly into the hands of any individual, particularly consumers. While certain components of the present invention, such as its use of serial numbers, appear to be obvious and common, these components are used in a new and unique way to solve global problems that currently remain unsolved by far more complex inventions.
Now referring to FIG. 1A, a block diagram of a method 100a for protecting sensitive data in accordance with one embodiment of the present invention is shown. The sensitive data is extracted from a data storage on a client 102 in block 106 and the extracted data is sent to a server 104 for storage in block 108. The sensitive data may include personal data, financial data, corporate data, legal data, government data, police data, immigration data, military data, intelligence data, security data, surveillance data, technical data, copyrighted content or a combination thereof. The server 104 receives the extracted data from the client 102 in block 110 and stores the extracted data to a secure storage on the server 104 in block 112. One or more pointers to the extracted data are generated in block 114 and the one or more pointers are sent to the client 102 in block 116. The pointer(s) may include random data that is of a same data type as the sensitive data. Furthermore and as shown in FIG. 1B, the pointer(s) is subsequently used to access the sensitive data after proper authentication. The client 102 receives the pointer(s) indicating where the extracted data has been stored in block 118 and then replaces the sensitive data on the data storage on the client 102 with the pointer(s) in block 120. Note that all the methods and processes described herein can be implemented using a computer program embodied on a computer readable medium wherein the steps are executed by one or more code segments. In addition, the communications between the server 104 and the client 102 can be encrypted using well known techniques.
Referring now to FIG. 1B, a block diagram of a method 100b for protecting sensitive data in accordance with one embodiment of the present invention is shown. The client 102 receives a request (first) for data stored on the data storage of the client 102 in block 150 and determines whether the requested data includes the sensitive data in decision block 152. If the requested data does not include the sensitive data, as determined in decision block 152, the requested data is provided in block 154. If, however, the requested data includes the sensitive data, as determined in decision block 152, a request (second) containing the pointer(s) to the sensitive data is sent to the server 104 in block 156 and the request (second) containing the pointer(s) to the sensitive data is received from the client 102 in block 158. If the request and pointer(s) are authentic, as determined in decision block 160, the sensitive data is retrieved using the pointer(s) in block 162 and the retrieved sensitive data is sent to the client 102 in block 164. The client 102 receives the sensitive data from the server 104 in block 168 and provides the requested data in block 154. If, however, the request or the pointer(s) are not authentic, as determined in decision block 160, a response denying the request (second) is sent to the client 102 in block 170. The client 102 receives the response denying the request (second) in block 172 and denies access to the requested data in block 174. An unauthorized attempt to access or use the sensitive data may result in various events being triggered, such as alarms or automatic notifications. Moreover, all these transactions can be logged to create an audit trail. Furthermore, the received sensitive information still may be restricted in that it may only be viewed or used in an authorized application. In other words, the received sensitive information cannot be further transferred or stored. Access to and storage of the sensitive data can be governed by one or more rules.
Now referring to FIG. 2, a block diagram of a server-client system 200 in accordance with one embodiment of the present invention is shown. The system 200 includes one or more clients 202 and a server 204 communicably coupled to the one or more clients 202. The client 202 is any device or system that stores sensitive data and then accesses it (e.g., a computer, a laptop computer, a handheld computer, a desktop computer, a workstation, a data terminal, a phone, a mobile phone, a personal data assistant, a media player, a gaming console, a security device, a surveillance device or a combination thereof). This could be anything from a small client like a cell phone right up to a large enterprise system. Each client 202 has client storage 206 and a content manager 208 that extracts the sensitive data from the data storage 206, sends the extracted data to the server 204 for storage, receives a pointer indicating where the extracted data has been stored and replaces the sensitive data on the data storage 206 with the pointer. The server 204 receives the extracted data from the client 202, stores the extracted data to a secure storage 210, generates the pointer and sends the pointer to the client 202. The server 204 can be communicably coupled to the one or more clients 202 via a computer network, a telecommunications network, a wireless communications link, a physical connection, a landline, a satellite communications link, an optical communications link, a cellular network or a combination thereof. Note that communications between the server 204 and the client 202 can be encrypted using well known techniques.
The server 204 includes an application program interface (API) layer 212, an authentication layer 214 coupled to the application program layer 212, a plug-in layer 216 coupled to the authentication layer 214, a data layer 218 coupled to the plug-in layer 216 and an events layer 220 coupled to the data layer 218, the plug-in layer 216 and the authentication layer 214.
The client 202 includes a data storage or client storage 206, one or more applications 222, a communications interface (caching) 224 to a remote server 204 having a secure storage 210, and a content manager 208 communicably coupled to the data storage 206, the one or more applications 222 and the communications interface (caching) 224. The content manager 208 controls access to the data storage 206, extracts the sensitive data from the data storage 206, sends the extracted data to the remote server 204 for storage via the communications interface (caching) 224, receives a pointer(s) indicating where the extracted data has been stored and replaces the sensitive data on the data storage 206 with the pointer(s). The content manager 208 also receives a first request from the one or more applications 222 for data stored on the data storage 206, and determines whether the requested data includes the sensitive data and provides the requested data to the one or more applications 222 whenever the requested data does not include the sensitive data. The content manager 208 performs the following steps whenever the requested data includes the sensitive data: sends a second request containing the pointer(s) to the server 204 that authenticates the second request, denies the first request whenever the authentication fails, and receives and provides the sensitive data to the one or more applications 222 whenever the authentication succeeds.
As a result, the present invention removes sensitive data from client storage 206 and transfers it to secure server 204. The content manager 208 is placed between the application 222 and client storage 206 so that the sensitive data can be merged back in a manner that is seamless and transparent to the application 222. The content manager 208 is a new type of client middleware that protects personal, sensitive, and/or copyright content from being used in an unauthorized manner.
The content manager 208 and API layer 212 of the secure server 204 communicate via XML, EDI, or any other communication protocol 226. The API layer 212 also includes an API table 236. Caching 224 may be used to speed up communication, or temporarily store sensitive data when the client 202 is not connected to the secure server 204.
A one-time process extracts the sensitive data in client storage 206 and sends it to secure storage 210 in the secure server 204. In return, the secure server 204 generates one or more pointers that indicate where in secure storage 210 the sensitive data has been stored. This pointer is returned to the content manager 208 and replaces the original sensitive data in client storage 206. One preferred embodiment for this pointer is random data, generated by a plug-in, with the same type as the sensitive data that it is replacing. This pointer is later used by the content manager 208 to get sensitive data from or put sensitive data back into the secure server 204.
After this one-time process, each time the application 222 accesses client storage, the content manager 208 checks to see if the request is for sensitive data. If it is not, then the request is processed in the regular manner. If the access involves sensitive data, then the content manager 208 passes the pointer in client storage 206 to the secure server 204. The sensitive data is got from or put in secure storage according to the rules 228 in the authentication layer 214 and/or plug-ins 230 in the plug-ins layer 216.
The secure server 204 authenticates all client requests in the authentication layer 214, which includes an authentication table 238. Authentication is based on rules 228 that are stored in the secure server 204. For example, a rule could require a specific hardware device be used during business hours with biometric access. Provision is made to integrate the present invention with other access control systems. If authentication fails, then the request is processed by the events manager 232. The events manager 232 provides additional processing capabilities for taking specific protection actions, sending an alarm 240 to notify people, updating audit trails 242, and other event requirements.
An authenticated request is passed to the plug-ins layer 216, which includes plug-in table 244, for processing. Plug-ins 230 provide additional processing capabilities for specific regulations, industries, devices, applications, and other processing needs. The majority of plug-in requests are passed to the data layer 218. Some plug-ins 230 provide additional support for the secure server 204, such as generating random index values for client storage 206, or processing special requests that the owner of the client 202 wants to outsource to a trusted firm, such as storing critical encryption keys in a safe, protected manner. The data layer 218 is controlled by the storage manager 234 where pointers are used to get sensitive data from or put sensitive data in secure storage 210. The data layer 218 also includes an index 246.
Securing Data and Digital Content
Once a table in client storage 206 has been identified as needing the present invention, certain steps are taken to protect it. In the preferred embodiment, the sensitive data in client storage 206 is transferred to secure storage 210 with the following steps:

    
    
        Referring to FIG. 3, an example of sensitive fields 300 in client storage 206 are shown. In this example, SSN 302, DOB 304, Name 306, and Address 308 need protection; whereas Employee Number 310, City 312, State 314 and Zip Code 316 do not need protection.
        Referring to FIG. 4, a screen 400 accepts the definitions of the system 402, table 404, and fields 406 in client storage 206 that contain sensitive data. These definitions are stored in client storage 206 and/or plug-in table 244.
        The sensitive data in the defined fields (402, 404 and 406) are removed from table in client storage 206, the fields in client storage 206 are replaced with random pointers, and the sensitive data is transferred to the secure storage 210.
    
    


These same definitions are later used by content manager 208, authentication 214, plug-ins 216, and storage manager 234 to access sensitive data in the index 246 and secure server 204, as well as move it to and from the application 222.
One embodiment of these field definitions can be seen in FIG. 4. The definitions for each sensitive data field include:

    
    
        The system name 402, such as Human Resources.
        The table name 404 in the system, such as HR101.
        The field name 406 in the table, such as SSN (Social Security Number).
        The pointer type 408, such as random data 410 generated by a plug-in 230, an encrypted value 412, or a combination 414.
        If the pointer is to be unique 416 in the current system 418 or for all systems 420 in the secure server 204.
        If auto version control 422 is required to make unique copies of the sensitive data in the secure server 204.
        If caching 424 on the client 202 is to be used for this field. Answering Yes increases accessibility but may reduce security because client storage 206 and sensitive data from secure storage 210 are on the same device.
        If sensitive data fields are to be split 426, and what process to use. For example, the first 4 bits of each byte may be stored in one physical location of secure storage 210 and the other 4 bits of each byte stored on another physical location of secure storage 210. This and other methods obfuscate sensitive data to reduce the chance of a single trusted person having access to all sensitive data.
        The process or processes to use if the sensitive data is to be mirrored 428 on more than one physical copy of secure storage 210.
        The process or processes to use if additional forensics data 430 is to be stored about this field in secure storage 210. This can be later used to determine the who, what, when, where, and why sensitive data was given.
        The process or processes to use if authentication fails 432. Examples include returning a blank value, a dummy value, or taking specific action.
        What plug-in(s) 434 to perform before the content manager's 208 request is processed by storage manager 234.
        What plug-in(s) 436 to perform after the content manager's 208 request is processed by storage manager 234.
    
    


After conversion is complete, the table 320 in client storage 206 is shown in FIG. 5, and the steps 600 taken are shown in FIG. 6. Each record has been examined and the sensitive fields have been moved from client storage 206 to secure storage 218. A plug-in 230 has generated a unique random pointer and passed it back to the content manager 208 where it replaced the original sensitive field. The random pointer was then stored in index in a way that permitted rapid access to the sensitive field. Note that each random pointer in the table used same field type as the sensitive data that it replaced. This made the present invention transparent and seamless to the client application 222.
Client Storage and Communications Security
The table in client storage 206 no longer contains sensitive data and the field values do not use encryption that can be analyzed in any way. The original sensitive data can only be obtained by having content manager 208 pass the random pointer to the secure server 204.
In the preferred embodiment, communication between the client 202 and secure server 204 is an SSL/TLS encryption tunnel.
All data stored in client memory (echo, page files, unallocated space) is single or double encrypted. One preferred embodiment encrypts all data before it is transmitted to the secure server 204. This data is also encrypted on the secure server 204. The use of stream cyphers for encryption allows the encrypted keys to be updated out of order, so that the data is never in the clear on the secure server 204.
Note that more complex security methods can be added to client storage 206, content manager 208, client memory, communications with secure server 204, and/or secure storage 210.
Content Manager
Content manager 208 seamlessly monitors requests from the application 222 to client storage 206. If the request is for sensitive data, the content manager 208 seamlessly gets sensitive data from or puts sensitive data in secure storage 210.
Content manager 208 also manages all communication with plug-ins 230. This could be to receive new random pointes, update new software and/or instructions, or any other process.
Client Caching
Caching 224 may be used by client 202 to speed access between the content manager 208 and secure server 204. It can also be used to temporarily store sensitive data from secure storage 210 when the client 202 is not connected to the secure server 204. This enables the application 222 to operate when the user is not connected to the secure server 204, such as on a plane.
Note that encrypted in-memory caching using a tool such as OpenSSL can also be used. One preferred embodiment keeps all cached data in memory in a way that its contents are not permanently stored on the client 202 and are automatically erased when the client device is turned off.
API Layer—How Clients Access the Secure Server
The secure server's 204 API layer 212 communicates with client devices via XML, EDI, or any other communication protocol 226 as defined by API table 236. This enables the present invention to protect sensitive data on any connected device, platform, or application. For example, a human resources system might run on an Oracle platform while a payroll system might run on a Sybase platform.
Note that the present invention can be used to store common sensitive data on the secure server 204 so that it is centrally located and easily accessed by all applications as regulations and business practices change. The present invention adds cross-platform interoperability and flexibility to existing legacy and enterprise systems for the data that is currently at most risk to process change.
Note that the present invention can also be used to centralize sensitive, critical, or complex data that is likely to be affected by new regulations. For example, a Federal Trade Commission's Data Disposal Rule permits individuals to contact companies that have collected their credit data. Individuals may request that these companies permanently dispose of this data, which could be stored in multiple servers running multiple applications. The present invention gives companies new tools to centrally store and manage this type of data so that it can be, in this example, easily located and disposed of.
Authentication Layer—Who has Access
The authentication layer 214 validates all access to plug-ins 230 and secure storage 210, including all requests from content manager 208. One preferred embodiment is storing the authentication rules in authentication table 238 that include:

    
    
        Who has access, including authorized user names, types of authentication permitted, authentication values such as passwords and biometric data.
        What applications and systems each user may access.
        When each user may access, including hours of the day and days of the week, as well as how often each user must re-authenticate.
        Where each user must access from, such as VPN addresses or specific device identifiers.
        Why each user has access so that suspicious behavior can be examined.
        What action must be taken when authentication fails. This can be as simple as logging the request and suggesting the user enter a new password to notifying a supervisor and downloading code so the client's content manager 208 can destroy the client storage 206 and client hardware.
    
    


In the preferred embodiment, the authentication rules 228 are dependant on the user, how much protection is required by the application 222, and the type of sensitive data that is in secure storage 210. Weak authentication could be a simple password entered on a laptop client running the application 222. Strong authentication could be a biometric fingerprint device on a specific laptop that can only be used at certain times of the day, and only while the user's finger remains on the biometric device. Referring to FIG. 7, authentication is dependant on rules defined in the authentication table 238.
Note that the present invention can also be used authenticate with other methods. Authentication could be, for example, by system, table, and/or field name. For example, a global rule for all Social Security Number fields can be set, irrespective of who is accessing the secure server 204.
Referring to FIG. 8, stolen data or a stolen device does not contain any sensitive data when the present invention is used because the sensitive data has been moved to the secure server 204 in a way that is transparent to the application 222. The only way to retrieve the sensitive data is to run the application 222 and content manager 208. As a result, parts of the device are now “transparently dumb” and can be used by the application 222 in a seamless manner 800. If the device has been reported as stolen 802, or if authentication fails 804, then appropriate action is taken by events manager 232, which could include warning alarms, denial of the request, and/or downloading code to the client content manager 208 that monitors behavior and/or destroys data and/or the client hardware.
Another embodiment of the present invention extends current Web authentication systems. Referring to FIG. 9, a Password Manager application 900 collects and stores sensitive data (User ID 902, Password 904) in secure storage 210. Using strong authentication, such as with a biometric device, the Password Manager application 900 enables single-click sign-on to any Website. This is done by:

    
    
        The user authenticating with Password Manager 900.
        The Password Manager application 900 getting the User ID 902 and Password 904 from secure storage 210.
        The Password Manager application 900 passing this to a browser application.
        The browser application using this to sign-on to the desired Website.

Note that this Password Manager application 900 is an example of when archiving is not required on the secure server 204 because when a password changes the previous value is not required, so the new value may override the previous one.

Plug-Ins Layer

    
    


Plug-ins 230 process authenticated requests from content manager 208. Referring to FIG. 10, plug-ins 230 are used to examine and control content manager 208 requests before and after storage manager 234 gets sensitive data from or puts sensitive data in secure storage 210.
Plug-ins 230 work with their own API's that permit any process or program to extend the capabilities of the present invention. For example, Sarbanes-Oxley compliance is so expensive that it can be measured as a percent of total revenue. Some of these costs involve auditing who has access to what sensitive data. In spite of these auditing controls, there is no audit or firewall that will prevent a trusted employee from copying sensitive data to, say, a flash drive for illegal purposes. The present invention ensures that the data copied from client storage 206 contains no sensitive data. Plug-ins 230 ensure that all access to the sensitive data in secure server 204 can be examined, denied, enhanced, and/or logged in an audit trail as needed.
Plug-ins 230 work in different ways. Pre processing plus-ins examine requests before sensitive data is got from or put in secure storage 210. Control may or may not then be passed to the data layer. Post processing plug-ins examine the results after data has been got from or put in secure storage 210. Plug-ins 230 may store temporary or permanent instructions or values in plug-in table 244 or external tables as needed. Plug-ins 230 may deny, enhance, or act on any request.
Plug-ins 230 embodiments may be used to:

    
    
        Look for suspicious behavior.
        Count how sensitive data is accessed for billing purposes.
        Ensure that outsourced sensitive data is properly used.
        Guard against triangulation or inference attacks.
        Integrate with other third party access control systems to enhance the authentication process in the present invention.
        Log all access to specific sensitive data, such as a trade secret or a SSN.
        Assure compliance with regulations, such as SOX, HIPAA, GLB, the EU Data Directive, Homeland Security, SB-1386, or any new regulation.
        Monitor access to dummy data intentionally stored where it can be stolen. This enables a new type of “honey pot” that could yield valuable information about how stolen data is traded or sold. The plug-in 230 could instruct the requesting content manager 208 to send additional data about the client 202 for law enforcement officers.
        Send a client's content manager 208 additional code for version control, feature update, forensic analysis, behavioral tracking, data destruction, hardware destruction, or any other purpose.
        Send any other process to the content manager 208 that is required by a specific industry expert, revenue model, or other custom purpose. Note that this can be sent at any time, thus allowing the rules for access to client storage 206 to be modified retroactively. The Holy Grail of security, as defined by the Center of Democracy and Technology, is the ability to control sensitive data after it has been released to others. Plug-ins 230 enable this.
        Generate random numbers and characters to provide content managers 208 with unique pointers that replace sensitive data in secure storage 210. This is an example of a plug-in 230 that does not call storage manager 234, but returns a random pointer to content manager 208.
        Many firms use outsourcing as a way to manage increasing costs. For example, inventory control has traditionally been considered a core capability, but increasing services from firms like UPS and FedEx permit freight companies to manage a firm's inventory. In the same way, the increasing costs and skill required to manage sensitive data makes this process an outsourcing candidate. Plug-ins 230 provide the framework for trusted firms to manage sensitive data as well as many of the applications 222 that access this sensitive data. For example, an auditing firm could process a client's human resources while providing assurances that Sarbanes-Oxley, HIPAA, GLB, and all other regulations are being met. This provides new revenue models for, say, auditing firms while permitting their client firms to reduce liabilities, save money, and focus on their core capabilities.
        Another plug-in 230 example is for firms that manage sensitive data that must be sent overseas for outsourced applications. This permits outsourcing to continue without the need to send large amounts of sensitive data overseas.
        Another is for as firm that uses the present invention to store critical encryption keys or other critical components of a client application 222. In this embodiment, plug-ins 230 could use secure server 204 or its own storage to archive these keys and/or critical components. This value-added service could prevent a catastrophic loss of data if the encryption keys or critical data is lost by a firm.
        Another is logging critical encryption keys for safe storage.
        At regular intervals set by a system administrator, a plug-in 230 can contact one or more client devices 202 to ensure that they are still connected to the secure server 204. If they are not, then the plug-in 230 and/or events manager 232 can take the appropriate action. For example, access can disallowed and a supervisor can be notified. In another preferred embodiment, the content manager 208 can notify a plug-in 230 at regular intervals.

Plug-ins 230 turn the capabilities of the present invention into a flexible, open platform for many uses related to data security, tracking, revenue, theft, forensics, and resolution.

Data Layer—Getting Sensitive Data From the Secure Server

    
    


When application 222 gets records from client storage 206, it communicates with content manager 208 in a way that is transparent and seamless in most cases, thus requiring no program changes in application 222 (if changes are required, they are discussed in Enterprise System Upgrades).
FIG. 11 describes one embodiment of how the content manager 208 processes a request to get a record from client storage 206. Each field is examined by content manager 208. If the field contains a random pointer, it is passed to the secure server 204 and, with correct authentication, gets sensitive data back that is then put back into the field. When all fields have been examined, the record is released to the application 222. Note that the record with sensitive data is not put in client storage 206.
FIG. 12 illustrates how each content manager 208 request to get sensitive data is processed on the secure server 204. If the request does not authenticate, then the events manager 232 is notified so that the appropriate action(s) are be taken and/or error condition(s) set. Error values may be a blank value, an erroneous value, or any other value as defined by a system administrator.
If the request does authenticate, then one or more pre-processing plug-ins 230 may be executed, the storage manager 234 uses pointer and index to locate the sensitive data in secure storage 210, and one or more post-processing plus-ins 230 may be executed. If there are no error conditions from the plug-ins 230 or retrieval, the sensitive data is released to the content manager 208. In another preferred embodiment, multiple fields may be retrieved from secure server 204 at once rather than one at a time.
Data Layer—Putting Sensitive in the Secure Server
When the application 222 wants to put records in client storage 206, it communicates with content manager 208 in a way that is transparent and seamless, thus requiring no program changes in application 222 (if changes are required, they are discussed in Enterprise System Upgrades).
FIG. 13 describes one embodiment of how content manager 208 processes a request to put a record in client storage 206. Each field is examined by content manager 208. If the field contains sensitive data, it is passed to the secure server 204 and, with correct authentication, receives a random pointer that replaces the sensitive data. When all fields have been examined, the record is put in client storage 206. Note that the sensitive data is not put in client storage 206.
FIG. 14 illustrates how each content manager 208 request to put sensitive data is processed on secure server 204. If the request does not authenticate, the events manager 232 is notified so that the appropriate action(s) are be taken and/or error condition(s) set. This error value may be a blank value, an erroneous value, or any other value as defined by a system administrator.
If the request does authenticate, then one or more pre-processing plug-ins 230 may be executed. The storage manager 234 determines the following: if automatic archiving is required, then a new random pointer is generated by a plug-in 230 and updated in index 246. If automatic archiving is not required, then the same random pointer is used. The sensitive data is put in secure storage 210. One or more post-processing plus-ins 230 may be executed, and the random pointer is returned to the content manger 208.
Applications that do not require archiving in secure storage 210 include Password Manager because old passwords are never needed. Most applications will require archiving because data may be shared, backed-up, or have multiple versions in use at the same time. In this case, each version of each table in client storage 206 must be able to retrieve its original sensitive data from secure server 204. In another preferred embodiment, multiple fields may be put in secure server 204 at once rather than one at a time.
Storage Manager
Storage manager 234 gets sensitive data from and puts sensitive data in secure storage 210. Storage manager 234 uses index 246 to rapidly determine the correct location in secure storage 210. Index 246 may include any method, including indexing or hashing. For example, FIG. 15 illustrates how the storage manager 234 uses random pointer and index 246 to locate the sensitive data in secure storage 210. Each item, such as SSN 302, DOB 304, Name 306, and Address 308, is put in a separate location in secure server 204. This ensures that triangulation and inference attacks cannot glean sensitive data from the relationship of different values.
For example, some statisticians have shown that knowing a person's date of birth and five digit zip code uniquely identifies them over 90% of the time. The present invention prevents this because date of birth and zip code are not put in index 246 or secure storage 210 in a way that can be associated.
Index
FIG. 16 illustrates how the index 246 takes a random pointer from storage manager 234 and uses it to locate an address in index 246. This address contains sensitive data in secure storage 210. In the preferred embodiment, index 246 is any indexing method that permits using the random pointer to rapidly access the address in secure storage 210 of the desired sensitive data.
Index 246 may be stored across multiple physical servers to reduce the chance that a single trusted person would have access to pointers that could reconstruct an entire record from client storage 206.
Secure Storage
Referring back to FIG. 2, index 246 and secure storage 210 are shown as single files. Other preferred embodiments may include a combination of the following:

    
    
        Mirrored files in separate physical servers. This protects against hardware, power, or environmental failure.
        Index 246 or sensitive data fields in secure storage being stored randomly on different physical servers. This protects against a single trusted person having access to all of the index 246 or sensitive data in secure storage 210.
        Sensitive data fields being split so that that, say, the first 4 bits of each byte is stored in one physical server and the other 4 bits of each byte stored on another physical server. This protects against a single trusted person having access to a sensitive data field.
        Encrypting the data on the client side and on the server side with different keys that are never exchanged. The server keys would be stored in a different location from the data.
    
    


Another embodiment to obfuscate sensitive data fields using bit separation to split the data into separate components is described:

    
    
        Generate n−1 bit strings, where n is less than the number of bits in the original data, to separate the data into n separate pieces. For example using the original bit string 1011, separating into 3 parts would require 2 mask bit strings (1010, 0110).
        To get string part 1 AND the original bit string with the first mask string (1011 AND 1010=1010).
        Next, calculate the remainder by XORing the original bit string with string part 1 (1011 XOR 1010=0001).
        Next take the remainder and AND that with string part 2 (0001 AND 0110=0000).
        Then calculate the reminder by XORing the previous reminder with string part 2 (0000 XOR 0001) to product the final string part.
        This result in 3 string parts (1010, 0000, 0001) which can then be XORed together in any order to reproduce the original data. Also any string part that is all 0's can be discarded to save space.
    
    


Note that index 246 and secure storage 210 can be used to design new ways to ensure that sensitive data is always stored in a way that is safe from hardware, power, environmental, or intentional human failures.
Events Manager
The events manager 232 may be activated by authentication 228, plug-in 230, and/or storage manager 234 requests. In the preferred embodiment, two event types are shown in FIG. 17. The first is an alarm 240 that could include calling a manager on a cell phone and sending a message to authentication rules to deactivate access for all applications on a particular laptop client. The second is an audit trail 242 that could include sensitive data accessed by all laptops so that if one is stolen, a finite number of customers can be notified under California's SB-1386 notification regulation. Note that types of events can be added to the present invention.
Digital Rights Management (DRM)
Another embodiment of present invention is protecting different types of sensitive data in a way that represents a new type of digital rights management. FIG. 18 refers to one embodiment where a manufacturing client 1800 removes critical components 1802 of, say, a DVD so that the DVD may be previewed but not played in full. These critical components 1802 are put in secure storage 210 under the full protection of the present invention. The DVD with the critical components 1802 removed can then be distributed as a sample, and any number of copies can be made by interested parties.
Anyone can load the DVD and can preview the contents of the DVD, but cannot play the entire DVD because the critical components 1802 re missing. With proper authentication from the consumer's client 1804, the secure server 204 can provide the missing critical components 1802 to the original DVD content. The critical components 1802 are seamlessly merged back by content manager 208 so that the original content can be viewed by the consumer, but not in a way that the data from the DVD and critical components 1802 can ever be stored together. Without proper authentication, the secure server 204 can take any action as shown in FIG. 8.
Other embodiments include always authenticating with no rules and using the present invention to count the number of times a DVD is played, what parts of the DVD are the most popular, what other digital content is known to content manager 208 for this individual, and so on. Still other embodiments include DRM protection for different geographical regions that the digital content is sold in, different industries, different media types, or any other market segment. Moreover, other embodiments include different types of digital content, including:

    
    
        PDF newsletters that are always up-to-date.
        Catalogues that are personalized to the color, style, size, shipping preferences, and loyalty program of each individual consumer.
        Software, hardware devices, and games that cannot be used unless a paying customer has authenticated.
        Protecting any other type of digital content, including phone numbers, games, movies, music, pictures, videos, email, program code, art, photos, passwords, news, IP, documents, DVDs, CDs, and patents.
    
    


Note that the present invention can be used to assure that revenue models are tied to people who authenticate before the critical components 1802 are released from secure storage 210. These revenue models could, for example, include every time a DVD is played, validating a membership or subscription, validating a software key, charging for the features used in software and/or hardware. The present invention can be used to retroactively enable new revenue models even after, say, the DVD with critical components removed has been widely distributed. The present invention gives the owner of the original content control for payment, auditing, destruction, or any other purpose.
Forensic Analysis
Another embodiment of present invention is tracking data to enable a unique type of forensic analysis. Current forensic analysis requires access to disk files, tapes, CDs, DVDs, flash drives, memory, and other types of digital storage media.
Referring to FIG. 19, digital content, such as an email message, can be created on client A 1900, sent to client B 1902, and then forwarded to client C 1904. In order to determine that the message is on client C 1904, the forensics analyst must have access to all three clients, and their contents must have been preserved. This is also problematic because the “trail” of messages cannot be broken. This is further problematic because the message can be transferred from one client to another in a manner that cannot be analyzed, such as by CD. This is even further problematic because multiple copies of the message could have been made, and may be in clients that are unknown, inaccessible, destroyed, or even overseas.
The present invention solves these problems because the trail of data is not required in order to perform forensics analysis. Referring to FIG. 8, a client 202 is stolen and can be moved to any location. Copies of client storage 206 can be made and again moved to any location. Any number of stolen data can end up on any number of clients 202 in any number of locations or countries.
As shown in FIG. 2, the present invention protects digital content not by how it got there but by the need to authenticate with the secure server 204 before sensitive data can be used by the client 202. The present invention provides a way to ensure that digital content is:

    
    
        Protected, no matter where it is located or how it got there.
        Paid for, as defined by plug-ins 230.
        Kept up-to-date or changed, as defined by the plug-ins 230 and sensitive data being returned.
        Monitored, as defined by plug-ins 230.
        Destroyed, as defined by plug-ins 230. This could also include software commands to destroy certain hardware components in the client 202.
        Able to have new processes retroactively deployed for future unknown threats, opportunities, and requirements, as defined by plug-ins 230.
    
    


Referring to FIG. 4, one or more forensics processes may be set for any field in client storage 206 that requires processing by secure server 204. This field could be just a dummy tag used for tracking purposes only. One embodiment of a forensics process is a plug-in that puts sensitive data with a unique time/date/user stamp in secure storage for later forensic analysis. Referring to FIG. 8, this can use an unauthorized attempt to determine what copy of the client data was stolen, when it was created, and who was responsible for it. The present invention gives forensics analysts new, simplified tools to track, interpret, monitor, and destroy sensitive data and client hardware that they are stored on.
Addition Client Control
Note that the present invention can be used in general and content manager 208 in particular to seamlessly add functionality to any application 222. This may include the protection, monitoring, controlling, payment, or destruction of sensitive data or just regular data.
European Data Directive Compliance
Many state, federal, and international regulations are following the lead of the European Data Directive. For example, California's SB-1386 was based on the European model that people should be notified if their personal data is put at risk. One of the most stringent requirements of the EU Directive is that personal data cannot move from one country to any another unless the receiving country complies with the EU Directive. This has created problems for many EU firms. For example, firms in England cannot send certain data to its own branch offices in countries like South Africa because the latter is not EU Directive compliant.
Referring to FIG. 20, the present invention solves this problem because sensitive or personal data is stored in a secure server 204 in England and never moves. Client devices, client storage 206, and client applications 222 are all free to move from business to business and from country to country because none contain sensitive or personal data.
If state or federal laws are passed that restrict the movement of sensitive or personal data, the present invention will provide an immediate solution reduce implementation and compliance costs. The present invention helps firms remain nimble in an increasingly costly and uncertain regulatory environment. The present invention provides a framework for protecting sensitive data for outsourcing to local companies and to overseas countries such as India.
An Enterprise Database Example
Referring to FIG. 3, enterprise database applications access tables in storage that contain sensitive data. A typical screen 2100 that accesses this data can be seen in FIG. 21. In the preferred embodiment, a database administrator creates a new table in client storage 206 or secure server 204 that contains information similar to the items shown in FIG. 4. This new table defines the fields in a system that needs protection. The database administrator then applies one or more triggers to tables or fields that need protection, and these triggers read the new table with the defined values. When the table in client storage 206 containing sensitive data has been converted, its resulting contents in client storage 206 can be seen in FIG. 5.
Referring to FIG. 22, application 2200 running on the left without authentication from secure server 204 returns the random pointers from client storage 206 that contain no sensitive data and cannot be cracked or unencrypted. However, application 2202 running on the right with authentication to and from secure server 204 returns sensitive data that is identical to FIG. 21. The present invention protects sensitive data in a way that is transparent and seamless to the enterprise database applications.
An Excel Example
The present invention can be embedded into any application 222. Another preferred embodiment is protecting sensitive data in Microsoft® Excel® files. Excel® is the most widely-used program to store and manage sensitive data. Yet the current ways to protect Excel® files are inadequate because they rely on passwords that can be cracked and encryption that can be complex to use. The present invention removes sensitive data from client storage 206 and puts it in secure servers 204 in a way that the sensitive data cannot be accessed without proper authentication.
One preferred embodiment is defining an entire Excel® file as sensitive data. The only way to access any data in this Excel® file when the client 202 is not connected to the secure server 204 is with client caching 224, which may reduce the overall security of the present invention.
Another embodiment is defining only the data in the Excel file that is sensitive. Referring to FIG. 23, Name 2300, Loan Number 2302, and SSN 2304 contain sensitive data while the rest of the Excel® file (credit score 2306, monthly payment 2308, overdue payments 2310, late charges 2312, other charges 2314 and total charges 2316) does not. A content manager 208 for Excel® has been installed on the client. In this embodiment, this is an Excel® plug-in 230 called “Theft-Proof Data” 2400 which can be seen in the command line.
Referring to FIG. 24A, the columns containing Name 2300, Loan Number 2302, and SSN 2304 have been selected, the Excel® plug-in 2400 has been selected in the command line, and a command to “theft-proof” the selected cells has been clicked. Another preferred embodiment is right-clicking to “theft-proof” the selected cells. These perform the following:

    
    
        Referring to FIG. 2, client 202 communicates with secure server's 204 API 212, authentication 214, plug-ins 216, and data 218 layers.
        All sensitive Excel® cells are stored in secure storage 210.
        All sensitive Excel® cells are displayed with an additional attribute, such as the color red, as defined in settings. This helps the user see what cells are stored on client storage 206 and what cells are stored in secure storage 210.
        A plug-in 230 generates random pointers that content manager 208 places in the comments fields of the selected Excel® cells. These random pointers are later used by content manager 208 to access sensitive data in secure storage 210.
    
    


Whenever this Excel® file is saved or closed, all sensitive data is automatically and transparently stored in secure server 204 according to random pointers in cell comment fields. The sensitive data is blanked out before the Excel® file is stored in client storage 206.
When this Excel® file is opened, all sensitive data is automatically and transparently read from secure server 204. Whenever a theft-proof cell is added, changed, deleted, or the theft-proof attribute is added or removed from a cell, the content manager 208 Excel® plug-in makes the corresponding change in secure server 204. In this embodiment, all data stored in secure storage 210 has auto version control turned on so that different copies of this Excel® file remain synchronized with secure server 204. Opening this Excel® file on any device with proper authentication automatically synchronizes sensitive data again in a way that is automatic and transparent to Excel®, but in a way that does not store the sensitive data on the client.
Referring to FIG. 8, if the Excel® file is stolen or tampered with by accessing secure server 204 without proper authentication, the blank cells stored in client storage 206 are shown and not the sensitive cells stored in secure storage 210, as shown in to FIG. 24B. The pointers stored in comments are random data that do not contain sensitive data.
Another preferred embodiment has a central system administrator controlling which rows, columns, and/or cells are to be protected. Ways to do this include having rules embedded in the Excel plug-in or in Excel® files with pre-defined rows, columns, and/or cells.
Another preferred embodiment is having the plug-in examine the content of values entered into cells and then determining if the cell contains information that should be protected. This embodiment uses a table with different mask values to determine the likely value type:














Mask Value
Likely Value Type









nnn nnn-nnn
Phone number



(nnn) nnn-nnn



nnn nn nnnn
Social Security Number



free-formatted with 2 or 3 words
Name



free-formatted starting with a number
Address



nnnnn
Zip code



nnnnn-nnn










This determination can include examining surrounding cells. For example, if 80% of the values in a column look like a Name, then the entire column can be protected. This automatic determination has the advantage of enforcing protection, even for new Excel® files that a system administrator is unaware of In another preferred embodiment, a central system administrator could set a default that all cells in a new file are protected until the file has been given proper security clearance.

The present invention can be used to protect sensitive data in other Microsoft® Office® products, including Word®, PowerPoint®, Access®, and Outlook®. For each, places to store random pointers that are transparent to the application can be found. These could include hidden text in Word® or PowerPoint®, an additional table in Access®, or an unused portion of an email header for Outlook®. The present invention can also be used to protect sensitive information in other products, such Intuit's Quicken® and Adobe's Acrobat®.
Tracking Attempted Data Theft
In the preferred embodiment, when an Excel® file is protected for the first time, the Excel® plug-in 2400 stores a GIF image file in a cell where it will automatically display when the file is opened. Each time the Excel® file is opened, but before the screen displays, the Excel® plug-in 2400 deletes this GIF image file. Before the Excel® file is stored, this clear GIF image file is put back for the next time it is opened.
In one preferred embodiment, the name of this clear GIF image file includes the address of the events manager, the time, date, and person who authorized the last sensitive data to be accessed by this Excel® file. In another embodiment, the GIF image file includes an address with the Excel® file name, time, date, and person who authorized the last sensitive data to be accessed by this Excel® file.
If the Excel® file is opened without Excel® plug-in 2400, the clear GIF image is not deleted, so it attempts to load a remote file on the events manager 32. If a connection is made, the events manager 232 takes the appropriate action for when someone has opened an Excel® file without the Excel® plug-in 2400 because the potential theft of a protected Excel® file has been tracked. Note that similar ways to track the attempted theft of other types of data, such as Microsoft® Word® and PowerPoint®, and digital content, such as music and movies can be developed.
Referring to FIGS. 25A and 25B, another preferred embodiment is looking for one or more links in a digital content file 2500 being protected. If a link 2502 is present to a target Website 2504, it is changed to point to a tracking Website 2506 that records the event in the same manner as described for the clear GIF image file. The tracking Website 2506 then redirects control to the target Website 2504.
Referring to FIG. 25C, each link in the file is sent to a tracking Website 2506 that:

    
    
        Creates a new link for the digital content file that points to the tracking Website 2506. In the preferred embodiment, this link includes the digital content file name, time, date, and person who authorized the last sensitive data to be accessed by the digital content file 2500. This is passed back to the digital content file 2500.
        Creates a process in tracking Website 2506 that accepts and stores the link data from the digital content file 2500 before passing control to the target Website 2504.

This can be done for all links in the digital content file 2500 or for a specified maximum number of links. A GIF image file can still be placed in the digital content file 2500.

    
    


The advantages of this embodiment include:

    
    
        A search for and removal of clear GIF image files will not prevent tracking the digital content file 2500.
        Any number of tracking Websites 2506 can be established to confuse any process that attempts to identify and remove these tracking links.
        This change is performed by the owner of the digital content, so no copyright violations have occurred.

Excel Plug-In Install Suggestions

    
    


Another similar and preferred embodiment uses a GIF image file to display instructions suggesting that the user install the Excel® plug-in. This GIF image file only appears if the Excel® plug-in is not installed on the client opening the Excel file. This process permits a shared Excel® file to educate users about the present invention. Note that similar ways to automatically suggest downloading the present invention to protect other types of data, such as Microsoft® Word® and PowerPoint®, and digital content, such as music and movies can be developed.
Dynamic Content
The present invention can also be used to keep multiple Excel® files or a single shared Excel® file up-to-date with dynamic content. For example, salesmen opening an Excel® file can always automatically have up-to-the-minute customer status, pricing, and delivery times. The present invention turns Excel® into a dynamic tool with content that is never out-of-date. The present invention turns Excel® into a dynamic tool that is personalized for the current needs of each user.
The present invention can be used to make any Microsoft® Office® product or any other product, service, or application a dynamic tool that is never out-of-date and is always personalized. For example, a catalogue in Word® or PDF format could automatically get personalized content from the secure server 204 for the user who has authenticated. This could include his or her favorite color, style, size, shipping preferences, and loyalty program, and so on. This greatly increases the relevance of the catalogue and value of the catalogue service.
Another embodiment of dynamic content is a PDF newsletter that could have a members-only section. Non-members could see an application form for becoming a member. The present invention can be used to permit digital content to be retroactively controlled after it has been disclosed, something that is currently difficult or next to impossible to achieve.
Data Brokers and Authentication Services
ChoicePoint is an Atlanta-based “data broker” that maintains 19 billion public and private records. Its vision statement says “We strive to create a safer and more secure society through the responsible use of information.” Similarly, its mission statement is “To be the most admired information company worldwide” by being “a demonstrated leader in social contribution, to reaffirm our recognition that a corporation must be a positive force in today's society” and by being “a leader in the responsible use of information, to assure that we strike the proper balance between society's right to know and the individual's right to privacy.”
ChoicePoint sells sensitive data to its customers to help them reduce the risk of conducting business. At the end of January 2005, an article in the Washington Post called ChoicePoint “an all-purpose commercial source of personal information about Americans, with billions of details about their homes, cars, relatives, criminal records and other aspects of their lives.”
ChoicePoint's world changed forever in February 2005 when it was forced to admit that companies had been set up to fraudulently purchase the sensitive data of 145,000 individuals. The immediate fallout included:

    
    
        An unknown but significant number of individuals had their identities stolen.
        A Nigerian man was convicted of fraud for stealing personal information from ChoicePoint.
        ChoicePoint's market valuation fell by $700 million.
        Several class action lawsuits were filed against ChoicePoint.
        The Chairman of the Federal Trade Commission said that ChoicePoint needed to be regulated. In the following year, no laws were introduced that would have prevented the ChoicePoint data theft.

Why Sensitive Data is Collected by Data Brokers and Authentication Services

    
    


Data brokers like ChoicePoint, Equifax, Experian, TransUnion, and LexisNexis collect sensitive data, in part to help their customers mitigate the risk of doing business. In the old days, these companies did business with people they knew. In the digital economy, companies must do business with people they do not know. Data brokers 2600 sell sensitive data to their customers 2602 so that they can make informed decisions about the risks of doing business with individuals and firms they do not know. Referring to FIG. 26, sensitive data is shown in shaded boxes (Name 2604, Address 2604, SSN 2606).
Authentication services like VeriSign collect sensitive data for similar reasons. They pre-screen individuals and firms and give them a digital certificate to authenticate that they are who they say they are. These certificates often contain sensitive data as a part of the authentication process. For this reason, the information passed from authentication services (data broker 2600) like VeriSign to its customers 2602 is similar to data brokers as shown in FIG. 26, although the number and types of fields may be different.
Data broker customers, authentication service customers, and other firms purchase or collect sensitive data in the regular course of doing business. To mitigate business risk, they must have access to sensitive data about prospective customers, employees, trading partners, and so on. It is ironic that knowing that the identity of a consumer has nothing to do with actually making a profit:

ITEMS SOLD times MARGIN/ITEM equals PROFIT

There is nothing in this formula related to sensitive data because the firm makes the same profit irrespective of who the consumer is.

Industry self-regulation has been around since 1996, and new laws have been around since 1998. Both have failed to protect the theft or misuse of sensitive data. This problem will continue to get worse because the amount of information collected is tied directly to the cost of collecting it. And these costs are tied to Moore's Law, which suggests that these costs will continue to fall.
There is a need for a system that manages sensitive data in such a way that mitigates the risk to data brokers, authentication services, their customers, and other firms, without increasing the risks to individuals or firms of having their sensitive data collected, stored, or managed. Moreover, there is a need for a system that manages sensitive data in such a way that firms can make a profit without necessarily having to know the identities of consumers. This would further reduce the risk of having to collect, store, or manage sensitive data.
In the preferred embodiment, sensitive data is controlled by not giving it out in the first place. As Winston Churchill once said, “It's wonderful how well men keep secrets they have not been told.”
How the Present Invention Helps Data Brokers and Authentication Services
The present invention provides a system and method that manages sensitive data to minimize the risk to individuals and firms while still providing sufficient information from data brokers and authentication services to their data broker customers.
The present invention provides four new solutions for protecting sensitive data by simply limiting who has access to it. The following table summarizes the benefits:














For Data Brokers and
For Their Customers



Authentication Services
and for Other Firms


















Centralize and protect
Reduce risk
Reduce risk


sensitive data


Authentication without
Increase revenue
Reduce risk


sensitive data


New services to manage
Increase revenue
Reduce risk


sensitive data


Enterprise system
Reduce risk
Reduce risk


upgrades









While these solutions may be implemented independently, they are shown in the above sequence.

Centralize and Protect Sensitive Data

One major problem is that sensitive data is often stored in multiple places within a firm. For example, ChoicePoint collects and stores information about a person's contact information, marriage history, driving history, motor vehicles, direct marketing history, child support, assets, credit history, and so on. Each of these may contain sensitive data for that person. Another example is that a single bank customer might have a checking account, savings account, mortgage, and car loan, and each may store sensitive data for that customer. This is undesirable for many reasons:

    
    
        Different copies of sensitive data for any given person may contain different values.
        When sensitive data changes, such as when a person moves, the change has to be updated in multiple places. Data synchronization errors occur.
        If there are multiple copies of sensitive data, more people may have access to it. For example, it has been reported that over 4 million records were stolen in 2004 from Softbank in Japan. A subsequent analysis revealed that no less than 135 people had access to the sensitive data. Not surprisingly, the analysis was unable to determine how the sensitive data was stolen.
        Different copies of the sensitive data can end up in very insecure places. For example, it has been reported that a laptop computer containing 200,000 mortgage customers were stolen from the car of a Wells Fargo consultant. Under California's SB-1386 law, each person had to be notified of the theft. Wells Fargo is said to have paid over $10 million to comply with SB-1386.
        When a sensitive data-related law changes or when there is a need to increase the security of sensitive data, the firm has to make these changes everywhere the sensitive data is stored. These costs additional time, require additional money, and dilutes efforts because the firm has to spread its resources to protect sensitive data in more than one location.

The present invention provides a solution to this problem, with the data broker used as an example:

        Referring to FIG. 2, a secure server 204 is created to store and protect sensitive data.
        Referring to FIG. 4, sensitive systems, table names, and field names are identified for the data broker.
        Referring to FIG. 6, sensitive data (2604, 2606 and 2608) is moved to the secure server 204 and a random pointer (2704, 2706 and 2708) replaces it. This process is repeated for each field, record, and table until there is no more sensitive data in the original tables.
        When completed, all sensitive data (2604, 2606 and 2608) is in the secure server 204. Referring to FIG. 27, the data broker's servers and systems are referred to as the data broker client 2700.
        Referring to FIG. 28, each time a record is accessed by data broker client 2700, the pointer (2704, 2706 and 2708) may be used to retrieve sensitive data 2604, 2606 and 2608) from the corresponding field from secure server 204. In this way, the original record can be reconstructed.
    
    


Benefits for the data broker (or any firm using the present invention):

    
    
        Storing all of the sensitive data in one place reduces the risk associated with the collection, storage, and management of sensitive data.
        A single copy of sensitive data eliminates data synchronization errors.
        The reduced number of systems containing sensitive data means that fewer people have access to it.
        Sensitive data is much less likely to end up in very insecure places, such as in laptop computers.
        When a related law changes, or when there is a need to increase the security of sensitive data, the data broker has to make changes in only one place.
        The data broker can focus all of its attention on protecting the sensitive data in a single location with the best people and resources available.

Authentication Without Sensitive Data

    
    


Data brokers and authentication services are a part of a multi-billion dollar industry that is under attack. How can any firm collect, store, manage, and then sell sensitive data to data broker customers without running the risk of its fraudulent use? Even the most reputable customer purchasing this sensitive data can be hacked, share data in error, or have it stolen by a rogue employee. As ChoicePoint has shown, a single occurrence may lead to disastrous consequences for a firm, customers, individuals, and society as a whole.
The present invention ensures that sensitive data (2604, 2606 and 2608) is not released to a data broker customer 2602 in the first place. The present invention provides a system that releases data with pointers (2704, 2706 and 2708) to sensitive data (2604, 2606 and 2608) rather than the sensitive data itself. These pointers (2704, 2706 and 2708) validate the existence of these fields, such as SSN, and the possible later access to these fields, without the risks associated with the collection, storage, and management of sensitive data (2604, 2606 and 2608), as shown in FIG. 29.
Benefits for the data broker:

    
    
        The data broker customer 2602 cannot abuse the sensitive data (2604, 2606 and 2608), even if it wanted to, because the data broker customer 2602 never receives any sensitive data (2604, 2606 and 2608). The sensitive data pointers (2704, 2706 and 2708) that the data broker customer 2602 receives validate that the data broker 2700 has the actual sensitive data (2604, 2606 and 2608) in the secure server 204, but the data broker customer 2602 never actually gets access to the sensitive data (2604, 2606 and 2608) itself. For example, SSN Pointer validates that there is a correct SSN in the secure server 204, but the data broker customer 2602 has no direct access to it (the data broker customer 2602 can instruct the data broker to process the SSN on its behalf, as discussed below). This is a major breakthrough that protects the future viability of data brokers. Reducing these risks decrease the costs of doing business.
        Instead of being a part of the privacy problem, data brokers are now a part of the solution. Those that are best at protecting sensitive data will have a sustainable competitive advantage over data brokers that are not.
        The data broker has the opportunity to generate new revenue models for new services. For example, the chance of sensitive data being abused by a data broker customer is greatly reduced or even eliminated. The data broker can charge a fee for this. In addition, the data broker can underwrite the risk of the sensitive data being incorrect. A fee can also be charged for this.
    
    


Benefits for the data broker customers 2602:

    
    
        The data broker customer 2602 has outsourced one of the most challenging parts of its business—a part that carries an increasing risk with no corresponding upside potential.
        The data broker customer 2602 has the information required to reduce the risk of conducting business with an unknown entity without increasing the risks associated with collecting, storing, and managing sensitive data.
        Reducing these risks decreases the data broker customer's cost of doing business.
        The data broker customer 2602 can focus on what it does best—increasing items sold and margins.
    
    


This example is for data brokers. The present invention can be adapted to work for any firm, including authentication firms such as VeriSign, so that they can offer certificates or some other service that validate the identity of an entity without revealing any sensitive data.
In addition to pointers that are random, another preferred embodiment is a reference number of each record passed from the data broker to the data broker customer may include the following:

    
    
        Customer code uniquely identifies the data broker customer and is used to validate subsequent requests from this customer to ensure that, for example, the data has not been stolen from another data broker customer.
        Customer number uniquely identifies the actual customer for this data broker customer and is needed because other applications may store other records for this actual customer, either locally, at the original data broker, or at another data broker. This “persistent” customer number may be assigned by the data broker customer and remains the same in all applications in all locations.
        Control number may be used by the data broker or data broker customer for version control, hashing, or any other control purpose.

New Services to Manage Sensitive Data

    
    


In addition to helping data broker customers reduce risk, data brokers currently sell sensitive data so that their data broker customers can increase their profits. For example, names and addresses may be sold so that data broker customers 2602 can send promotional material to prospects. But this creates problems:

    
    
        As recent events have shown, sensitive data in the hands of data broker customers can be abused. Even the most reputable firms have rogue employees, and sensitive data only has to be stolen once for lives to be ruined.
        The risks associated with collecting a, individual's sensitive data could one day be more than the lifetime value of that individual. If this occurs, the firm's very survival could be put at risk.
        When sensitive data is sold, it is usually under certain terms and conditions. For example, names and addresses may be sold to be used for a specific time period or a limited number of times. Data brokers “seed” this data with fake names for the sole purpose of auditing how this data is used. This is problematic because (1) it's after-the-fact and too late to protect the abuse, and (2) it represents lost revenue for the data broker.
    
    


The unique solution to this problem is the data broker customer passing requests back to the data broker (or some other trusted third party) for further processing:

    
    
        The reference number (or some other unique identifier) is passed by the data broker customer back to the data broker.
        Also passed back are instructions and, optionally, some other material. For example, this could be “send the attached brochure to all of these people using first class mail” or “do a certain analysis for all people with a SSN beginning with 344.”
        Referring to FIG. 30, the data broker uses the reference number to recreate the original record or parts of the original record. This is done by using the reference number to validate the request and the retrieve the data from data broker server and sensitive data from the secure server 204. When this is completed, the data broker processes the record according to the data broker customer's instructions.
    
    


Benefits for the data broker:

    
    
        Because the data broker is the only party that knows how to convert reference number into the actual sensitive data, all sensitive data is always under the direct control of the data broker.
        For the same reason, the data broker has new “baked in” revenue models. These include fulfillment (mailing promotional materials), further analysis that includes examining sensitive data data, ensuring that the desired results are correct, and so on.
        If data is stolen from the data broker customer, any receiving party can only act upon the stolen data by making a request to the data broker. When this happens, (1) the data broker can reject the request and (2) notify the data broker customer that it has a security problem. This self-auditing process is a major benefit of the present invention. In no case is the sensitive data at risk when data is stolen.
        The economies of scale permit the data broker to manage data broker customer requests in a much more efficient manner than by any single firm. This means that data brokers have higher margin potential as their business grows.
    
    


Benefits for data broker customers:

    
    
        Again, the data broker customer has outsourced one of the most challenging parts of its business—a part that carries an increasing risk without any corresponding upside potential.
        The data broker customer has the information required to reduce the risk of conducting business with an unknown person without increasing the risk's associated with collecting, storing, and managing sensitive data.
        The concept of outsourcing all work related to sensitive data has the potential to free the data broker customer of liabilities associated with sensitive data. This could include order entry, payment processing, order fulfillment, help desks, and all other commodity services that are not core to the data broker customer's mission.
        The data broker customer can focus on what it does best—increasing items sold and margins.
    
    


This example is for data brokers. These same methods or process can be adapted to work for any firm, including authentication firms such as VeriSign, so that it can offer certificates that validate the identity of a person without revealing any sensitive data. Authentication without identification would give firms like VeriSign, new revenue model opportunities.
Enterprise System Upgrades
Regulations for running an enterprise are constantly changing. In addition, the liabilities associated with collecting, storing, and managing sensitive data continues to increase. And Moore's Law suggests that this will increase at an accelerated rate.
These problems are a major concern for firms with large enterprise systems. As the Y2K problem showed, it can cost tens of millions of dollars to upgrade an enterprise system. The main difference between the Y2K problem and the management of sensitive data is that Y2K was a one-time problem, whereas problems related to data theft and new regulation compliance is ongoing. It would be highly desirable if there was a way for a firm to gain control of the management of sensitive data so that changes from new regulations and risks could be dealt with in a more timely and cost-effective manner. Another embodiment of the present invention provides such a solution.
Referring to FIG. 31, any firm 3100 has the same problems managing sensitive data as data brokers have. The solution to this is similar to the solution previously described for data brokers.
Referring to FIG. 32, all fields containing sensitive data (2604, 2606 and 2608) are identified, the contents are moved to a new secure server 204, and the original field has a random pointer (2704, 2706 and 2708) inserted that points to the new location of the sensitive data (2604, 2606 and 2608).
Care must be taken to ensure that the new pointer information is the same type as the sensitive data field that it is replacing. This will help make these changes transparent to the file management system used by the enterprise system. For example, a 9-digit SSN stored in ASCII text should be replaced with a 9-digit or less pointer also stored in ASCII text.
The applications that access the enterprise system may be modified with plug-ins and database triggers as previously described.
Another preferred embodiment is changing application code that manages sensitive data from:

    
    
        move CUSTOMER-SSN to PRINT-SSN

. . . to:

        move sensitivedata(CUSTOMER-SSN) to PRINT-SSN

. . . where “sensitivedata” is a new function that performs certain tasks:

        Authentication that the application and user running this application is permitted access to SSN.
        Ensuring that the reason for and usage of the SSN confirms with best practices, legal requirements and operational procedures, as defined by plug-ins.
        Using the SSN pointer to access the correct SSN data in secure server 204.

Post Content Managers for Devices

    
    


Referring now to FIG. 33, a block diagram of server-client system in accordance with another embodiment of the present invention is shown. In this embodiment, functionality is moved from the content manager as previously described to a pre-content manager and a post-content manager in the device. This solves the potential problem that the application, the hardware that it runs on, and the people who operate it or have access to it all have full access to the sensitive information. This solution can be implemented by:

    
    
        Move part of content manager to pre-content manager and part to post-content manager. For example, pre-content manager could retrieve salary from secure server so that application could calculate tax deductions, while post-content manager could retrieve name and social security number (SSN) from secure server so that payroll checks could be printed by device. In this way, an anonymous salary would not be protected in application and communication lines, but the associated names and SSNs would be.
        Move all of content manager to post-content manager, thus eliminating the need for pre-content manager. For example, a third party contractor printing payroll checks from an anonymous file, either on media such as tape or CD, or directly from remote server, would be completely protected. At no time would the third party have access to or have servers containing or communication lines transmitting sensitive information.
    
    


This embodiment of the present invention protects sensitive information at all times:












Location
FIG. 2
FIG. 33







Secure server
Protected
Protected


Communication between secure server and
Protected
Protected


content manager


Client storage
Protected
Protected


Communication between client storage and
Protected
Protected


content manager


Content manager
Protected
Protected


Communication between content manager
Not Protected
Protected


and application


Application
Not Protected
Protected


Communication between application and
Not Protected
Protected


device


Device
Not Protected
Protected









Other preferred embodiments include protecting sensitive information on devices such as DVD burners because they only authenticate with special blank media what is controlled by a trusted source.
While the described preferred embodiments benefits both the enterprise and the third parties they outsource their sensitive information to, other preferred embodiments offer additional ways to protect this sensitive information. For example, some print jobs are so big that the output is stored on CDs. Reports for brokerage firms are sometimes so large that they are sent by CD rather than on paper.
For example, each client has a data storage, a pre-content manager and a post-content manager. The pre-content manager extracts the sensitive data from the data storage, sends the extracted data to a server for storage, receives a pointer indicating where the extracted data has been stored and replaces the sensitive data on the data storage with the pointer. The post-content manager is communicably coupled with the pre-content manager or the server and one or more media devices, receives the sensitive data from the pre-content manager or the server, and transmits the sensitive data to the one or more media devices. The server is communicably coupled to the one or more clients, wherein the server receives the extracted data from the client, stores the extracted data to a secure storage, generates the pointer and sends the pointer to the client.
The pre-content manager may further receive a first request from the one or more applications for data stored on the data storage, determine whether the requested data includes the sensitive data or the non-sensitive data, provide the non-sensitive data to one or more post-content manager or to the one or more applications, and perform the following steps whenever the requested data includes the sensitive data: send a second request containing the pointer to a server that authenticates the second request, deny the first request whenever the authentication fails, and receive and provide the sensitive data to the one or more post-content manager or the one or more applications whenever the authentication succeeds. In addition, the pre-content manager may also perform one or more corrective or destructive actions whenever the authentication fails and the client is determined to be compromised, lost or stolen. Note that the post-content manger can be integrated into the one or more media devices. The communications between the integrated post-content manager and the pre-content manager can be encrypted.
The post-content manager may further perform the following steps whenever the post-content manager receives the sensitive data from the server or the pre-content manager: sends one or more authentication codes to the pre-content manager or the server, accepts the sensitive data whenever the one or more authentication codes is accepted by the server or the pre-content manager, and rejects the sensitive data whenever the one or more authentication codes is rejected by the pre-content manger or the server.
In another example, an apparatus for protecting sensitive data includes a data storage containing sensitive or non-sensitive data, one or more applications, a communications interface to a remote server having a secure storage, one or more media devices, a pre-content manager and a post-content manager. The pre-content manager is communicably coupled to the data storage, the one or more applications and the communications interface. The pre-content manager controls access to the data storage, extracts the sensitive data and non-sensitive from the data storage, sends the extracted sensitive data to the remote server for storage via the communications interface, receives a pointer indicating where the extracted sensitive data has been stored and replaces the sensitive data on the data storage with the pointer. The post-content manager is communicably coupled with the pre-content manager or the server and one or more media devices. The post-content manager receives the sensitive data or the non-sensitive data from the pre-content manager or the server, and transmits the sensitive data or the non-sensitive data to the one or more media devices.
In yet another example, a method for protecting sensitive data can be provided using a pre-content manager and a post-content manager. The pre-content manager extracts sensitive or non-sensitive data from a data storage on a client, sends the extracted sensitive data to a server for storage, receives a pointer indicating where the extracted sensitive data has been stored and replaces the sensitive data on the data storage on the client with the pointer. The post content manager receives the sensitive data from the pre-content manager and transmits the sensitive data to one or more media devices. The foregoing method can be implemented as a computer program embodied on a computer readable medium wherein the steps are executed by one or more code segments.
Referring now to FIG. 34, one embodiment of the present invention is illustrated to print sensitive information. A record is read from the application and is stored in volatile memory. If the record does not contain a random pointer then printing continues. If the record contains a random pointer the user and/or device and/or device medium is authenticated with one or more of:

    
    
        A password typed into the printer console.
        A key, RFID-enabled card, or other physical security device.
        A biometric reader. For example, highly sensitive print jobs may require that the printer operator has his or her finger on a fingerprint scanner for the entire duration of the print job.
        An attribute unique to the device, such as serial number, IP address, date, and/or time of day.
        An attribute unique to the device medium, such as the type of paper loaded in the printer. Alternatively, plain paper could be loaded with unique codes or identifiers pre-printed on the paper that are read by the printer. Limiting sensitive print jobs to run only on specially controlled paper by a trusted source provides an additional level of security for sensitive information.
        Some other authentication device, method, or procedure.

Note that in FIG. 34 authentication repeats for each record read, not just at the beginning of the print process. This enables real-time control provided by devices such as biometric readers.

    
    


If authentication fails, alarm procedures are activated. This could include a sound device, locking the printer, sending a text message to a supervisor, clearing printer memory, updating a log file, and/or other procedures deemed necessary
With proper authentication, the random pointer is used to retrieve sensitive information from the secure server as previously described. This replaces the pointer in the record read from application. Note that more than one pointer per record will require additional sensitive information to be retrieved and replaced. When all pointers for this record are processed, the record is then printed. When the last record is read from application, job termination procedures are the initiated, which may include clearing printer memory and updating a log file.
Referring to FIG. 35, another preferred embodiment is client A that creates these CDs optionally with a pre-content manager and/or post-content manager. However, the random pointers to certain sensitive information are not converted by client A. The CD is then sent to client B where another application uses another post-content manager to retrieve sensitive information from secure server. In this way, the sensitive information is always protected, even when it passes from device to device and company to company.
Central System Administrator Controls
As previously described, the present invention allows a central system administrator to control which Excel® rows, columns, and/or cells may be automatically protected. One preferred embodiment is having rules embedded in the plug-in for protecting sensitive information in Excel® files. The plug-in examines the content of values entered into cells and then determining if the cell contains sensitive information that should be automatically protected. These embodiments use a table with different “mask values” to determine the likely value type:














Mask Value
Likely Value Type









nnn nnn-nnnn
Phone number



(nnn) nnn-nnnn



nnn nn nnnn
SSN



free-formatted with 2 or 3 words
Name



free-formatted starting with a number
Address



nnnnn
Zip code



nnnnn-nnnn










This determination includes examining surrounding cells. For example, if 80% of the values in a column look like a Name, then the entire column can be automatically protected. This determination has the advantage of enforcing protection, even for new Excel® files that a central system administrator is unaware of In another preferred embodiment, a system administrator could set a default that all cells in a new file are protected until the file has been given proper security clearance.

Another embodiment of the present invention gives a central system administrator information about and control over all potentially sensitive information in all servers, PCs, and devices in the enterprise. When something is located, rules set by the administrator automatically report back and/or protect the sensitive information to immediately eliminate the risk. As a result, the system administrator has a centralized, holistic view of and control over all sensitive information in the enterprise. The administrator schedules a program, process, or plug-in to run automatically on all servers, PCs, and devices in the enterprise so that all files can be scanned, whether or not the administrator is aware of its existence, type, location, or contents.
Referring to FIG. 36, an example of a system administrator's control screen in accordance with one embodiment of the present invention is shown. The control screen includes:

    
    
        Definitions of the file types in the enterprise that may contain sensitive information. These could include Microsoft Office® files, PDF files, Oracle databases, DB2® databases, Sybase® databases, etc.
        How often each file type in the enterprise is to be scanned for sensitive information. This could be every day, week, or month at a pre-defined time of day. In one preferred embodiment, when unprotected information is matched it is automatically protected as previously described.
        Whether or not newly-protected information requires the person responsible for that file to contact the system administrator. For example, if a new Excel® file is located with sensitive information, this might be in violation of company policy, or it may require the person to explain how this file got on his or her laptop, or it might require additional training In one embodiment, if this indicator is not set, then automatic access is given to this person. Otherwise, he or she must contact the system administrator to get permission to access the newly-protected information.
        The mask definitions for each type of sensitive information. For example, a SSN could be in the mask of “nnn nn nnnn” or “nnn-nn-nnnn” and must be 11 characters long.
        The actions to take if the fields being scanned match one of the defined masks. In one preferred embodiment an action could include the automatic protection for just that field, for the entire column in the file, or for the entire file. Alternatively, the entire device could be locked until the user contacts the system administrator.
    
    


New definitions can be added as needed. For example, the present invention permits new regulations to be centrally implemented and enforced without any changes to applications throughout the enterprise.
The present invention includes code that is sent to a program, process, or plug-in in each server, PC, and device in the enterprise. This code runs at the specified interval to scan for sensitive information that is unprotected. In one preferred embodiment, each match performs the following:

    
    
        The field is protected by replacing it with a random pointer as defined above.
        A message is sent to the user about the action taken and/or what to do or who to contact.
        Details of the database or device, file name, file type, value found, action taken, and whether the person is required to contact the system administrator is consolidated and reported to the appropriate person.
    
    


Referring now to FIG. 37, an example of a report format in accordance with one embodiment of the present invention is shown. This report gives a central system administrator a detailed summary of sensitive information potentially at risk in the enterprise and what actions were automatically taken. Additional features may include the training messages sent to file owners who may be unaware of new regulations and how they should be used, or the ability to add new and unique ways to control all sensitive information in the enterprise.
Centralized Storage and Control of Sensitive Data
Referring to FIG. 38, any number of client applications may access secure server. This embodiment of the present invention provides:

    
    
        A system administrator identifies fields containing root data: A list is made of all enterprise fields that require protection by secure server as defined above. Of these, those fields that require additional control, including elimination of data redundancy, increased regulatory compliance, and/or ongoing innovation are identified. These become the “root data” fields.
        Set up secure server and root document: Secure server is set up to store and protect all fields that require protection. These include root data fields, which collectively define the “root document” for the enterprise. Referring now to FIG. 39, a root document could contain Loan Number, Name, SSN, and Date of Birth (DOB).
        Populate the root document: Preferred embodiments for client applications transferring data from various client storage to secure storage include:
        
            Batch updates.
            Database triggers.
            Progressive updates.
            Communications packet inspection between application and client storage.
        
        
        When all client applications process fields in client storage containing root data, or when these fields are protected for the first time, each root data value is checked to see if it is already in the root document in secure storage:
        
            If it is not, then root data is added to root document and a new random pointer is returned to replace the original field value in client storage.
            If it is, then the existing random pointer for this root data is returned to replace the original field value in client storage.

As such, only one copy of each root data value is stored in secure storage and all references to it have the same random pointer.

        
        
    
    


When all files in all client storage have been processed in this way, they contain no sensitive information or data—only random pointers to root data in root document in secure storage. As a result, client applications have seamless, transparent access to root document values.
In one embodiment, additional steps are required to maintain the integrity of root documents, including:

    
    
        Modify root data: If an application has the authority to modify root data, it updates the value in root document, thus making it immediately and retroactively available to all client applications in the enterprise.
        Purge root data: If an application has the authority to purge root data, it purges the value in root document, thus making it immediately and retroactively unavailable to all client applications in the enterprise.
        Special processing: If there is special processing required for any or all client applications, it only has to be done at the root document level in secure storage. An example could be managing a “watch list” of SSNs for Homeland Security. This is significantly simpler, safer, and more cost-effective than having to change, test, and coordinate all client applications.
    
    


Another embodiment is an index in secure storage that identifies the name and location of all client applications referencing the root document. This simplifies complex tasks such as purging or updating all references to a root data in all client storage, for notification appropriate people when additional compliance training is required, and for preparing for compliance audits.
The present invention can be used to simplify additional complex tasks, including:

    
    
        Y2K-type changes: In 2005, the U.S. Congress passed a measure to begin daylight-saving time three weeks early—the first such time change since 1986. A Computerworld poll showed that just 42% of businesses were ready for this change. Not surprisingly, ABC News ran a story titled Daylight Savings: Y2K All Over Again? Whether or not this is a problem, businesses are woefully prepared for these types of changes. The present invention permits an enterprise to identify critical fields to be stored in root documents so that enterprise-wide changes can be made quickly and seamlessly.
        European Data Directive compliance: The EU Directive sets the standard for EU countries, as well as virtually all other industrialized countries outside the U.S. In fact, most U.S. state privacy regulations are following subsets of the EU Directive. Its strict data management includes the requirement for individual permissions to be granted before confidential information can move from one country to another. The present invention permits global access to sensitive information without the need to move it from one country to another. In addition, root documents provide additional compliance with the EU Data Directive, such as the ability to give individuals access to all of their personal information because it is stored in just one location.
        Digital Rights Management (DRM) control for enterprise documents: Applications may use the present invention to keep documents dynamically up-to-date. For example:
        
            Product manuals may seamlessly refer to centralized descriptions, pricing, and delivery information. This means that PDF files, Excel® files, and Websites are always dynamically updated with the most current information.
            PowerPoint® presentations can always have up-to-date contact information. Disposable email addresses can be used to reduce spam.
            Newspapers and newsletters can use root documents to create dynamic content that is never out-of-date. This type of DRM may generate additional revenue. For example, readers who authenticates as paid subscribers may see one type of content, while those who have not paid see another, including an invitation to subscribe.
            The present invention can be used to customize content for each individual. For example, a catalogue could use root documents to retrieve dynamic content that shows preferred brands, colors, payment options, tax and freight, etc. for each individual.

Eliminating Sensitive Data on Compromised or Stolen Devices

        
        
    
    


Referring to FIG. 40, sensitive information is never at risk because it has been previously transferred to secure server. However, it may still be desirable for additional steps to be taken to protect a stolen laptop, PDA, or any other device. This includes warning alarms at a central secure server, denial of requests, and/or downloading software that monitors behavior and/or destroys contents.
The present invention gives individuals direct, instant control of their stolen device. Referring now to FIG. 41, one embodiment is shown. A user accesses the Web to register the device or devices to enable instant device locking In this embodiment, the person registers by entering a reference number such as phone number, device description, and PIN code for each device being registered.
When a device is stolen or missing, the person notifies the present invention as quickly as possible via a TouchTone® phone, IM message, text message, or Website to lock the device. In one preferred embodiment, the present invention instantly locks access to the central server to protect all sensitive information.
Referring now to FIG. 42, as soon as the person has Web access, additional instructions may be given to the device. With appropriate warnings and authentication, the preferred embodiment instructions include:

    
    
        When the device connects to the Internet, deploy security by destroying all data and/or system files. Additional security methods, including destroying the functionality of the device, can be used.
        When the device connects to the Internet, deploy stealth tracking In the preferred embodiment, these include forwarding copies of any text messages sent or received, phone numbers dialed, recordings of any phone calls made, and/or take pictures using the camera. Additional tracking methods can be used.
        Immediately notify law enforcement and the device manufacturer.
        Unlock the device in case it has been found. In this case, any those parties initially will be told that the device has been returned to its proper owner.

As a result, the present invention can provide: protection in seconds without operator assistance; protection if the disk is removed or used as slave; protection if the data is copied; protection when booted in safe mode; protection when run offline; assurance that copied data is protected; data security between the time the device stolen and reported stolen; protection for all devices; and data deletion controlled by the user. Note that the present invention can be modified to add additional authentication, security, tracking, notification, and recovery methods and screens.

    
    


Referring to FIG. 43, if the plug-in is not on the device, then any protected files must have been transferred from another device and may have been stolen. As previously described these files use clear GIF images and/or links pointing to one or more tracking Websites to notify the secure server or other authority of the possible data theft. If the plug-in is on the device, it can check with the secure server to see if the device has been reported stolen. Again, FIG. 40 describes how secure server can deny requests from, plant monitoring software on, and/or destroy contents in the stolen device.
The present invention performs additional levels of security. One embodiment is a program that executes when the device is first booted before the user gains control of the device. This could be with a system-level driver, a change to the BIOS to call a program, or a Windows® driver. Note that the latter is less desirable because it can be bypassed in Windows® Safe Mode. Additional ways to execute this program before the user gains control of the device can also be used.
In one embodiment, the program does not ask the user to authenticate but contacts the secure server to see if the device has been reported stolen. If it has, then the device accepts and executes commands from the secure server.
In another embodiment, the program asks the user to authenticate. Passwords, biometrics, hardware devices, and/or some other authentication methods can be used.
If the user authenticates, the device boot sequence continues and control is given to the user. This embodiment permits the device to be used when it is offline. In another embodiment, the device still uses the program to contact the secure server to provide additional protection.
If the user does not authenticate, then the program tries to contact the secure server. If a connection is not made, then the device locks and does not give control to the user. If a connection is made, the program reports the authentication failure and sees if the device has been reported stolen. The device then accepts and executes commands from the secure server.
In another embodiment, a GIF image is shown when an Excel® file is opened without the plug-in. As shown in FIG. 44, this GIF image may include a link to get additional educational information and a link to download the plug-in. Another embodiment is a warning that opening this file has already started a forensics process to trace the unauthorized access to this file. The GIF image may be changed at any time to meet the changing needs of the enterprise, the different risks the document may face, or any other business needs deemed necessary. When the file is saved, the plug-in may check with the secure server to see if a new GIF image address is needed. Additional methods can be used to increase the ease-of-use, education, installation, and/or security of the present invention.
Protecting Users from Counterfeit Items
Using the systems, devices and methods previously described, the present invention can be used to imprint a globally-unique random serial number or code on a label or item in such a way that the contract manufacturer or third party does not have any control over the globally-unique random serial number or code. For example, the device is imprints the unique random serial number or code on the label or item using: (1) a pre-content manager and a post-content manager (e.g., FIG. 33 and FIG. 35 (Client A)); or (2) a post-content manager without the pre-content manager (e.g., FIG. 35 (Client B)). In FIG. 35, Client A is the owner or primary manufacturer and Client B is the contract manufacturer or third party. The secure server can be operated by Client A or a third-party provider. The Client A media device sends or transmits the information needed by Client B for a manufacturing or production run of the items or labels for Client A. The information may include both sensitive and non-sensitive data/information wherein the sensitive data includes the pointers corresponding to the unique random serial numbers or codes stored on the secure server. The Client B media device imprints the unique random serial number or code on the label or item using the post-content manager, which obtains the unique random serial numbers or codes from the secure server using the pointers.
In one scenario, the primary manufacturer or owner generates the unique random serial number or code and sends it to the secure server as “sensitive data”, which is then accessed by a media device using the pointer to imprint the unique random serial number or code on the item. The unique random serial number or code can be reused after a specified time period whenever the item, label, or label attached to the item has a limited life expectancy (e.g., cigarettes, perishable goods or other consumables). Moreover, the unique random serial number or code can be geographic specific and reused in other geographic locations. The media device can be a printer, a plotter, a label maker, a copier, an inscribing device, a stamping machine, an etching machine or a combination thereof. A customer, user or subsequent purchaser can use the unique random number serial number or code to authenticate the item or label (e.g., authentic, counterfeit, grey market, location restriction, previously sold, rejected batch, etc.), determine whether an expiration date associated with the item or label has been exceeded, or other desired type of authentication/verification.
In another scenario, the primary manufacturer or owner does not generate the unique random serial number or code; the secure server does. As a result, a third party can monitor the actual production runs of a manufacturer to detect illegal or unauthorized production by a contract manufacturer. Moreover, the secure server could monitor or poll the device to detect attempts to circumvent the system (e.g., tampering, production runs that do not use the secure server supplied unique random serial numbers or codes, unexplained or unexpected loss of communication with the device, etc.). The present invention can also be used to track the items through the supply chain and/or record a chain of title.
Referring now to FIG. 45, the present invention provides a system for authentication of an item or a label that includes one or more clients (e.g., contract manufacturers) and a server communicably coupled to the one or more clients. Each client has a data storage, a post-content manager and one or more media devices communicably coupled to the client storage and the post-content manager. Note that the post-content manager can be embedded or integrated into the media device (e.g., a plug-in, an application or other interface). Note also that the data storage can be any type of electronic data storage and may also include physical or electronic media. The server stores one or more unique random serial numbers or codes in a secure storage that can be used to authenticate the item or the label, generates a pointer to each stored unique random serial number or code, and sends the generated pointer(s) to the client for use or for storage in the client data storage. Alternatively, the unique random serial number(s) or code(s) can be generated by the owner or the primary manufacturer and transmitted securely to the server. The server can be operated by an owner, a primary manufacturer or agent (third party) of the owner or primary manufacturer. As a result, the contract manufacturer does not have access to or control over the unique random serial number(s) or code(s).
During or prior to a production run of the item(s) or label(s), the post-content manager obtains the generated pointer(s) from the media device, obtains the unique random serial number(s) or code(s) from the server using the generated pointer(s), and transmits the obtained unique random serial number(s) or code(s) to the media device. The media device then imprints the received unique random serial number(s) or code(s) on the item(s) or the label(s). The labels are printed and attached to the items, and the items can be any type of manufactured or assembled product. The media device can be controlled by one or more applications (not shown) that control the manufacturing or labeling process and/or interface with the client data storage. The pointer(s) can be requested by the one or more clients as part of a production run of the items or labels. The one or more clients may include a computer, a laptop computer, a handheld computer, a desktop computer, a workstation, a data terminal, a manufacturing controller or a combination thereof. The media devices may include a printer, a plotter, a label maker, a copier, an inscribing device, a stamping machine, an etching machine or a combination thereof. The server can be communicably coupled to the one or more clients via a computer network, a telecommunications network, a wireless communications link, a physical connection, a landline, a satellite communications link, an optical communications link, a cellular network or a combination thereof.
The unique random serial number(s) or code(s) can be combined with a contact information or a security mechanism. The contact information may include a phone number, a web address, an instant messaging address, a communications address, or a combination thereof, such that the contact information can be used to certify the authenticity of the item or label. The security mechanism may include a special ink, a special thread, a special code, a holographic symbol, or a combination thereof.
The server can be used to monitor the production run to detect illegal or unauthorized production of the item(s) or label(s), and detects any attempt to circumvent the system. The server may also include an application program interface layer, an authentication layer coupled to the application program layer, a plug-in layer coupled to the authentication layer, a data layer coupled to the plug-in layer, and an events layer coupled to the data layer, the plug-in layer and the authentication layer. Access to and storage of the unique random serial number(s) or code(s) can be governed by one or more rules. The pointer(s) can be subsequently used to access the unique random serial number(s) or code(s) after proper authentication. In addition, the communications between the server and the client can be encrypted.
Now referring to FIG. 46, the system may also include a pre-content manager on each client communicably coupled to the client storage, the post-content manager and the media device. In this case, the pre-content manager receives the pointer(s) indicating where the unique random serial number(s) or code(s) has been stored in the secure storage and stores the pointer(s) in the client data storage. In addition, the post-content manager obtains the unique random serial number(s) or code(s) from the server via the pre-content manager using the pointer(s) instead of directly from the server.
The pre-content manager may also receives a first request from one or more applications for data stored on the data storage, determine whether the requested data includes the unique random serial number(s) or code(s) or a non-sensitive data, provide the non-sensitive data to the post-content manager or to the one or more applications, and perform the following steps whenever the requested data includes the unique random serial number(s) or code(s): sends a second request containing the pointer(s) to a server that authenticates the second request, denies the first request whenever the authentication fails, and receives and provides the unique random serial number(s) or code(s) to the post-content manager whenever the authentication succeeds. In addition, the pre-content manager can perform one or more corrective or destructive actions whenever the authentication fails and the client is determined to be compromised, lost or stolen
The post-content manager may also perform the following steps whenever the post-content manager receives the unique random serial number(s) or code(s) from the server or the pre-content manager: send one or more authentication codes to the pre-content manager or the server, accept the unique random serial number(s) or code(s) whenever the one or more authentication codes is accepted by the server or the pre-content manager, and reject the unique random serial number(s) or code(s) whenever the one or more authentication codes is rejected by the pre-content manger or the server.
In addition, the present invention provides an apparatus for authentication of an item or a label that includes a communications interface to a remote server having a secure storage, a client data storage, one or more media devices communicably coupled to the data storage, and a post-content manager communicably coupled with the server via the communications interface and the media device. The remote server stores one or more unique random serial numbers or codes in the secure storage that can be used to authenticate the item or the label and generates a pointer to each stored unique random serial number or code. The generated pointer(s) are stored on the client data storage. During or prior to a production run of the item(s) or label(s): (a) the post-content manager obtains the generated pointer(s) from the media device, obtains the unique random serial number(s) or code(s) from the server using the generated pointer(s), and transmits the obtained unique random serial number(s) or code(s) to the one or more media devices, and (b) the media device imprint the received unique random serial number(s) or code(s) on the item(s) or the label(s).
Moreover, the present invention provides a method for authentication of an item or a label by storing one or more unique random serial numbers or codes in a remote secure storage that can be used to authenticate the item or the label, generating a pointer to each stored unique random serial number or code and storing the generated pointer(s) in a data storage of a client. During or prior to a production run of the item(s) or label(s): (a) the generated point(s) are sent from the data storage of the client to one or more media devices, (b) the generated pointer(s) are obtained from the media device using a post-content manager, (c) the unique random serial number(s) or code(s) are obtained from the server via the post-content manager using the generated pointer(s), (d) the obtained unique random serial number(s) or code(s) are sent to the media device, and (e) the received unique random serial number(s) or code(s) are imprinted on the item(s) or the label(s) using the media device. The method can be implemented by a computer program embodied on a computer readable medium wherein the method steps are executed by one or code segments.
The pre-content manager can also perform the following steps: receiving a first request for data stored on the data storage; determining whether the requested data includes the unique random serial number(s) or code(s); providing the requested data whenever the requested data includes a non-sensitive data; and performing the following steps whenever the requested data includes the unique random serial number(s) or code(s): sending a second request containing the pointer(s) to the server, authenticating the second request, denying the second request whenever the authentication fails, retrieving the unique random serial number(s) or code(s) using the pointer(s) and sending the unique random serial number(s) or code(s) to one or more media devices whenever the authentication succeeds. In addition, the pre-content manager can receive one or more authentication codes from the post-content manager, validate the one or more authentication codes, and transmit the unique random serial number(s) or code(s) whenever the one or more authentication codes are valid.
The post-content manager can also perform the following steps: sending one or more authentication codes to the pre-content manager or server; and transmitting the unique random serial number(s) or code(s) to one or more media devices whenever the one or more authentication codes are accepted by the pre-content manager or server.
In one embodiment, the globally-unique random serial number or code (e.g., 132-112-435-111-2) is combined with contact information as illustrated in FIGS. 47A-C. The contact information can be a phone number for phone certification or text messaging certification (FIG. 47A), a Web address for PC, laptop, or PDA certification (FIG. 47B), an instant messaging address for an instant messaging device (FIG. 47C), other suitable communications address, or a combination thereof The contact information can also be generated and controlled by the secure server. Also note that the universal question mark sign, which is common for many languages, can be used along with the unique random serial number or code. Moreover, the label or imprint can have a “scratch off” portion or be combined with other security measures, such as special inks, threads, codes, holographic symbols, etc.
Referring to FIG. 48A, labels are printed or attached to individual product items (as shown) or the information is imprinted directly on the item before the items enter the supply chain. The items can be any manufactured product, e.g., drugs, books, CDs, DVDs, equipment, clothing, accessories, or anything that someone might want to counterfeit. At any time, anyone can use the contact information to contact secure server either by phone (including text messaging), instant messaging device, or Web-enabled device. In particular, anyone, such as a potential consumer, can use the present invention to certify that the item being purchased is authentic against: (1) a missing or invalid serial number; (2) the item has been previously sold and is not supposed to be resold; (3) an item beyond its expiration date; (4) an item is outside its authorized location (e.g., grey market goods); and/or (5) the item is part of” a rejected or recalled batch. If it is not, then the person is immediately notified and certification fails. The notification or confirmation message to the person may include instructions, promotional message(s), advertising or other information. In addition, secure server can immediately notify the proper authorities (e.g., law enforcement or governmental authority, primary manufacturer, distributor, retailer, etc.) and take additional actions as deemed necessary. Note that the customer's device does not require any special software or hardware, so that prepaid phones/pay phones or other “dumb” devices can be used in third world or remote locates to check the certification of an item.
Similarly with respect to FIG. 48B, the same steps from FIG. 46A may be taken to certify a service that is represented by, for example, an accompanied support manual or printed certificate. In this case the proper authorities may also include a publisher or training center, etc. Anyone with a phone or Web-enabled device can use the present invention to quickly certify that the service being considered is genuine.
FIG. 49 refers to one embodiment of a phone call using the present invention. The sequence of questions and secure server actions are shown as a caller tries to certify the authenticity of a product or service:
Three questions are asked:

    
    
        the serial number of the item being certified
        the retail identifier where the item is located, and
        whether the item is being purchased.
    
    


The serial number is used to perform item certification, including:

    
    
        serial number is missing or invalid,
        item has been previously sold,
        item's expiration date has expired,
        item in wrong location (for protection against grey market products and services), and
        item's manufacturing batch has been rejected.
    
    


If the item certification fails:

    
    
        the caller is informed,
        the retailer identification is requested,
        the proper authorities are notified,
        the log file is updated, and
        another serial number is requested.
    
    


If the item certification passes:

    
    
        the caller is informed,
        the caller is asked if the item is being purchased,
        if being purchased, the retailer identification is requested,
        the log file is updated, and
        the phone call is terminated.

Note that the process/questions can be changed to accommodate Web access, IM access, or text messaging. Moreover, location information can be obtained from the communications device rather than the user or retailer information. Non verbal communication can also be used—once the code has been entered, a color or tone representing certification pass/fail is sent to the device.

    
    


One embodiment of managing items that fail certification includes multiple notification actions:














Notify
Notify



Manufacturer
Law Enforcement


















Previously sold: this serial number has previously been sold and
Call immediately
Call immediately


should not be sold again


Expiration: this serial number is being sold outside the timeframe
Just log
n/a


defined by the product batch and should not be sold


Location: this serial number is being sold outside the intended
Just log
Call immediately


location defined by the product batch and should not be sold


Batch: this serial number is being sold from a batch that has been
Call immediately
Call immediately


rejected and should not be sold









In another embodiment similar questions and answers are entered into a Web-enabled device, such as a PC, laptop, or PDA. In yet another embodiment the serial number is sent to secure server by instant messenger device and the answers are returned in a text message.
Referring now to FIG. 50, the database tables managing one embodiment of the present invention are shown. The contents and function of each table are described:

    
    
        Manufacturers (primary): contains firms or entities that want to use the present invention to protect its products or services from counterfeit and diversion threats. A primary manufacturer controls the products, batches, retailers, and enforcement tables that are required to deliver certified products and services to consumers.
        Products: contains the details of the various products and services controlled by a primary manufacturer.
        Batches: contains manufacturing details for products or services. In one embodiment, all items in a batch have a common manufacturer, product description, intended location, and expiration date. If an item in a batch is found to be counterfeit, the manufacturer has the option to immediately invalidate the entire batch or just specific serial numbers in that batch. In another embodiment, additional actions may be taken for invalid batches, such as additional tracing procedures. Batch processing puts additional pressure on all parties to control the quality of products and services in the supply chain.
        Batch Log: contains information related to each batch, such as its movement through the supply chain.
        Super-item (optional): is another embodiment that uses groupings of products, such as all bottles of pills on a pallet. In some applications, this would permit a more streamlined management of products and services as they move through the supply chain.
        Items: contains individual products or services in a specific batch. In the pharmaceutical industry, an item could be a bottle of pills. The present invention assigns each item with a globally-unique random serial number that may be used to identify things such as the manufacturer, product, batch, intended location, and expiration date.
        Sub-item (optional): is another embodiment where products where each item is made up of multiple smaller items. In the pharmaceutical industry, an item could be a bottle of pills and the sub-item could be each pill in the bottle. RFID technology is advancing to the point where each pill can contain an eatable tag and therefore be uniquely identified. This embodiment includes tracking each pill, thus further reducing the economic benefit by reducing the size of a run of counterfeit items.
        Item Log: contains all activity for the specific a item, including when it was sold and by which retailer. Optionally, additional information can be logged such as the number of times the item was considered for sale before the actual sale occurred.
        Enforcement: contains the contact information to be used by the present invention when a suspected counterfeit item is identified.
        Retailers: contains the information about the various retailers selling items for each manufacturer. In one embodiment, the location of the retailer can be used to validate the location of the item being sold. This is much more specific and granular than, for example, using the phone number being called to validate the location of a serial number being certified.
        Retailer Log: contains all activity related to this retailer, including items sold, consumer ratings, etc.
        Consumers (optional): In another embodiment the present invention requests or automatically captures caller identification so that the purchase intent and behavior can be logged for later analysis. This caller identity can be matched with product details to warn of drug conflicts, special promotions, and other personalized services.
    
    


The present invention may be used to protect any product, such as Gucci bags, or service, such as medical training manuals that can be uniquely identified. The present invention is unique because it removes the economic benefit of mass-producing counterfeit products or services, and by removing the diversion of products and services to locations outside the intended market.
It will be understood by those of skill in the art that information and signals may be represented using any of a variety of different technologies and techniques (e.g., data, instructions, commands, information, signals, bits, symbols, and chips may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof). Likewise, the various illustrative logical blocks, modules, circuits, and algorithm steps described herein may be implemented as electronic hardware, computer software, or combinations of both, depending on the application and functionality. Moreover, the various logical blocks, modules, and circuits described herein may be implemented or performed with a general purpose processor (e.g., microprocessor, conventional processor, controller, microcontroller, state machine or combination of computing devices), a digital signal processor (“DSP”), an application specific integrated circuit (“ASIC”), a field programmable gate array (“FPGA”) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Similarly, steps of a method or process described herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Although preferred embodiments of the present invention have been described in detail, it will be understood by those skilled in the art that various modifications can be made therein without departing from the spirit and scope of the invention as set forth in the appended claims.

## Claims

1. A system for authentication of an item or a label comprising:
a server device communicably coupled to one or more client devices, the server device comprising a server processor and a server memory device, the server memory device storing server computer readable instructions that when executed by the server processor causes the server processor to perform the steps of:
storing one or more unique random serial numbers or codes in a secure storage that can be used to authenticate the item or the label,
generating a pointer for each of the stored unique random serial numbers or codes stored in the secure storage, and
sending at least one of the generated pointer(s) to a data storage of at least one of the client devices; and

each of the one or more client devices comprising a client processor, one or more media devices, and a client memory device storing client computer readable instructions that when executed by the client processor causes the client processor to perform during or prior to a production run of the item(s) or label(s) the steps of:
obtaining at least one of the generated pointer(s) from the client data storage by the one or more media devices,
obtaining at least one of the unique random serial number(s) or code(s) from the server device using at least one of the obtained generated pointer(s),
transmitting the obtained at least one of unique random serial number(s) or code(s) to the one or more media devices, and

imprinting, by the one or more media devices, the transmitted at least one of the unique random serial number(s) or code(s) on the item(s) or the label(s).

2. The system as recited in claim 1, wherein the unique random serial number(s) or code(s) are generated by the server device.

3. The system as recited in claim 1, wherein:
the one or more client devices are operated by a contract manufacturer and the server device is operated by an owner, a primary manufacturer or agent of the owner or the primary manufacturer;
the contract manufacturer does not have access to or control over the unique random serial number(s) or code(s); and
the labels are printed and attached to the items.

4. The system as recited in claim 3, wherein the unique random serial number(s) or code(s) are generated by the owner or the primary manufacturer and transmitted securely to the server device.

5. The system as recited in claim 1, wherein:
the pointer(s) are requested by the one or more client devices as part of a production run of the items or labels;
the one or more client devices comprise a computer, a laptop computer, a handheld computer, a desktop computer, a workstation, a data terminal, a manufacturing controller or a combination thereof;
the media devices comprise a printer, a plotter, a label maker, a copier, an inscribing device, a stamping machine, an etching machine or a combination thereof; and
the server device is communicably coupled to the one or more client devices via a computer network, a telecommunications network, a wireless communications link, a physical connection, a landline, a satellite communications link, an optical communications link, a cellular network or a combination thereof; and
the items comprise a manufactured product.

6. The system as recited in claim 1, wherein:
the unique random serial number(s) or code(s) are combined with a contact information or a security mechanism;
the contact information comprises a phone number, a web address, an instant messaging address, a communications address, or a combination thereof;
the contact information is used to certify the authenticity of the item or label, or determine whether an expiration date associated with the item or label has been exceeded;
an authenticity confirmation, an authenticity denial, the expiration date, one or more instructions, promotions or advertisements, or a combination thereof are provided whenever the contact information is used; and
the security mechanism comprises a scratch-off portion, a special ink, a special thread, a special code, a holographic symbol, or a combination thereof.

7. The system as recited in claim 1, wherein the server device monitors the production run to detect illegal or unauthorized production of the item(s) or label(s), and detects any attempt to circumvent the system.

8. The system as recited in claim 1, further comprising:
a pre-content manager on each client device communicably coupled to a data storage, the media device and the post-content manager, wherein the pre-content manager receives the pointer(s) indicating where the unique random serial number(s) or code(s) has been stored in the secure storage and stores the pointer(s) in the data storage; and
wherein the post-content manager obtains the unique random serial number(s) or code(s) from the pre-content manager using the pointer(s) instead of from the server device.

9. The system as recited in claim 8, wherein the pre-content manager further receives a first request from one or more applications for data stored on the data storage, determines whether the requested data includes the unique random serial number(s) or code(s) or a non-sensitive data, provides the non-sensitive data to the post-content manager or to the one or more applications, and performs the following steps whenever the requested data includes the unique random serial number(s) or code(s): sends a second request containing the pointer(s) to a server device that authenticates the second request, denies the first request whenever the authentication fails, and receives and provides the unique random serial number(s) or code(s) to the post-content manager whenever the authentication succeeds.

10. The system as recited in claim 8, wherein the post-content manager further performs the following steps whenever the post-content manager receives the unique random serial number(s) or code(s) from the server device or the pre-content manager: sends one or more authentication codes to the pre-content manager or the server device, accepts the unique random serial number(s) or code(s) whenever the one or more authentication codes is accepted by the server device or the pre-content manager, and rejects the unique random serial number(s) or code(s) whenever the one or more authentication codes is rejected by the pre-content manger or the server device.

11. The system as recited in claim 8, wherein the pre-content manager performs one or more corrective or destructive actions whenever the authentication fails and the client device is determined to be compromised, lost or stolen.

12. The system as recited in claim 1, wherein the communications between the server device and the client device are encrypted.

13. The system as recited in claim 1, wherein the server device further comprises:
an application program interface layer;
an authentication layer coupled to the application program layer;
a plug-in layer coupled to the authentication layer;
a data layer coupled to the plug-in layer; and
an events layer coupled to the data layer, the plug-in layer and the authentication layer.

14. The system as recited in claim 1, wherein the pointer(s) is subsequently used to access the unique random serial number(s) or code(s) after proper authentication.

15. The system as recited in claim 1, wherein access to and storage of the unique random serial number(s) or code(s) is governed by one or more rules.

16. A method for authentication of an item or a label comprising the steps of:
storing one or more unique random serial numbers or codes in a remote secure storage by a server device, wherein the one or more unique random serial number or codes can be used to authenticate the item or the label;
generating a pointer for each of the stored unique random serial number or code by the server device;
storing the generated pointer(s) in a data storage of a client device by the client device;
performing a production run of the item(s) or label(s); and
during or prior to a production run of the item(s) or label(s):
(a) sending at least one of the generated pointer(s) from the data storage of the client device to one or more media devices,
(b) obtaining the at least one of the generated pointer(s) from the media device using a post-content manager,
(c) obtaining one or more of the unique random serial number(s) or code(s) from the server device via the post-content manager using the at least one of the generated pointer(s),
(d) sending the obtained one or more unique random serial number(s) or code(s) from the post-content manager to the one or more media devices, and
(e) imprinting the sent one or more unique random serial number(s) or code(s) on the item(s) or the label(s) using the one or more media devices.

17. The method as recited in claim 16, further comprising the following steps performed by a pre-content manager:
receiving a first request for data stored on the data storage;
determining whether the requested data includes the unique random serial number(s) or code(s);
providing the requested data whenever the requested data includes a non-sensitive data; and
performing the following steps whenever the requested data includes the unique random serial number(s) or code(s): sending a second request containing the pointer(s) to the server device, authenticating the second request, denying the second request whenever the authentication fails, retrieving the unique random serial number(s) or code(s) using the pointer(s) and sending the unique random serial number(s) or code(s) to one or more media devices whenever the authentication succeeds.

18. The method as recited in claim 17, further comprising the following steps performed by the post-content manager:
sending one or more authentication codes to the pre-content manager or server device; and
transmitting the unique random serial number(s) or code(s) to one or more media device whenever the one or more authentication codes is accepted by the pre-content manager or server device.

19. The method as recited in claim 17, further comprising the following steps performed by the pre-content manager:
receiving one or more authentication codes from the post-content manager;
validating the one or more authentication codes; and
transmitting the unique random serial number(s) or code(s) whenever the one or more authentication codes are valid.

20. A computer readable storage medium for authentication of an item or a label comprising:
a first computer readable storage medium comprising program instructions when executed by a server computer causes the server computer to perform the steps of:
storing one or more unique random serial numbers or codes in a remote secure storage that can be used to authenticate the item or the label, and
generating a pointer for each of the stored unique random serial numbers or codes;

a second computer readable storage medium comprising program instructions when executed by a client computer causes the client computer to perform the steps of:
storing the generated pointer(s) in a data storage of a client device, and
during or prior to a production run of the item(s) or label(s):
(a) sending at least one of the generated pointers(s) from the data storage of the client device to one or more media devices,
(b) obtaining at least one of the generated pointer(s) from the media device using a post-content manager,
(c) obtaining one or more of the unique random serial number(s) or code(s) from the server computer via the post-content manager using at least one of the generated pointer(s),
(d) sending the obtained one or more unique random serial number(s) or code(s) to the one or more media devices, and
(e) imprinting the sent one or more unique random serial number(s) or code(s) on the item(s) or the label(s) using the one or more media devices.

21. The computer readable storage medium as recited in claim 20, wherein the second computer readable storage medium further comprises program instructions when executed by the client computer causes the client computer to perform the following steps using a pre-content manager:
receiving a first request for data stored on the data storage;
determining whether the requested data includes the unique random serial number(s) or code(s);
providing the requested data whenever the requested data includes a non-sensitive data; and
performing the following steps whenever the requested data includes the unique random serial number(s) or code(s): sending a second request containing the pointer(s) to the server computer, authenticating the second request, denying the second request whenever the authentication fails, retrieving the unique random serial number(s) or code(s) using the pointer(s) and sending the unique random serial number(s) or code(s) to one or more media devices whenever the authentication succeeds.

22. The computer readable storage medium as recited in claim 21, wherein the second computer readable storage medium further comprises program instructions when executed by the client computer causes the client computer to perform the following steps using the post-content manager:
sending one or more authentication codes to the pre-content manager or server computer; and
transmitting the unique random serial number(s) or code(s) to one or more media device whenever the one or more authentication codes is accepted by the pre-content manager or server computer.

23. The computer readable storage medium as recited in claim 20, wherein the second computer readable storage medium further comprises program instructions when executed by the client computer causes the client computer to perform the following steps using the pre-content manager:
receiving one or more authentication codes from the post-content manager;
validating the one or more authentication codes; and
transmitting the unique random serial number(s) or code(s) whenever the one or more authentication codes are valid.

24. The computer readable storage medium as recited in claim 20, wherein the unique random serial number(s) or code(s) are generated by the server computer.

25. The computer readable storage medium as recited in claim 20, wherein:
the one or more client devices are operated by a contract manufacturer and the server computer is operated by an owner, a primary manufacturer or agent of the owner or the primary manufacturer;
the contract manufacturer does not have access to or control over the unique random serial number(s) or code(s); and
the labels are printed and attached to the items.

26. The computer readable storage medium as recited in claim 25, wherein the unique random serial number(s) or code(s) are generated by the owner or the primary manufacturer and transmitted securely to the server computer.

27. The computer readable storage medium as recited in claim 20, wherein:
the pointer(s) are requested by the one or more client devices as part of a production run of the items or labels;
the one or more client devices comprise a computer, a laptop computer, a handheld computer, a desktop computer, a workstation, a data terminal, a manufacturing controller or a combination thereof;
the media devices comprise a printer, a plotter, a label maker, a copier, an inscribing device, a stamping machine, an etching machine or a combination thereof; and
the server computer is communicably coupled to the one or more client devices via a computer network, a telecommunications network, a wireless communications link, a physical connection, a landline, a satellite communications link, an optical communications link, a cellular network or a combination thereof; and
the items comprise a manufactured product.

28. The computer readable storage medium as recited in claim 20, wherein:
the unique random serial number(s) or code(s) are combined with a contact information or a security mechanism;
the contact information comprises a phone number, a web address, an instant messaging address, a communications address, or a combination thereof;
the contact information is used to certify the authenticity of the item or label, or determine whether an expiration date associated with the item or label has been exceeded;
an authenticity confirmation, an authenticity denial, the expiration date, one or more instructions, promotions or advertisements, or a combination thereof are provided whenever the contact information is used; and
the security mechanism comprises a scratch-off portion, a special ink, a special thread, a special code, a holographic symbol, or a combination thereof.

29. The computer readable storage medium as recited in claim 20, wherein the server computer monitors the production run to detect illegal or unauthorized production of the item(s) or label(s), and detects any attempt to circumvent the system.

30. The computer readable storage medium as recited in claim 21, wherein the pre-content manager performs one or more corrective or destructive actions whenever the authentication fails and the client device is determined to be compromised, lost or stolen.

31. The computer readable storage medium as recited in claim 20, wherein the communications between the server computer and the client device are encrypted.

32. The computer readable storage medium as recited in claim 20, wherein the server computer further comprises:
an application program interface layer;
an authentication layer coupled to the application program layer;
a plug-in layer coupled to the authentication layer;
a data layer coupled to the plug-in layer; and
an events layer coupled to the data layer, the plug-in layer and the authentication layer.

33. The computer readable storage medium as recited in claim 20, wherein the pointer(s) is subsequently used to access the unique random serial number(s) or code(s) after proper authentication.

34. The computer readable storage medium as recited in claim 20, wherein access to and storage of the unique random serial number(s) or code(s) is governed by one or more rules.

35. The method as recited in claim 16, wherein the unique random serial number(s) or code(s) are generated by the server device.

36. The method as recited in claim 16, wherein:
the one or more client devices are operated by a contract manufacturer and the server device is operated by an owner, a primary manufacturer or agent of the owner or the primary manufacturer;
the contract manufacturer does not have access to or control over the unique random serial number(s) or code(s); and
the labels are printed and attached to the items.

37. The method as recited in claim 36, wherein the unique random serial number(s) or code(s) are generated by the owner or the primary manufacturer and transmitted securely to the server device.

38. The method as recited in claim 16, wherein:
the pointer(s) are requested by the one or more client devices as part of a production run of the items or labels;
the one or more client devices comprise a computer, a laptop computer, a handheld computer, a desktop computer, a workstation, a data terminal, a manufacturing controller or a combination thereof;
the media devices comprise a printer, a plotter, a label maker, a copier, an inscribing device, a stamping machine, an etching machine or a combination thereof; and
the server device is communicably coupled to the one or more client devices via a computer network, a telecommunications network, a wireless communications link, a physical connection, a landline, a satellite communications link, an optical communications link, a cellular network or a combination thereof; and
the items comprise a manufactured product.

39. The method as recited in claim 16, wherein:
the unique random serial number(s) or code(s) are combined with a contact information or a security mechanism;
the contact information comprises a phone number, a web address, an instant messaging address, a communications address, or a combination thereof;
the contact information is used to certify the authenticity of the item or label, or determine whether an expiration date associated with the item or label has been exceeded;
an authenticity confirmation, an authenticity denial, the expiration date, one or more instructions, promotions or advertisements, or a combination thereof are provided whenever the contact information is used; and
the security mechanism comprises a scratch-off portion, a special ink, a special thread, a special code, a holographic symbol, or a combination thereof.

40. The method as recited in claim 16, wherein the server device monitors the production run to detect illegal or unauthorized production of the item(s) or label(s), and detects any attempt to circumvent the system.

41. The method as recited in claim 40, wherein the pre-content manager performs one or more corrective or destructive actions whenever the authentication fails and the client device is determined to be compromised, lost or stolen.

42. The method as recited in claim 16, wherein the communications between the server device and the client device are encrypted.

43. The method as recited in claim 16, wherein the server device further comprises:
an application program interface layer;
an authentication layer coupled to the application program layer;
a plug-in layer coupled to the authentication layer;
a data layer coupled to the plug-in layer; and
an events layer coupled to the data layer, the plug-in layer and the authentication layer.

44. The method as recited in claim 16, wherein the pointer(s) is subsequently used to access the unique random serial number(s) or code(s) after proper authentication.

45. The method as recited in claim 16, wherein access to and storage of the unique random serial number(s) or code(s) is governed by one or more rules.