Embodiments of the disclosure relate generally to authentication. More specifically, embodiments of the disclosure relate to a system, method, and computer program product for authenticating a sealed product using a digital signature.
To ensure authenticity of a product, a label or mark is typically placed on the product or on a seal of the product. For example, a label or mark may be placed on the box/packaging of the product, a pallet used for delivery of the product, or the bottle/housing containing the product, and such label may be placed such that the label must be broken in order to access the product (for example, a label printed on wrapping around the lid of a bottle is configured to break when the lid is twisted or otherwise lifted to open the bottle). In the alternative, or in addition to a label or mark, a seal may be used, such as a cork, bottle cap, lid, or any other sealing mechanism, to ensure both authenticity and integrity of the product. These techniques may not protect against sophisticated forms of counterfeiting.
For example, a technique commonly used by counterfeiters is to refill an original container (e.g., empty medicine bottle) with counterfeit content (e.g., counterfeit medicine), and sell the counterfeit product as if original. This technique is also commonly used to counterfeit alcoholic beverages. For example, the contents of an expensive bottle of wine may be replaced with a much cheaper wine, the cork replaced, and the bottle resold. Depending on the skill of the counterfeiter, it may be very difficult to recognize that consumed content has been replaced or compromised until the content is closely examined, used, which may be after the point of sale.
Detecting tampering is of special importance in cases where the content itself cannot be marked, such as in products in liquid form (e.g., alcoholic beverages), and even more so where use of a counterfeit content may lead to serious harm, such as in products like medicines and food.
Exemplary embodiments are described with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Additionally, the left most digit(s) of a reference number identifies the drawing in which the reference number first appears.
The following Detailed Description refers to accompanying drawings to illustrate various exemplary embodiments. References in the Detailed Description to “one exemplary embodiment,” “an exemplary embodiment,” “an example exemplary embodiment,” etc., indicate that the exemplary embodiment described may include a particular feature, structure, or characteristic, but every exemplary embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same exemplary embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an exemplary embodiment, it is within the knowledge of those skilled in the relevant art(s) to affect such feature, structure, or characteristic in connection with other exemplary embodiments whether or not explicitly described.
The various exemplary embodiments will so fully reveal the general nature of the disclosure that others can, by applying knowledge of those skilled in relevant art(s), readily modify and/or adapt for various applications such exemplary embodiments, without undue experimentation, without departing from the spirit and scope of the disclosure. Therefore, such adaptations and modifications are intended to be within the meaning and plurality of equivalents of the exemplary embodiments based upon the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by those skilled in relevant art(s) in light of the teachings herein.
Although a seal on a product may appeal intact, and may even include the logo of the manufacturer, a consumer may be concerned that the contents contained therein are counterfeit. Methods and systems are described to allow a consumer (or retailer) to authenticate data stored with the product to provide assurance to a consumer that the product is the original product from the manufacturer.
Environment 100 includes a sealed product 105, an authentication device 110, a communication network 150, a product manufacturer, and a certificate authority 120. Sealed product 105 includes a seal 115 for sealing the contents of sealed product 105. Seal 115 is illustrated as a lid covering the opening of the product, in which case, a lack of a seal, a tear, or puncture therein, may indicate potential tampering. As would be appreciated by a person of ordinary skill in the art, a seal may be any component or components covering the opening of a product. Additionally, or alternatively, seal 115 may be a foil or paper label or the like covering the opening of the product. Sealed product 105 further includes secure element 130 for detecting attempts to tamper with the contents of the packaging.
In the exemplary embodiment, secure element 230 includes tamper detection module 232, data storage module 234, and communication module 236. Data storage module 234 is configured to store a digital signature for the product. A digital signature is created by hashing a set of data and encrypting the hashed data using a cryptographic key, such as a private key. Data storage module 234 may also store the data used to generate the digital signature. In an embodiment, the set of data used to generate the digital signature for the product may include all or a portion of the serial number or other identifier of the product, a one-time password or timestamp, the location of the manufacturer or packager, etc. The digital signature may be generated during manufacture or packaging of the product and stored in secure element 230.
Tamper detection module 232 is coupled to a tamper detection mechanism integrated into the seal (e.g., a wire) or into the product container (e.g., a sensor). Tamper detection module 232 may include circuits and/or processing elements to detect tampering or an attempt to tamper with seal 215. Additionally, tamper detection module 232 is configured to alter the digital signature or the data used to generate the digital signature when an attempt to tamper with the seal is detected. For example, the digital signature is a string of bits. Tamper detection module 232 may alter one or more of the digital signature bits (e.g., change the values) when an attempt to tamper with the seal is detected. When the data used to generate the signature is also stored, tamper detection module 232 may additionally or alternatively modify one or more of the data values stored in data storage 234.
In an exemplary embodiment, communication module 236 includes circuits and/or processing elements to communicate with an authentication device, such as authentication device 110 illustrated in
Returning to
Authentication module 114 is configured to authenticate the digital signature received from secure element 130. When authentication is initiated, authentication module 114 is configured to obtain the data necessary to authenticate the digital signature. Authentication module 114 may request the digital signature and the set of data used to generate the digital signature from a secure element coupled to the product. Alternatively, authentication module 114 may request the digital signature from a secure element and obtain the set of data used to generate the digital signature through alternative methods. For example, some or all of the data may be obtained from the product bar code or may be entered into the authentication device in a conventional manner, such as by use of a keyboard or a keypad. Authentication device 110 may therefore include an interface to an external bar code reader or may include a bar code reader 116. Bar code reader 116 (when present) includes circuits and/or processing elements to read bat code identification information from the product being validated. The authentication device receives the bar code data and parses the received data to extract the data necessary to authenticate the digital signature.
Authentication module 114 is further configured to obtain a cryptographic key (e.g., the public key) for the product. The cryptographic key may be stored in the authentication device or may be obtained in real-time. For example, device 110 may obtain the cryptographic key from a certificate authority over a network. Seal authentication device 110 may therefore include network interface 118 to couple the authentication device to a communication network such as the internet. The authentication device 110 may use portions of the product identification information (e.g., as obtained from a bar code) to identify the certificate authority holding the keys from the product.
At block 305, a digital signature for a product is generated using a set of data. The digital signature may be generated by the manufacturer of the product, the packager of the product, or by another entity in the distribution chain. In this step, the digital signature and/or the set of data used to generate the digital signature is stored in data storage module 234 of the secure element. As described above, the digital signature is generated by hashing data set of data using a hash algorithm (e.g., SHA) and encrypting the hashed data with a cryptographic key assigned to the entity generating the digital signature. The cryptographic key may be a portion of an asymmetric key pair (e.g., a private key). The corresponding portion of the asymmetric key pair (e.g., the public key) may be stored in a certificate authority or other publicly accessible database. The public key can be downloaded and used by an authentication device to authenticate the digital signature.
At block 310, secure element 130 detects an attempt to tamper with the seal of the product. If an attempt to tamper is detected, operation proceeds to block 315. If no tampering is detected, operation remains at step 310.
In block 315, modifications to the digital signature and/or data used to generate the digital signature stored in the secure element are made. For example, the secure element may modify the value of one or more bits in the digital signature and/or one or more bits in the data used to generate the digital signature. Modification of either the digital signature or the associated data will cause authentication of the digital signature using the associated data to fail, and thus, indicate that seal 115 has been tampered with.
At block 320, product authentication is initiated. For example, a user may launch an application on the authentication device (or device containing the authentication device) to initiate the authentication process.
At block 325, the authentication device obtains the information necessary to perform authentication of the product. In this step, the authentication device requests a digital signature for the product from the secure element. The authentication device also obtains the set of data used to generate the digital signature. This data may also be requested from the secure element, obtained by reading a bar code associated with the product, and/or entered by the user of the authentication device. Authentication device 110 also obtains the cryptographic key (e.g., public key) needed to authenticate the digital signature. The cryptographic key may be stored in the authentication device or obtained from an external source such as a certificate authority.
At block 330, authentication device 110 authenticates the received digital signature. Specifically, authentication device 110 hashes the set of data used to generate the digital signature using the same hash function as was used to create the received digital signature. The resulting hash value is referred to herein as the validation hash. The authentication device also decrypts the digital signature using the key corresponding to the key used to generate the digital signature (e.g., the public key). The result is a decrypted hash value. The authentication device then compares the decrypted hash value to the validation hash value. If the decrypted hash value matches the validation hash value, operation proceeds to step 340 where the authentication device 110 indicates to the user that the digital signature is authentic and thus the product has not been compromised. If, on the other hand, decrypted hash value does not match the validation hash value, operation proceeds to step 345 where the authentication device 110 indicates that the digital signature is not authentic, and thus, the product may have been compromised. The indication to the user may be a visual indication and/or may be an audible indication.
Various aspects of the present disclosure can be implemented by software, firmware, hardware, or a combination thereof.
Processing system 400 includes one or more processors, such as processor 404. Processor 404 can be a special purpose or a general purpose processor. Processor 404 may be connected to a communication infrastructure 406 (for example, a bus or network) for communicating with other modules, such as communication module 412, which may provide radio frequency identification communication to sealed product 105 illustrated in
Such processor-executable code, when executed, enable processing system 400 to implement exemplary embodiments of the present disclosure as discussed herein. In particular, the processor-executable programs, when executed, enable processor 404 to implement the processes of the present disclosure, such as the steps in the methods illustrated by flowchart 300 of
It is to be appreciated that the Detailed Description section, and not the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary embodiments of the disclosure as contemplated by the inventor(s), and thus, are not intended to limit the disclosure and the appended claims in any way.
The disclosure has been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed.
It will be apparent to those skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope of the disclosure. Thus the disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
The present application claims the benefit of U.S. Provisional Application No. 61/702,685, filed Sep. 18, 2012, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6869015 | Cummings et al. | Mar 2005 | B2 |
7340602 | Serret-Avila | Mar 2008 | B2 |
7644290 | Ransom et al. | Jan 2010 | B2 |
7652575 | Lyons et al. | Jan 2010 | B2 |
7791484 | Commagnac et al. | Sep 2010 | B2 |
7937593 | Chen et al. | May 2011 | B2 |
8004404 | Izumi et al. | Aug 2011 | B2 |
20050039040 | Ransom | Feb 2005 | A1 |
20060214789 | Posamentier et al. | Sep 2006 | A1 |
20070168680 | Jonas | Jul 2007 | A1 |
20080149518 | Macor | Jun 2008 | A1 |
20090100271 | Harris | Apr 2009 | A1 |
20100117797 | Bauchot | May 2010 | A1 |
20110199225 | Touchberry et al. | Aug 2011 | A1 |
20120093318 | Obukhov et al. | Apr 2012 | A1 |
20130169992 | Panshin et al. | Jul 2013 | A1 |
Number | Date | Country |
---|---|---|
201229768 | Jul 2012 | TW |
Entry |
---|
European Search Report for related European Patent Application No. 13004404.3, mailed Feb. 10, 2014; 5 pages. |
Communication from the Examining Division of the European Patent Office for related European Patent Application No. 13004404.3, mailed Jun. 6, 2014; 5 pages. |
Office Action directed to related Taiwanese Patent Application No. 102132419, mailed May 18, 2015; 8 pages. |
Office Action directed to related Taiwanese Patent Application No. 102132419, mailed Mar. 2, 2016; 9 pages. |
Number | Date | Country | |
---|---|---|---|
20140077928 A1 | Mar 2014 | US |
Number | Date | Country | |
---|---|---|---|
61702685 | Sep 2012 | US |