System and method for authenticating the legitimacy of a request for a resource by a user

• US 10,516,662 B2
• Filed: 12/21/2017
• Issued: 12/24/2019
• Est. Priority Date: 11/27/2012
• Status: Active Grant

• Current Assignee: Robojar Ip Holdings LLC
• Original Assignee: Robojar Pty Ltd
• Inventors: Chester, Jacques Noel Marc
• Primary Examiner(s): Li, Meng
• Assistant Examiner(s): Lapian, Alexander R
• Application Number:
  US15/851,625
• Publication Number:
  US 20180124043A1
• Time in Patent Office: 733 Days
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/6272 by registering files or documents with a third party
• CPC Class Codes: G06F 21/645 using a third party
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: G06F 2221/2135 Metering
• CPC Class Codes: G06Q 2220/12 Usage or charge determination
• CPC Class Codes: H04L 2209/60 Digital content management, e.g. content distribution
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• 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 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/1433 Vulnerability analysis
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 9/0618 Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
• CPC Class Codes: H04L 9/14 using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/30 Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• CPC Class Codes: H04L 9/3242 involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/3263 involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823

Abstract

A method of authenticating the legitimacy of a request for a resource from a resource provider by a user, including providing an authentication process in which a resource provider message is received and de-assembled, the integrity of the user request message is confirmed, a result indicator as to the legitimacy of the resource provider message is created by performing two or more authenticity checks, and an authentication result is sent.

Claims

1. A method of authenticating the legitimacy of a request for a resource by a user, the method being executable in an electronic communication system after the following predetermined steps have occurred:

a structured user message having been created, said structured user message including a resource identifier to identify the resource, and a user identifier to identify the user that is requesting the resource;

a user request message having been assembled, said user request message including the structured user message, and the resource identifier to identify the resource being requested of a resource provider,

the user request message having been sent to the resource provider,

a process having been run by the resource provider receiving the user request message to create a resource provider message that includes a second resource identifier and the user request message,

said method including the steps of;

receiving and de-assembling the resource provider message,

creating a result indicator as to the legitimacy of the resource provider message by at least determining the resource identifier in the structured user message is equal or equivalent to the second resource identifier in the resource provider message, and

sending an authentication result including said result indicator.

2. A method as claimed in claim 1,

wherein, prior to the user request message having been assembled, a verification string derived from at least part of the structured user message having been appended to said structured user message,

wherein the verification string is ciphertext generated using an asymmetric key algorithm;

wherein said method further comprises confirming the integrity of the user request message by checking that the verification string accords with a well-formed structured user message.

3. A method as claimed in claim 2, wherein the structured user message including,

the collation of the structured user message being signed using a signing key A_s to create a ciphertext signature, and

the collation of the structured user message and the ciphertext signature then signed using an encryption key B_e resulting in the structured user message being comprised predominantly of a verification ciphertext,

said structured user message having been encrypted prior to the user request message having been assembled,

wherein said method further comprises confirming the integrity of the user request message by checking the verification ciphertext accords with a well-formed structured user message,

and the step of confirming the integrity of the structured user message comprises the steps of:

decrypting the structured user message using decryption key B_d to obtain the structured user message and the ciphertext signature, and confirming the integrity of the structured user message by using verification key A_v on the structured user message to confirm that the ciphertext signature is valid.

4. A method as claimed in claim 1, wherein the collation of the contents of the structured user message is not repeatable due to an identifier.

5. A method as claimed in claim 1, further comprising an additional step of creating a log entry in a parseable format, and thereafter parsing and processing the plurality of log entries created over time, to generate zero or more suspicious activity criteria based on analysis of the plurality of log entries.

6. A method as claimed in claim 5, wherein each log entry includes a digital signature, to create an unforgettable log entry.

7. A method as claimed in claim 5, wherein creating the result indicator further comprises determining whether any information associated with the resource provider message matches any of the suspicious activity criteria.

8. A method as claimed in claim 1, wherein the structured user message includes a timestamp of when the request was created, and a timestamp authenticity checker is provided, that checks that the timestamp was generated within a predetermined preceding time period.

9. A method as claimed in claim 1, wherein the step of receiving the resource provider message is conducted over a secure channel, at least in part using a TLS client certificate.

10. A method as claimed in claim 1, wherein the resource is a request for an Internet resource over the IP protocol, and the resource provider message includes the user'"'"'s IP address.

11. A method as claimed in claim 1, wherein the structured user message includes a device identifier that identifies the device used to generate the structured user message.

12. An authentication server comprising a memory operably coupled to an electronic communications network,

said authentication server forming part of an authentication system for authenticating the legitimacy of a request for a resource by a user,

said authentication system including one or more resource provider servers, arranged to receive a user request message from the user, said user request message comprising a structured user message including a user identifier and a resource identifier, and said one or more resource provider servers operable to create a resource provider message that includes a second resource identifier and the user request message,

said authentication server being operable to receive and de-assemble said resource provider message as an input,

said authentication server being arranged to determine whether the resource identifier in the structured user message is equal or equivalent to the second resource identifier in the resource provider message,

said authentication server being operable to generate an authentication result including a result indicator as to the legitimacy of the resource provider message based on the result of determining, and

said authentication server being operable to receive the resource provider message, and return the authentication result determined.

13. An authentication server as claimed in claim 12,

wherein, prior to the user request message having been assembled, a verification string derived from at least part of the structured user message having been appended to said structured user message,

wherein the verification string is ciphertext generated using an asymmetric key algorithm;

said authentication server being operable to confirm the integrity of the user request message by checking that the verification string accords with a well-formed structured user message.

14. An authentication server as claimed in claim 13, wherein:

said structured user message having been encrypted prior to the user request message having been assembled,

said authentication server being operable to confirm said verification string accords with a well-formed structured user message according to a predetermined criteria,

wherein the predetermined criteria comprises;

decrypting the structured user message using decryption key B_d to obtain the structured user message and a digital signature, the digital signature having been created by a signing key A_s held by the user, said structured user message having been encrypted by an encryption key B_e held by the user, and

confirming the integrity of the structured user message by applying verification key A_v against the structured user message, to confirm that the digital signature is valid.

15. An authentication server as claimed in claim 12, wherein collations of the contents of the structured user message are not repeatable due to an identifier.

16. An authentication server as claimed in claim 12, wherein the authentication system being operable to store log entries in a parseable format, and to thereafter parse and process the plurality of log entries created over time, to generate zero or more suspicious activity criteria based on using a classification analysis processor.

17. An authentication server as claimed in claim 16, wherein each log entry includes a digital signature, to create an unforgettable log entry.

18. An authentication server as claimed in claim 16, wherein the authentication server being operable to determine whether any information associated with the resource provider message matches any of the suspicious activity criteria.

19. An authentication server as claimed in claim 12, wherein the structured user message includes a timestamp of when the request was created, and being operable to check that the timestamp was generated within a predetermined preceding time period.

20. An authentication server as claimed in claim 12, wherein said communications means utilizes a secure communications channel, in part using a TLS client certificate.

21. An authentication server as claimed in claim 12, wherein the resource is a request for an Internet resource over the IP protocol, and the resource provider message includes the user'"'"'s IP address.

22. An authentication server as claimed in claim 12, wherein the structured user message includes a device identifier that identifies the device used to generate the structured user message.