Digital data authentication

• US 8,949,607 B2
• Filed: 05/08/2013
• Issued: 02/03/2015
• Est. Priority Date: 12/15/2006
• Status: Active Grant

• Current Assignee: Codesealer 2018 ApS
• Original Assignee: CodeSealer A/S
• Inventors: Boesgaard Soerensen, Hans Martin
• Primary Examiner(s): Rao, Andy
• Assistant Examiner(s): ELAHI, SHAN E
• Application Number:
  US13/889,764
• Publication Number:
  US 20130254845A1
• Time in Patent Office: 636 Days
• Field of Search: 713/170
• US Class Current: 713/170
• CPC Class Codes: G06F 21/55 Detecting local intrusion or implementing counter-measures
• CPC Class Codes: G06F 21/554 involving event detection and direct action
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 2221/2119 Authenticating web pages, e.g. with suspicious links
• CPC Class Codes: H04L 2209/76 Proxy, i.e. using intermediary entity to perform cryptographic operations network architectures or network communication protocols using hop-by-hop encryption H04L63/0464
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 9/0662 with particular pseudorandom sequence generator
• CPC Class Codes: H04L 9/3226 using a predetermined code, e.g. password, passphrase or PIN network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083
• CPC Class Codes: H04L 9/3236 using cryptographic hash functions

Abstract

A method for protecting a digital document and user data typed into a digital document is presented. The method comprises computation of an authentication tag when the document is sent from a server. A similar authentication tag is computed when the document is shown on a client. When another document referenced in the document is requested by the client from the server, the authentication tag computed by the client is attached to the request for that other document. The server receiving the request compares the authentication tag it computed with the one it received to verify if the request came from an authentic copy of the document. The method is suitable for protection of online banking, online investment, online shopping, and other electronic applications.

Claims

1. A method of verifying if a request for a second digital document originates from a reference within an authentic copy of a first digital document, the method comprising:

a first computer sends the first digital document to a second computer via a computer network;

the second computer receives a possibly tampered version of the first digital document via the computer network;

the first computer computes a first authentication tag on at least a part of the first digital document;

the second computer computes a second authentication tag on at least a part of the possibly tampered version of the first digital document;

the second computer sends the request for the second digital document referenced in the possibly tampered version of the first digital document to the first computer via the computer network, the request including the second authentication tag;

the first computer receives a possibly tampered version of the request and deducts the second authentication tag;

the first computer considers the possibly tampered version of the request as originating from an authentic copy of the first digital document if the second authentication tag is equal to the first authentication tag; and

the first computer causes the second document to be sent to the second computer only if the second authentication tag is equal to the first authentication tag.

2. The method according to claim 1 further comprising:

the second computer collects the digital data to be included in a request for the second digital document;

the second computer computes a third authentication tag on at least a part of the digital data;

the second computer includes the digital data and the third authentication tag in the request sent to the first computer;

the first computer also deducts the digital data and the third authentication tag from the possibly tampered version of the request;

the first computer computes a fourth authentication tag on at least a part of the digital data attached to the possibly tampered version of the request;

the first computer considers the digital data attached to the possibly tampered version of the request as authentic if the third authentication tag is equal to the fourth authentication tag.

3. The method according to claim 1 wherein the first authentication tag is stored on the first computer from a first point in time when the first digital document is sent to the second computer to a second point in time when the first authentication tag is compared with the second authentication tag, and wherein the transmission of the first digital document from the first computer does not include the first authentication tag.

4. The method according to claim 1 where the first authentication tag is inserted into the first digital document in encrypted or authenticated form by the first computer;

the encrypted or authenticated first authentication tag is included in the request by the second computer;

the encrypted or authenticated first authentication tag deducted from the possibly tampered version of the request is decrypted or verified by the second computer before being compared to the second authentication tag.

5. The method according to claim 1 where the second authentication tag or the third authentication tag is encrypted or authenticated by the second computer and transmitted in encrypted or authenticated form to the first computer.

6. The method according to claim 1 where the first computer is a web server or a proxy server.

7. The method according to claim 1 where the second computer is a web browser.

8. The method according to claim 1 where the first computer refuses to send the second digital document to the second computer if at least one of the possibly tampered version of the first digital document and the digital data is not authentic.

9. The method according to claim 1 where at least one of the second authentication tag and the third authentication tag is computed more than once by the second computer.

10. The method according to claim 9 where at least one of the second authentication tag and the third authentication tag is computed on at least one of the following events:

the document is loaded,

the document is shown,

a link in the document is activated,

script code in the document is activated or executed,

an amount of time has elapsed,

a change has occurred to the possibly tampered version of the first digital document, and

a change has occurred to user data entered into the possibly tampered version.

11. The method according to claim 1 where at least two of said authentication tags are computed on at least two different parts of the possibly tampered version of the first digital document or on at least two different parts of the first digital document.

12. The method according to claim 1 where at least one authentication tag is calculated by at least one of the following,

a hash function,

a message authentication code function, and

an asymmetric digital signature algorithm.

13. The method according to claim 1 where an authentication tag that authenticates at least some of the data in the first digital document is also provided in the first digital document itself.

14. The method according to claim 1 where a computer program is embedded into the first digital document or referenced in the first digital document, the computer program being adapted to calculate at least some of the authentication tags to be included in the request.

15. The method according to claim 1, wherein at least one of said authentication tags is computed by a computer program, and wherein each user or group of users uses a different computer-executable program file to run the computer program.

16. The method according to claim 15 where the computer-executable program file is fabricated from a source code, the computer program including, in said computer-executable program file, at least one embedded value or means for generating at least one value, said value being uniquely selected or uniquely generated for the computer-executable program file, whereby the computer-executable program file is capable of carrying out instructions provided by the source code and of generating a unique output, which depends from said uniquely selected or uniquely generated value.

17. The method according to claim 16 where the embedded means for generating at least one value comprises at least one extractor subfunction.

18. The method according to claim 17 where at least one of the extractor subfunctions is uniquely selected for each computer-executable program file.

19. The method according to claim 1 where at least one reference in the first digital document is replaced by the first computer with a substitute reference;

the substitute reference is unique for the first digital document or for a specific copy of the first digital document;

the first computer maintains a table of substitute references such that it can identify which digital document to send to the second computer when the second computer requests a substitute referenced digital document.

20. The method according to claim 1 where a computer program running on the second computer oversees relevant actions on that computer in order to detect unusual behavior.

21. The method according to claim 20 where the computer program running on the second computer that oversees relevant actions also computes at least one of the authentication tags to be included in the request.

22. The method according to claim 20 where data recorded in order to detect unusual behavior includes at least one of:

timing of input data received from the user,

value of input data received from the user, and

visibility of data to be presented to the user.

23. The method according to claim 20 where the second computer sends a report to the first computer on detected behavior on the second computer.

24. The method according to claim 20 where the second computer stores a copy of at least a part of the last accepted state of user data typed into the possibly tampered version of the first digital document, and wherein, if unusual behavior is detected while the user data in the possibly tampered version of the first digital document is edited, at least a part of the user data in the possibly tampered version of the first digital document is rolled back to the last accepted state by overwriting the at least a part of the user data in the possibly tampered version of the first digital document with the stored copy of the at least a part of the last accepted state.

25. The method according to claim 1 where rules define constraints on the content of those parts of the possibly tampered version of the first digital document not included in calculating the second authentication tag.

26. The method according to claim 25 where the rules define that at least some of those parts of the possibly tampered version of the first digital document not included in calculating the second authentication tag may only be displayed in predetermined parts of the graphical user interface of the second computer.

27. The method according to claim 25 where the rules are included in the first digital document or downloaded from the first computer.

28. The method according to claim 1 where the first computer embeds a value into the first digital document, and wherein at least one authentication tag computed by the second computer depends on that embedded value.

29. The method according to claim 28 where the value embedded into the first digital document is unique for each copy of the first digital document sent from the first computer.