# US 8,788,814 B2 · Secure data transfer using an embedded system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,788,814 B2 - Document ID: US8788814B2 - Status: Granted - Kind: B2 - Application number: 12/964,467 - Filed: 2010-12-09 - Published: 2011-05-12 - Granted: 2014-07-22 - Earliest claimed: 2003-11-13 - Assignees: Lantronix, Inc. - Applicants: Nicholas J. Witchey - Inventors: Nicholas J. Witchey - Web page: https://patentgrep.com/patent/US8788814B2 ## CPC - H04L 9/0844: {with user authentication or key authentication, e.g. ElGamal, MTI, MQV-Menezes-Qu-Vanstone protocol or Diffie-Hellman protocols using implicitly-certified keys} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method and device for securing data transmission via an embedded system that is operationally coupled to a local device and a remote computing system using a network is provided. The method includes, determining if data received from the remote computing system is secured, handshaking with the remote computing system if the data received is from a new connection; decrypting the secured data; and transmitting the decrypted data to the local device. The method also includes, determining if the data received from the local device is from a new connection, handshaking with the remote computing system if the data received is from a new connection; encrypting the data; and transmitting the encrypted data to the remote computing system. A receiving module determines whether input data needs to be encrypted or decrypted; a processing module for encrypting and/or decrypting input data; and an output module for transmitting encrypted and/decrypted data. ## Claims ### Claim 1 A method for processing insecure data using an embedded system that is operationally coupled to a local device and a remote computing system using a network, comprising: providing at least a first connector and a second connector whereby the first connector provides physical connectivity with the remote computing system and includes at least an RJ-45 jack and further wherein the second connector couples the remote computing system with the local device; determining when the insecure data received from the local device is from a new connection; handshaking with the remote computing system when the insecure data received is from the new connection; the second connector assumes the media access controller (“MAC”) address and the Internet Protocol (“IP”) address of a local device so that an embedded system appears as the local device itself; encrypting the insecure data; and transmitting the encrypted data to the remote computing system. ### Claim 2 (depends on 1) The method of claim 1, wherein data headers are stripped before being sent to the remote computing system. ### Claim 3 (depends on 1) The method of claim 1, wherein the received data is based on TCP format. ### Claim 4 (depends on 1) The method of claim 1, wherein the received data is based on UDP format. ### Claim 5 (depends on 1) The method of claim 1, wherein encryption techniques are based on SSL, SSH and AES standards. ### Claim 6 (depends on 1) The method of claim 1, wherein the first connector includes an RJ-45 jack. ### Claim 7 (depends on 1) The method of claim 1, wherein the first connector and the second connector have random access memory. ### Claim 8 (depends on 1) The method of claim 1, wherein at least one of the first connector or the second connector identifies the media access controller address of the local device so that an embedded system appears as the local device itself. ### Claim 9 (depends on 1) The method of claim 1, wherein the local device is a legacy device. ### Claim 10 A device for securing data transmission between a local device and a remote computing system using a network, comprising: at least a first connector and a second connector, the first connector provides physical connectivity with the remote computing system and includes at least an RJ-45 jack and further wherein the second connector couples the remote computing system with the local device; the second connector assumes the media access controller (“MAC”) address and the Internet Protocol (“IP”) address of a local device so that an embedded system appears as the local device itself; a receiving module that determines whether input data needs to be encrypted or decrypted and when the input data received from the local device is from a new connection; handshaking with the remote computing system when the received input data is from the new connection; a processing module for encrypting and/or decrypting the input data; and an output module for transmitting encrypted and/or decrypted data. ### Claim 11 (depends on 10) The device of claim 10, wherein the receiving module determines if data received from the remote computing system is secured and the processing module de-crypts the secured data. ### Claim 12 (depends on 10) The device of claim 10, wherein the receiving module determines if data received from the local device is from a new connection and the processing module encrypts data before data is sent to the remote computing system. ### Claim 13 (depends on 10) The device of claim 10, wherein data is based on TCP format. ### Claim 14 (depends on 10) The device of claim 10, wherein data is based on UDP format. ### Claim 15 (depends on 10) The device of claim 10, wherein decryption techniques are based on SSL, SSH and AES standards. ### Claim 16 (depends on 10) The device of claim 10, wherein encryption techniques are based on SSL, SSH and AES standards. ### Claim 17 (depends on 10) The device of claim 10, wherein the first connector includes an RJ-45 jack. ### Claim 18 (depends on 10) The device of claim 10, wherein the first connector and the second connector have random access memory. ### Claim 19 (depends on 10) The device of claim 10, wherein at least one of the first connector or the second connector is capable of identifying the media access controller address of the local device so that an embedded system appears as the local device itself. ### Claim 20 (depends on 10) The device of claim 10, wherein the local device is a legacy device.