# US 2024/0005031 A1 · Information security systems and methods thereof

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0005031 A1
- Document ID: US20240005031A1
- Status: Published application
- Kind: A1
- Application number: 18/252,755
- Filed: 2021-11-18
- Published: 2024-01-04
- Earliest claimed: 2020-11-23
- Assignees: Biojars Holdings Pty Ltd
- Applicants: Biojars Holdings Pty Ltd
- Inventors: Andrej Simec; Stephen Robert Hogben; Patrick Charles Purcell
- Web page: https://patentgrep.com/patent/US20240005031A1

## CPC

- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- H04L 9/0822: {using key encryption key}
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/6272: {by registering files or documents with a third party}
- H04L 9/0662: {with particular pseudorandom sequence generator}
- H04L 9/0869: {involving random numbers or seeds}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments of the present disclosure provide a system and a method of providing information security to information assets of a user. The information security system provides a more secure way of collecting, retrieving and storing data in one place to the users for their own use as well as for curating and sharing their most precious information assets such as, but not limited to, personal memories and precious information with selected friends and family, both now and in the future. The information security system includes a service management system, an encryption engine, a random data source, a secure third-party storage system, and a distribution and delivery device. The information security system is hack proof as it has high cryptographic strength and maintains high security and also usability/workability for potentially many years and decades in between uses.

## Claims

### Claim 1

An information security system comprising:
a service management system configured to receive at least one information asset from at least one user for storage;
an encryption engine configured to receive the at least one information asset in its component files and unique identifying information of the at least one user from the service management system;
a random number source configured to provide genuine random numbers to the encryption engine, wherein the encryption engine generates one or more encryption keys based on the genuine random numbers;
a distribution and delivery device configured to:
encrypt the at least one information asset using the one or more encryption keys; and store the encrypted information asset; and
a secure third-party storage system configured to:
accept the encrypted information asset for storing securely; and
return the stored encrypted information asset on demand upon presentation of correct credentials to the distribution and delivery device, wherein the distribution and delivery device presents the information asset to the at least one user upon receiving a retrieve request.

### Claim 2 (depends on 1)

The information security system of claim 1, wherein the service management system is further configured to:
receive a network address where the at least one information asset is located from the at least one user; and
retrieve the at least one information asset from the network address for storage.

### Claim 3 (depends on 1)

The information security system of claim 1, wherein the encryption engine is further configured to:
obtain a genuine random number from the random number source;
use the genuine random number to create a unique encryption key, wherein the secure third-party storage system generates another encryption key from a pseudo random number function;
encrypt the at least one information asset by using the unique encryption key;
store the encrypted at least one information asset in the distribution and delivery device; and
send the unique encryption key to the secure third-party storage system, wherein the secure third-party storage system is configured to encrypt the unique encryption key with another encryption key to create an encrypted unique encryption key.

### Claim 4 (depends on 3)

The information security system of claim 3, wherein the secure third-party storage system is configured to:
encrypt the unique encryption key using the another encryption key to create an encrypted unique encryption key;
store the resultant encrypted unique encryption key together with a one-way transformation of the another encryption key;
generate a unique key ID that corresponds to the encrypted unique encryption key;
return the another encryption key and the unique key ID to the encryption engine; and
validate a received another encryption key with the one-way transformation of the another encryption key by matching the one-way transformation of the another encryption key with the one-way transformation of the received another encryption key.

### Claim 5 (depends on 4)

The information security system of claim 4, wherein the encryption engine is configured to:
return the unique key ID and the another encryption key to the service management system with the unique identifying information and filename of the at least one information asset; and
delete the unique encryption key, the unique key ID the another encryption key and the original at least one information asset.

### Claim 6 (depends on 5)

The information security system of claim 5, wherein the service management system is configured to:
enable the at least one user to create an IP session with the service management system; receive at least one of the retrieve request and a delete request from the at least one user,
wherein the retrieve request comprising a filename of the information asset to be retrieved, wherein the delete request comprising a filename of a pre-stored information to be deleted; and
pass information comprising at least one of the retrieve request, the delete request, the unique identifying information, the filename of the information asset to be retrieved, the filename of the pre-stored information asset to be deleted, the another encryption key that was provided to the at least one user or stored in the service management system when the information asset was originally stored, a key ID that was provided to the at least one user or stored in the service management system when the information asset was originally stored, an IP address, a file type, and a time period to the encryption engine.

### Claim 7 (depends on 6)

The information security system of claim 6, wherein for retrieving the information asset, the encryption engine is further configured to:
request a unique encryption key from the secure third-party storage system using the key ID to reference the unique encryption key and provide the another encryption key to decrypt the unique encryption key, wherein when the another encryption key is verified against the stored one-way transformation of the another encryption key, then the secure third-party storage system knows that the credentials are correct and actions the retrieve request to return the unique encryption key and the key ID;
obtain the encrypted stored information asset from the distribution and delivery device based on the unique encryption key;
decrypt the encrypted stored information asset using the unique encryption key; and
send the decrypted information asset to the distribution and delivery device.

### Claim 8 (depends on 6)

The information security system of claim 6, wherein for deleting the pre-stored information asset, the encryption engine is further configured to:
receive information comprising at least one of the delete request, a filename of the pre-stored information asset, the user identifying information, the another encryption key that was provided to the at least one user or stored in the service management system when the information asset was originally stored, and a key ID that was provided to the at least one user or stored in the service management system when the information asset was originally stored from the service management system; and
send the another encryption key and the key ID to the secure third-party storage system,
wherein when the secure third-party storage system verifies that another encryption key and the key ID are correct, then a key object comprising the pre-stored information asset is deleted to render the pre-stored information asset permanently unreadable;
further wherein the secure third-party storage system notifies the encryption engine about the deletion of the key object comprising the pre-stored information asset; and
wherein the encryption engine at least one of deletes the encrypted pre-stored information asset and directs the distribution and delivery system to delete the encrypted pre-stored information asset.

### Claim 9 (depends on 1)

The information security system of claim 1, wherein the encryption engine is further configured to:
encrypt an information asset with a unique encryption key;
convert the resultant encrypted information asset to a character set that uses visible characters using the Base64 method; and
input the resultant Base64 version of the resultant encrypted information asset comprising an image of resultant encrypted information asset to a steganography algorithm, wherein the steganography algorithm is used to hide the resultant encrypted information asset within an image, further wherein the image used by the steganography algorithm is at least one of supplied by the user, or taken from the user's profile.

### Claim 10

A method of managing a plurality of information assets of at least one user, comprising:
receiving, by a service management system, at least one information asset from the at least one user for storage;
receiving, by an encryption engine, the at least one information asset in its component files and unique identifying information of the at least one user from the service management system;
providing, by a random number source, genuine random numbers to the encryption engine for generating one or more encryption keys;
encrypting, by a distribution and delivery device, the at least one information asset using the one or more encryption keys;
storing, by a distribution and delivery device, the encrypted information asset;
accepting, by a secure third-party storage system, the encrypted information asset for storing securely; and
returning, by the secure third-party storage system, the stored encrypted information asset on demand upon presentation of correct credentials to the distribution and delivery device, wherein the information asset is presented to the at least one user, by the distribution and delivery device, upon receiving a retrieve request.

### Claim 11 (depends on 10)

The method of claim 10 further comprising:
receiving, by the service management system, a network address where the at least one information asset is located from the at least one user; and
retrieving, by the service management system, the at least one information asset from the network address for storage.

### Claim 12 (depends on 11)

The method of claim 11 further comprising:
obtaining, by the encryption engine, a genuine random number from the random number source;
using, by the encryption engine, the genuine random number to create a unique encryption key;
generating, by at least one of the encryption engine and the secure third-party storage system, another encryption key from a pseudo random number function;
encrypting, by the encryption engine, the at least one information asset by using the unique encryption key;
storing, by the encryption engine, the encrypted at least one information asset in the distribution and delivery device;
sending, by the encryption engine, the unique encryption key and the another encryption key to the secure third-party storage system;
encrypting, by the secure third-party storage system, the unique encryption key using the another encryption key to create an encrypted unique encryption key;
storing, by the secure third-party storage system, the resultant encrypted unique encryption key (ems) together with a one-way transformation of the another encryption key;
generating, by the secure third-party storage system, a unique key ID that corresponds to the encrypted unique encryption key; and
returning, by the secure third-party storage system, the another encryption key and the unique key ID to the encryption engine.

### Claim 13 (depends on 12)

The method of claim 12 further comprising:
validating, by the secure third-party storage system, a received another encryption key with the one-way transformation of the another encryption key by matching the one-way transformation of the another encryption key with the one-way transformation of the received another encryption key;
returning, by the encryption engine, the unique key ID and the another encryption key to the service management system with the unique identifying information and filename of the at least one information asset; and
deleting, by the encryption engine, the unique encryption key, the unique key ID, the another encryption key, and the original at least one information asset.

### Claim 14 (depends on 13)

The method of claim 13 further comprising:
enabling, by the service management system, the at least one user to create an IP session with the service management system;
receiving, by the service management system, at least one of the retrieve request and a delete request from the at least one user, wherein the retrieve request comprising a filename of the information asset to be retrieved, wherein the delete request comprising a filename of a pre-stored information to be deleted; and
sending, by the service management system, information comprising at least one of the retrieve request, the delete request, the unique identifying information, the filename of the information asset to be retrieved, the filename of the pre-stored information to be deleted, the another encryption key that was provided to the at least one user or stored in the service management system when the information asset was originally stored, a key ID that was provided to the at least one user or stored in the service management system when the information asset was originally stored, an IP address, a file type, and a time period to the encryption engine.

### Claim 15 (depends on 14)

The method of claim 14 further comprising:
upon receiving the retrieve request from the service management system, requesting, by the encryption engine, a unique encryption key from the secure third-party storage system using the key ID to reference the unique encryption key and provide the another encryption key to decrypt the unique encryption key, wherein when the another encryption key is verified against the stored one-way transformation of the another encryption key, then the secure third-party storage system knows that the credentials are correct and actions the retrieve request to return the unique encryption key and the key ID;
obtaining, by the encryption engine, the encrypted stored information asset from the distribution and delivery device based on the unique encryption key;
decrypting, by the encryption engine, the encrypted stored information asset using the unique encryption key; and
sending, by the encryption engine, the decrypted information asset to the distribution and delivery device.

### Claim 16 (depends on 14)

The method of claim 14 further comprising:
upon receiving the delete request, receiving, by the encryption engine, information from the service management system, wherein the information comprises at least one of the delete request, a filename of the pre-stored information asset, the user identifying information, the another encryption key that was provided to the at least one user or stored in the service management system when the information asset was originally stored, and a key ID that was provided to the at least one user or stored in the service management system when the information asset was originally stored;
sending, by the encryption engine, the another encryption key and the key ID to the secure third-party storage system, wherein when the secure third-party storage system verifies that another encryption key and the key ID are correct, then a key object comprising the pre-stored information asset is deleted to render the pre-stored information asset permanently unreadable; and
notifying, by the secure third-party storage system, the encryption engine about the deletion of the key object comprising the pre-stored information asset, wherein the encryption engine at least one of deletes the encrypted pre-stored information asset and directs the distribution and delivery system to delete the encrypted pre-stored information asset.

### Claim 17

A method of securely storing a plurality of information assets of at least one user, comprising:
receiving, by a service management system, at least one information asset from the at least one user for storage;
receiving, by an encryption engine, the at least one information asset in its component files and unique identifying information of the at least one user from the service management system;
obtaining, by the encryption engine, a genuine random number from a random number source;
using, by the encryption engine, the genuine random number to create a unique encryption key;
generating, by at least one of the encryption engine and a secure third-party storage system, another encryption key from a pseudo random number function;
encrypting, by the encryption engine, the at least one information asset by using the unique encryption key;
storing, by the encryption engine, the encrypted at least one information asset in a distribution and delivery device;
sending, by the encryption engine, at least one of the unique encryption key and the another encryption key to the secure third-party storage system;
encrypting, by the secure third-party storage system, the unique encryption key using the another encryption key;
storing, by the secure third-party storage system, an encrypted unique encryption key together with a one-way transformation of the another encryption key;
generating, by the secure third-party storage system, a unique key ID; and
returning, by the secure third-party storage system, the one-way transformation of the another encryption key and the unique key ID to the encryption engine.

### Claim 18

(canceled)

### Claim 19

An information security system for managing a plurality of information assets of at least one user, comprising:
a service management system; an encryption engine;
a random number source configured to generate one or more genuine random numbers;
a distribution and delivery device; and
a secure third-party storage system;
wherein:
the service management system is configured to receive at least one information asset from at least one user for storage;
the encryption engine is configured to:
receive the at least one information asset in its component files and unique identifying information of the at least one user from the service management system;
obtain a genuine random number from the random number source;
use the genuine random number to create a unique encryption key, wherein at least one of the encryption engine and the secure third-party storage system generates another encryption key from a pseudo random number function;
encrypt the at least one information asset by using the unique encryption key;
store the encrypted at least one information asset in the distribution and delivery device; and
send at least one of the unique encryption key and the another encryption key to the secure third-party storage system; and
the secure third-party storage system is configured to:
encrypt the unique encryption key using the another encryption key to create an encrypted unique encryption key;
store, by the secure third-party storage system, the resultant encrypted unique encryption key together with a one-way transformation of the KEK another encryption key;
generate a unique key ID that corresponds to the encrypted unique encryption key; and
return the one-way transformation of the KEK another encryption key and the unique key ID to the encryption engine.

### Claim 20 (depends on 19)

The information security system of claim 19, wherein the service management system is further configured to:
receive a network address where the at least one information asset is located from the at least one user; and
retrieve the at least one information asset from the network address for storage.

### Claim 21

An information security system for managing information assets of at least one user including:
a service management system;
an encryption engine;
a random number source configured to generate on or more genuine random numbers;
a distribution and delivery device; and
a secure storage system, wherein any one or more of the foregoing is implemented on one or more corresponding devices.

### Claim at position 22

-27. (canceled)
