Systems and methods for breach-proof, resilient, compliant data in a multi-vendor cloud environment and automatically self heals in the event of a ransomware attack

1. A cloud-based system for securely storing data, comprising:

a processor coupled to memory configured to:

obtain original data from a client storage device;

split the original data into at least three data blocks;

encrypt the data blocks using an encryption key associated with the data blocks; and

write the encrypted data blocks across at least three cloud storage providers, each cloud storage provider located in a different physical location, each of the encrypted data blocks written to at least two but less than all of the cloud storage providers, whereby there is no single cloud storage provider to which all of the encrypted data blocks are written; such that if any one cloud storage provider is unavailable, the encrypted data blocks stored thereon may be retrieved from at least one other cloud storage provider; and in the case any one of the cloud storage providers is compromised, the original data cannot be recovered from the encrypted data blocks stored in that cloud storage provider alone;

create a pointer file containing locations of each of the encrypted data blocks in every cloud storage provider in which they were written;

store the pointer file in the client storage device; and

delete the original data from the client storage device;

the processor further configured to thereafter:

detect a condition in one of the clouds that renders it abnormal and unusable;

abandon the abnormal cloud;

establish a new cloud to replace the abnormal cloud;

use the pointer file to:

identify encrypted block fragments that were stored in the abnormal cloud; and

locate at least one normal cloud in which each of the identified encrypted block fragments is stored;

copy the identified encrypted block fragments from the located normal clouds to the established new cloud; and

update the pointer file by replacing information contained therein of encrypted block fragments that were stored in the abnormal cloud, with information of corresponding encrypted block fragments stored in the established new cloud.

2. The system as recited in claim 1 , wherein the processor is further configured to thereafter:

obtain encrypted block storage information from the pointer file;

retrieve the encrypted blocks using the storage information; and

decrypt and reassemble the retrieved encrypted blocks as the original data.

3. A computer implemented method for secure storage of data, comprising causing a processor to complete steps including:

obtaining original data from a client storage device;

splitting the original data into at least three data blocks;

encrypting the data blocks using an encryption key associated with the data blocks;

writing the encrypted data blocks across at least three cloud storage providers, each cloud storage provider located in a different physical location, each of the encrypted data blocks written to at least two but less than all of the cloud storage providers, whereby there is no single cloud storage provider to which all of the encrypted data blocks are written; such that if any one cloud storage provider is unavailable, the encrypted data blocks stored thereon may be retrieved from at least one other cloud storage provider; and in the case any one of the cloud storage providers is compromised, the original data cannot be recovered from the encrypted data blocks stored in that cloud storage provider alone;

creating a pointer file containing locations of the encrypted data blocks in every cloud storage provider to which each of the encrypted data blocks was written;

storing the pointer file in the client storage device;

deleting the original data from the client storage device;

and-thereafter:

detecting a condition in one of the clouds that renders it abnormal and unusable;

abandoning the abnormal cloud;

establishing a new cloud to replace the abnormal cloud;

using the pointer file to:

identify the encrypted block fragments that were stored in the abnormal cloud; and

locate at least one normal cloud in which each of the identified encrypted block fragments is stored;

copying the identified encrypted block fragments from the located normal clouds to the established new cloud; and

updating the pointer file by replacing information contained therein of encrypted block fragments that were stored in the abnormal cloud, with information of corresponding encrypted block fragments stored in the established new cloud.

4. The method as recited in claim 3 , further comprising:

obtaining encrypted block storage information from the pointer file;

retrieving the encrypted blocks using the storage information; and

decrypting and reassembling the retrieved encrypted blocks as the original data.