US2018131511A1PendingUtilityA1

Systems and Methods for Dynamic Cypher Key Management

49
Assignee: TAYLOR JAMESPriority: Aug 3, 2016Filed: Aug 3, 2017Published: May 10, 2018
Est. expiryAug 3, 2036(~10.1 yrs left)· nominal 20-yr term from priority
H04L 9/14H04L 63/06H04L 63/062H04L 9/3236H04L 63/0272H04L 9/0861H04L 9/3234H04L 9/0877H04L 63/0428H04L 9/50
49
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Dynamic Cipher Key Management (DCKM) of the present invention enables the protection of sensitive electronic data by assigning symmetric or asymmetric cipher keys using a process that delivers the cipher key to a network endpoint device by means of a key installation, delivery, and storage methodology. DCKM may negate the need to physically touch the network device under protection. Further, DCKM's process is based on a set of operating principles that maintains the highest levels of assurance that the cipher key pairs are issued with only devices that have the right and authorization to create a secure communication path. The DCKM process realizes the same level of security confidence that is only achieved today with conventional token based key management services with respect to the paired devices linked via a cipher key public and private relationship.

Claims

exact text as granted — not AI-modified
1 . A method of protecting security of electronic data transmitted across a network comprising:
 identifying a master device couple to the network;   identifying a slave device coupled to the network;   selectively pairing the slave device and the master with one another; and   dynamically generating a cipher key at the master device and the slave device when electronic data is transmitted such that a secure data path is created between the master device and the slave devices.   
     
     
         2 . The method of  claim 1  further comprising preconfiguring the master device and the with a deterministic model application for establishing the trust relationship of master and slave devices. 
     
     
         3 . The method of  claim 2  further comprising determining whether the master device and the slave device are trusted devices prior to installing the deterministic model application for generating the cipher key. 
     
     
         4 . The method of  claim 2  wherein the deterministic model is selected from the group comprising AES, DES, Triple DES, Diffie-Hellman and RSA. 
     
     
         5 . The method of  claim 2  wherein the deterministic model is based on a blockchain technology. 
     
     
         6 . The method of  claim 1  further comprising identifying master slave device pairs in a network. 
     
     
         7 . The method of  claim 6  further comprising recoding identified master slave device pairs in a network database. 
     
     
         8 . The method of  claim 7  further comprising analyzing master slave device pairs in a network database to identify secure network transmission paths. 
     
     
         9 . The method of  claim 1  further comprising remotely deploying a deterministic model on the slave device. 
     
     
         10 . The method of  claim 9  wherein the deterministic model is an application program. 
     
     
         11 . The method of  claim 1  wherein the master device has an associated administrator

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.