Cryptography method and system for securing data via electronic transmission

• US 10,263,785 B1
• Filed: 05/05/2017
• Issued: 04/16/2019
• Est. Priority Date: 05/06/2016
• Status: Active Grant

• Current Assignee: Autography LLC
• Original Assignee: Autography LLC
• Inventors: Waters, Thomas J., Waters, Richard H., Barrett, Robert N.
• Primary Examiner(s): Ho, Dao Q
• Application Number:
  US15/588,192
• Time in Patent Office: 711 Days
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/034 Test or assess a computer or a system
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/062 for key distribution, e.g. centrally by trusted party cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819
• CPC Class Codes: H04L 9/083 involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

Securing information is increasingly difficult. With technological advances and tools/information sharing between hackers it is becoming even more difficult to ensure that sensitive data remains secure. Disclosed are systems and methods for uniquely securing data for each communication. The disclosed systems and methods allow for transmitting data across multiple boundaries (national, linguistic, operating system, platform, brand, etc.), while maintaining the desired security of the originator'"'"'s data.

Claims

1. A method for encrypting data utilizing a data encryption server, comprising the steps of:

registering, with the server, a data originator;

creating, by the server, a data originator encryption key and a corresponding recipient encryption key, the data originator encryption key and the recipient encryption key being a randomly-generated asymmetrical key-pair set configured for one-time use and not otherwise publicly stored, wherein the randomly-generated key-pair set is utilized for a single data transmission between the data originator peripheral device and the recipient peripheral device and discarded after decryption of the transmitted data, wherein the data to be transmitted is a message and each character and/or space of the message is assigned a randomly-generated character, wherein the randomly-generated character is not repeated, further comprising additional randomly-generated intermittently dispersed characters that do not correspond to the data to be transmitted that further conceal the nature and size of the data to transmitted to the recipient peripheral device;

transmitting, by the server, the data originator encryption key to a data originator peripheral device and the recipient encryption key to a recipient peripheral device;

encrypting data to be transmitted by the data originator peripheral device with the data originator encryption key;

transmitting the encrypted data to the recipient peripheral device;

verifying that the recipient encryption key and the data originator encryption key are from the same randomly-generated key-pair set; and

when the recipient encryption key and the data originator encryption key are verified to be from the same randomly-generated key-pair set, decrypting the encrypted data received by the recipient peripheral device.

2. The method according to claim 1, wherein the additional randomly-generated intermittently dispersed characters are not repeated.

3. The method of claim 2, wherein the encrypted data has a unique file extension.

4. The method of claim 3, further comprising tracking the encrypted data via blockchain technology.

6. The method according to claim 1, wherein the data to be transmitted is a message and certain ones of characters and/or spaced of the message are assigned a randomly-generated character.

7. The method according to claim 6, wherein the randomly-generated character is not repeated.

8. The method according to claim 7, further comprising additional randomly-generated intermittently dispersed characters that do not correspond to the data to be transmitted is further provided to further mask the nature and size of the data to transmitted to the recipient peripheral device.

9. The method according to claim 8, wherein the additional randomly-generated intermittently dispersed characters are not repeated.

10. The method of claim 9, wherein the encrypted data has a unique file extension.

11. The method of claim 10, further comprising tracking the encrypted data via blockchain technology.

5. The method of 2, wherein the additional randomly-generated intermittently dispersed characters are numbers.

12. The method of 1, wherein the assigned randomly-generated character is a number.

13. A system for encrypting data, comprising:

(a) at least a first and second peripheral device;

(b) a data encryption server;

(c) and a network router allowing for communication between the first peripheral device, second peripheral device, and data encryption server;

wherein;

the first peripheral device is a data originator and is configured to communicated with and register with the encryption server;

the encryption server is configured to concurrently create a data originator encryption key and a corresponding recipient encryption key once the first peripheral device registers with the encryption server, the data originator encryption key and the recipient encryption key being a randomly-generated asymmetrical key-pair set configured for one-time use and not otherwise publicly stored, wherein the randomly-generated key-pair set is utilized for a single data transmission between the data originator peripheral device and the recipient peripheral device and discarded after decryption of the transmitted data, wherein the data to be transmitted is a message and each character and/or space of the message is assigned a randomly-generated character, wherein the randomly-generated character is not repeated, further comprising additional randomly-generated intermittently dispersed characters that do not correspond to the data to be transmitted that further conceal the nature and size of the data to transmitted to the recipient peripheral device;

the encryption server is further configured to transmit the data originator encryption key to the first peripheral device and the recipient encryption key to the second peripheral device,

which is a recipient peripheral device;

the encryption server is configured to encrypt data to be transmitted by the data originator peripheral device with the data originator encryption key and transmit the encrypted data to the recipient peripheral device;

at least one of the first peripheral device, the second peripheral device, and/or encryption server are configured to verify that the recipient encryption key and the data originator encryption key are from the same randomly-generated key-pair set; and

if the recipient encryption key and the data originator encryption key are verified to be from the same randomly-generated key-pair set, decrypting the encrypted data received by the recipient peripheral device.

14. The system according to claim 13, wherein the additional randomly-generated intermittently dispersed characters are not repeated.

15. The system of claim 14, wherein the encrypted data has a unique file extension.

16. The system of claim 15, wherein the unique file extension is at least one of an .epub file, a .zip file, or a .tkp file.

17. The system of claim 16, further comprising tracking the encrypted data via blockchain technology.