As described, sharding is a database technology that separates a database into chunks placed in different nodes to ‘speed up’ the access of data queries in a database. If you break into one node or container you can rebuild the entire dataset. Sharding is not a data security technology, sharding does not break data apart at the binary file level and sharding does not protect data.

To contrast, Secured2 is a multi step security algorithm that protects data, randomizes data, and then breaks up the data at a binary level into small segments. Then each segment is randomly distributed into multiple physically separated storage locations of a customer’s choosing (think of turning remote storage like the cloud into RAID drives on a computer with the benefit of built in redundancy of the cloud itself). With Secured2 you cannot rebuild a database with one segment of data. With Secured2, if a bad actor breaks into a container, they cannot rebuild the dataset because they get no valuable data. They just get a bunch of scrambled and unusable ciphertext. They would need to break into all the physically separated containers where the data was randomly segmented, they would need to break the encryption of each segment, they would need to reassemble the data in the precise order it was shred, they would need to unmask the data, decompress, and as well verify identity to reverse the process. It’s impossible.