Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
  • G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
  • G06F21/575—Secure boot
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/60—Protecting data
  • G06F21/602—Providing cryptographic facilities or services
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
  • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
  • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
  • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
  • H04L9/0894—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/06—Authentication
  • H04W12/068—Authentication using credential vaults, e.g. password manager applications or one time password [OTP] applications
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
  • H04L2209/76—Proxy, i.e. using intermediary entity to perform cryptographic operations

Definitions

• the present invention relates to the storage of data on electronic networks and, more particularly although not exclusively, to the secure storage of data which is accessible across an electronic network.
• a common practice is to secure sensitive or secure data on a centralised server is a common practice in the art. In the past this was an efficient way of storing data in that the security resources of a server were considered more secure and efficient than trying to store the same data on the client side device.
• encryption and decryption including shielding the end user from the need to be aware of any encryption or decryption keys.
• encryption and decryption and the securing of a file are carried out on a server (in preferred forms by a methodology requiring data transfer between
• Embodiments of the disclosed invention are designed to address these issues.
• Client server environment an arrangement of computing resources having a topology wherein client devices communicate over a network with at least logically and in most instances usually physically separate server devices.
• the server devices will usually have greater resources than the client devices and the client devices rely, at least in part, on communication with one or more of the server devices to carry out tasks on the client device.
• Encryption/decryption in relation to a file containing data a methodology involving applying an algorithm such that the data is reformatted in a way which renders it substantially indecipherable unless a reverse algorithm is then applied to the data so as to return it to its unencrypted form.
• a "key" is used as a reference element in the algorithm.
• the same key is used to encrypt the data as to decrypt the data.
• the key used for encryption is different to the key used for decryption.
• Encryption is to be distinguished from simple password protection where access to the data within a file requires a password but the data itself within the file is not reformatted.
• Authentication authentication in this specification is a methodology whereby the identity of an entity is
• authentication is often carried out by a combination of a username and a password-that is the provision of a given username with a corresponding password pair comprises authentication.
• the entity may be an individual operating software on a particular platform or the entity may be the platform itself.
• client devices such as a smart phone may qualify as an entity.
• a given user of the smart phone may also qualify as an entity as an alternative to or as well as the smart phone.
• a decryption key for the encrypted data element is stored at the first location.
• the second location is a client device.
• the client device is programmed to execute a Web enabled application which has a storage
• the encrypted data element is stored on the client device utilising the storage capability of the Web enabled application.
• the Web enabled application is a Web browser .
• the web browser executes HTML 5 including the HTML 5 local storage function.
• a method for storing data securely comprising encrypting the data at a first location using a processor located at the first
• the data thus encrypted comprising encrypted data which requires a key to decrypt the encrypted data; the key stored at the first location; the encrypted data transmitted to a second location remote from the first location and stored at the second location until further processing is required to be done on the data at which time the encrypted data is transmitted to the first location and unencrypted by applying the key to a decryption algorithm executed by the processor.
• an apparatus for secure storage of data comprising a first processor at a first location which encrypts data utilising a key; set apparatus further comprising a second processor located at a second location remote from the first location; the data, after encryption, moved over a network to the second processor and stored in association with the second processor until the data is required for execution of an application on the first processor at which time the data is moved back from the second processor to the first processor and the first processor applies the key to a decryption algorithm to decrypt the data for use by the application executing on the first processor .
• login/username account decrypting the encrypted data using the decryption key.
• the separate device is a Web server.
• the user login is a username and
• the decryption key is stored on the server .
• the encryption/decryption is not done on the client.
• the encryption/decryption is done on the server .
• the decryption key is released for use if and only if authentication of a client/service session is validated .
• the environment requires authentication at the user level.
• decryption key is referenced against the authentication .
• authentication is at the user device level.
• the data is a small data quantum.
• the data quantum is 100 MB.
• the data quantum is 50 MB.
• the data quantum is 10 MB.
• the data quantum is 1 MB.
• the data quantum is 0.5 MB.
• the data quantum is 0.1 MB.
• the data is only changed incrementally, if at all, each user session.
• Preferably only some elements of the data are changed, if at all, each user session.
• a method of securely storing data comprising generating a data element at a first location encrypting the data element at the first location thereby to form an encrypted data element transmitting the encrypted data element to a second location remote from the first location storing the encrypted data element at the second location.
• a decryption key for the encrypted data element is stored at the first location.
• the second location is a client device.
• the client device is programmed to execute a Web enabled application which has a storage
• the web enabled application executes HTML 5 including the HTML 5 local storage function.
• the encrypted data element is stored on the client device utilising the storage capability of the Web enabled application.
• the Web enabled application is a Web browser .
• a method for storing data securely comprising encrypting the data at a first location using a processor located at the first location; the data thus encrypted comprising encrypted data which requires a key to decrypt the encrypted data; the key stored at the first location; the encrypted data transmitted to a second location remote from the first location and stored at the second location until further processing is required to be done on the data at which time the encrypted data is transmitted to the first location and unencrypted by applying the key to a decryption algorithm executed by the processor.
• apparatus comprising a first processor at a first location which encrypts data utilising a key; set apparatus further comprising a second processor located at a second location remote from the first location; the data, after encryption, moved over a network to the second processor and stored in association with the second processor until the data is required for execution of an application on the first
• the processor at which time the data is moved back from the second processor to the first processor and the first processor applies the key to a decryption algorithm to decrypt the data for use by the application executing on the first processor.
• Figure 2 Control process for initial storage of data in accordance with an embodiment of the invention.
• Figure 3 Control process for subsequent use of encrypted data in accordance with an embodiment of the invention .
• Figures 4A, B, C describe in diagrammatic form one form of execution of an example embodiment of the invention.
• Figure 5 illustrates in block diagram form a client/server environment suitable for use with any of the described embodiments.
• Figures 6A-P illustrates steps in execution of an example of an embodiment of the invention, and use.
• Figure 1 describes the main components of an example embodiment.
• the client device 10 stores an encrypted version of the data being stored 11.
• the key to decrypt the data 18 is not stored on the client 10 but is stored on a server 14 that is usually
• a network 15 such as the Internet.
• the key 18 to decrypt the data 11 is stored on the server 14 in association with a specific user account 17 in a database of users 16 that have secure access to the server 14.
• the encrypted data 11 is stored in the domain related Local Storagel area 13 of a browser 12 or web enabled application 12 running on the client device 10.
• the server 14 is used for various processes associated with and involving the encryption2, collection and processing of the data which is subsequently stored on the client 10 as an encrypted data file 11.
• Figure 2 discloses the control process for the initial storage and encryption of data.
• the user 40 initiates a secure connection 30 to the server 41 and the client device is logged onto a secure user account 31.
• the server 40 supplies a form for use by the user to format the data to be secured 32 and the user fills out the form with some or all of the data to be secured 33.
• the user then opts to store the data securely on their client device 34.
• the server then retrieves the entered data and processes it 35. Processing may or may not include data verification and integrity checking. Subsequently an
• encryption key is generated by the server 36 and the key is linked to the current user's account 37.
• the key is then used to encrypt the data to be protected 38 and the resulting encrypted data file or files is stored on the client device in the browser or web enabled applications Local Storage for future retrieval 39.
• Figure 3 shows a control process for the subsequent use of encrypted data. Initially the user starts a secure connection 50 and the server then establishes a secure
• the server may present the user with a form to collect information that the user has
• the server retrieves the encrypted data from the client Local Storage 54.
• the server then retrieves the decryption key from the associated username account 55 and the data is decrypted on the server to memory 56 and the data is processed as needed 57.
• the server generates a new encryption key which is used to re-encrypt the data 59 so that it can be safely stored again on the client device Local Storage 60.
• the new encryption key is then stored with the user account in the anticipation of future decryption and use 61.
• Figures 4A, B, C illustrate in diagrammatic form one form of topology and execution of an example embodiment of the invention .
• a storage system 80 relies on a server 81 in communication with client device 82 in this instance over network 83.
• network 83 includes the internet which itself comprises an interconnected network of computers adapted for transmission of packet data 84 to destinations identified in header 85.
• client device 82 will be in electronic communication with network 83 by way of initial link 86 which may comprise a mobile telephone network or other radio communication network such as wifi or the like.
• client device 82 includes a client device memory 87 and client devicse processor 88 whereby code 89 stored in memory can be executed by processor 88.
• the code 89 includes an application adapted to receive commands 90 and data 91 from server 81.
• the commands 90 and data 91 permit creation of form fields Fl - F7 in a form structure 92.
• the form structure 92 is determined on server 81 and forms part of the commands 90 and data 91 transmitted to client device 82 during the unsecured window period.
• Each form field can receive respective data Dl - D7 which may be received from the server 81 as data 91 or may be inserted by a local user of the client device 82.
• the form structure 92 and data 91 is
• Server 81 typically located at a location physically remote from client device 82, received data Dl - D7 over either a secured or unsecured data channel and saves data Dl - D7 in server memory 93 referenced against an entity account 94.
• a secured window period commences when server 81 encrypts data Dl - D7 with reference to at least one key 95 so as to form encrypted data 96 which is then transmitted by server 81 to client device 82 which is to say the client device 82 which formulated data Dl - D7 and from which the data was transmitted to server 81 referenced against entity account 94.
• entity account may be owned by the client device 82 itself.
• entity account may be owned by a user of the code 89 executed on the client device 82 from which the data Dl - D7
• the server 81 references the data both before encryption and after encryption against the entity account 94.
• the server 81 is a web server. In an alternative preferred form the server may serve
• the server 81 deletes all instances of data Dl - D7 from its storage - whether in an encrypted or unencrypted form leaving the only key 95 stored against the entity account 94.
• the client device 82 stores the encrypted data 96 locally in client device memory 87. It is to be noted that the key 95 is not provided to the client device 82.
• a user of client device 82 may be given the option as to whether to invoke the procedure described above.
• FIG. 5 there is illustrated in block diagram form the topology of a typical client/server environment 70 which, in this instance, comprises at least one client device 71 and at least one server 72.
• the client device 71 is in data communication with the server 72 via a data communication channel 73.
• this channel 73 may be unidirectional. In other instances the channel 73 will be bidirectional.
• channel 73 or at least part of it is implemented over the Internet whereby data is
• each packet comprising at least a header containing target address information and a data portion containing a data "payload".
• data for of a webpage on the client 71 resides on server 72 and is delivered from the server 72 to the client 71 on request made by the client to the server.
• the data comprises a series of commands which, upon execution on the client 71, result in communication of data on the client device 71-usually by way of a visual interface, often display of a webpage 74.
• the webpage 74 itself typically is comprised of a multitude of data portions-some of which are constructed by the client 71 executing the commands received from the web server 72 whilst other portions may be comprised of data entered into the client by way of local input output operated by a user of the client device 71.
• HTML HyperText Markup Language
• Figures 6A-P disclose in block diagram format an example application of the system.
• an application 101 runs on the user device 100-in this instance a smart phone.
• user 102 fills out, in this example, their flight details and payment details in fields 105 on a form 103 displayed on touch enabled display 104 of the user device 100.
• the user device 100 is in first data communication with a Web server 106 whereby data
• server 106 may itself be in separate second data communication with server 107.
• Server 107 may for example utilised by financial intermediaries for the purpose of facilitating funds transfer including, for example, payment authorisation as between the parties involved in the transaction 108.
• server 106 constituting the data necessary to trigger transaction 108 whereby the data is communicated electronically to server 106.
• server 106 communicates with server 107 for the purpose of payment authorisation of the transaction 108.
• the example embodiment re-encrypts the data with a new key every time the data is used.
• An alternative embodiment could see the data re-encrypted every time or at a multiple of times that the client and server connect irrespective of whether the data is processed and or used in a form or not.
• another embodiment could see the encrypted data using the same encryption key for an unlimited amount of time.
• the example embodiment uses HTML5 Local Storage to store the encrypted data on the client.
• HTML5 Local Storage to store the encrypted data on the client.
• embodiment could use any storage means available on the client and accessible to a server on a web enabled application or browser .
• the example embodiment is used in the context of data stored and linked to a single domain.
• An alternative embodiment could allow the encrypted data to be accessed across multiple domains using a technique known in the art.
• An example of this is where an iFrame allowing access to local storage for a secure domain area where encrypted data is stored, can be embedded within a web page that accesses and references a different secure domain space on the client, but where data from the iFrame secure area can be passed to and used by the parent or other related pages.
• the example embodiment shows the user being able to optionally encrypt and store the data for future use.
• An alternative embodiment could see this function being an automatic process without the need for the user to opt for the data to be encrypted and stored locally.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Hardware Design (AREA)
• General Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Software Systems (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computing Systems (AREA)
• General Health & Medical Sciences (AREA)
• Bioethics (AREA)
• Health & Medical Sciences (AREA)
• Storage Device Security (AREA)
• Computer And Data Communications (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Priority Applications (11)

Applications Claiming Priority (2)

Publications (1)

Family

ID=59088769

Family Applications (1)

Country Status (8)

Families Citing this family (5)

Citations (7)

Family Cites Families (27)

• 2017
  • 2017-01-03 EP EP17732010.8A patent/EP3394787B1/en active Active
  • 2017-01-03 WO PCT/AU2017/000002 patent/WO2017106938A1/en not_active Ceased
  • 2017-01-03 SG SG11201806423QA patent/SG11201806423QA/en unknown
  • 2017-01-03 CN CN201780013304.3A patent/CN108701200B/zh active Active
  • 2017-01-03 CN CN202311217934.6A patent/CN117494151A/zh active Pending
  • 2017-01-03 CA CA3009229A patent/CA3009229C/en active Active
  • 2017-01-03 US US16/066,029 patent/US11314873B2/en active Active
  • 2017-01-03 AU AU2017204537A patent/AU2017204537A1/en not_active Abandoned
  • 2017-01-03 JP JP2018533811A patent/JP6854529B2/ja active Active
• 2020
  • 2020-09-21 AU AU2020239610A patent/AU2020239610A1/en not_active Abandoned
• 2021
  • 2021-11-12 AU AU2021266356A patent/AU2021266356A1/en not_active Abandoned
• 2024
  • 2024-01-05 AU AU2024200080A patent/AU2024200080A1/en active Pending

Patent Citations (7)

Also Published As

Similar Documents

Legal Events