Systems and methods for trusted path secure communication
A system for establishing a trusted path for secure communication between client devices and server devices, such as between an account holder and a financial institution, can provide the core security attributes of confidentiality (of the parties), integrity (of the information), anti-replay (protection against replay fraud) and/or anti-tampering (protection against unauthorized changes to information being exchanged and/or modules that generate and communicate such information). A messaging layer implementation in favor of a transport layer implementation can provide a trusted path. This infrastructure features secure cryptographic key storage, and implementation of a trusted path built using the cryptographic infrastructure. The trusted path protects against unauthorized information disclosure, modification, or replays. These services can effectively protect against Man-in-the-Middle, Man-in-the-Application, and other attacks.
1. A method for a secure message layer exchange of information on a network between a client device and a server, the method comprising:
receiving, by the server and from the client device, a secured object, wherein the secured object comprises an encrypted message used for authentication of the client device by the server, wherein encrypted message comprises a digital signature, an anti-replay component, an anti-tamper component, and an information component, the information component being encrypted and the anti-tamper component configured to determine whether the client device has a message digest corresponding to a value in a malware signature file;
decrypting, by the server, the secured object to reveal the encrypted message;
validating, by the server, the encrypted message, the validating comprising:
validating, based on a public key associated with the server, the digital signature,
wherein the digital signature is based, in part, on a private key associated with the client device;
validating the anti-replay component to determine if the encrypted message was previously-received and if the encrypted message was received outside a permissible pre-determined time window; and
when the encrypted message is determined not to be previously-received or received outside the permissible pre-determined time window, processing, by the server, the information component.
2. The method of claim 1 , the anti-replay component further comprising a timestamp and the validating the anti-replay component further comprising validating the timestamp.
3. The method of claim 2 , the validating the timestamp further comprising:
comparing the timestamp to a current time as observed by the server; and
discarding the secured object when the timestamp is older.
4. The method of claim 1 , the secured object further comprising a message identifier and the validating the anti-replay component further comprising:
validating the message identifier against a server cache; and
when the message identifier is not stored in the server cache, accepting the secured object; and
when the message identifier is stored in the server cache, discarding the secured object.
5. The method of claim 4 , the validating the anti-replay component further comprising:
storing, by the server, in the server cache, the message identifier and a corresponding timestamp of the anti-replay component of the secured object;
removing, by the server, from the server cache, the message identifier and the corresponding timestamp of the anti-replay component of a previously received stored object, when the corresponding timestamp is outside of the pre-determined time window.
6. The method of claim 1 , wherein the information component comprises any of: an authentication e-biometric, a detection of root or malware infection, a device location, a certificate pinning, a signature based transaction or a device interrogation.
7. The method of claim 1 , wherein the encrypted message includes any of: cryptographic keys, malware lists, application list for detecting whether the client device is rooted or location information.
8. A system, comprising:
a memory; and
at least one processor coupled to the memory and configured to:
receive, by a server and from a client device, a secured object, wherein the secured object comprises an encrypted message used for authentication of the client device by the server, wherein the encrypted message comprises a digital signature, an anti-replay component, an anti-tamper component, and an information component, the information component being encrypted and the anti-tamper component configured to determine whether the client device has a message digest corresponding to a value in a malware signature file;
decrypt, by the server, the secured object to reveal the encrypted message;
validate, by the server, the encrypted message, comprising:
validating, based on a public key associated with the server, the digital signature, wherein the digital signature is based, in part, on a private key associated with the client device;
validating the anti-replay component to determine if the encrypted message was previously-received and if the encrypted message was received outside a permissible pre-determined time window; and
when the encrypted message is determined not to be previously-received or received outside the permissible pre-determined time window, process, by the server, the information component.
9. The system of claim 8 , the anti-replay component further comprising a timestamp and the validating the anti-replay component further comprising validating the timestamp.
10. The system of claim 9 , the validating the timestamp further comprising:
comparing the timestamp to a current time as observed by the server; and
discarding the secured object when the timestamp is older.
11. The system of claim 8 , the secured object further comprising a message identifier and the validating the anti-replay component further comprising:
validating the message identifier against a server cache; and
when the message identifier is not stored in the server cache, accepting the secured object; and
when the message identifier is stored in the server cache, discarding the secured object.
12. The system of claim 11 , the validating the anti-replay component further comprising:
storing, by the server, in the server cache, the message identifier and a corresponding timestamp of the anti-replay component of the secured object;
removing, by the server, from the server cache, the message identifier and the corresponding timestamp of the anti-replay component of a previously received stored object, when the corresponding timestamp is outside of the pre-determined time window.
13. The system of claim 8 , the information component comprising any of: an authentication e-biometric, a detection of root or malware infection, a device location, a certificate pinning, a signature based transaction or a device interrogation.
14. A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:
receiving, by a server and from a client device, a secured object, wherein the secured object comprises an encrypted message used for authentication of the client device by the server, wherein the encrypted message comprises a digital signature, an anti-replay component, an anti-tamper component, and an information component, the information component being encrypted and the anti-tamper component configured to determine whether the client device has a message digest corresponding to a value in a malware signature file;
decrypting, by the server, the secured object to reveal the encrypted message;
validating, by the server, the encrypted message, the validating comprising:
validating, based on a public key associated with the server, the digital signature, wherein the digital signature is based, in part, on a private key associated with the client device;
validating the anti-replay component to determine if the encrypted message was previously-received and if the encrypted message was received outside a permissible pre-determined time window; and
when the encrypted message is determined not to be previously-received or received outside the permissible pre-determined time window, processing, by the server, the information component.
15. The non-transitory computer-readable device of claim 14 , the validating the anti-replay component further comprising:
storing, by the server, in the server cache, a message identifier and a corresponding timestamp of the anti-replay component of the secured object;
removing, by the server, from the server cache the message identifier and the corresponding timestamp of the anti-replay component of a previously received stored object, when the corresponding timestamp is outside of the pre-determined time window.
16. The non-transitory computer-readable device of claim 14 , the anti-replay component further comprising a timestamp and the validating the anti-replay component further comprising validating the timestamp.
17. The non-transitory computer-readable device of claim 16 , the validating the timestamp further comprising discarding the secured object when the timestamp is older than a predetermined threshold subtracted from a current time as observed by the server.
18. The non-transitory computer-readable device of claim 14 , the secured object further comprising a message identifier and the operations further comprising:
validating the message identifier against a server cache; and
when the message identifier is not stored in the server cache, accepting the secured object; and
when the message identifier is stored in the server cache, discarding the secured object.
19. The non-transitory computer-readable device of claim 14 , wherein the information component comprises any of: an authentication e-biometric, a detection of root or malware infection, a device location, a certificate pinning, a signature based transaction or a device interrogation.
20. The non-transitory computer-readable device of claim 14 , wherein the encrypted message includes any of cryptographic keys, malware lists, application list for detecting whether the client device is rooted or location information.