The most common standard for encryption today is AES-256 (256-bit Advanced Encryption Standard), a highly secure standard chosen by the National Institute of Standards. ProtectedCloud Security utilizes AES-256 and adds a second XTS Encryption Key for data that is in-flight or while stored at the Cloud.
The first Key, the “Encryption Key”, is created by the storage administrator before any data is written to a new Cloud Storage bucket, and it cannot be changed. Coronado V-NAS Global Access Points and the Coronado V-NAS Global View Manager store this key locally and only use this key for encryption of a specific storage bucket. The key is never copied to any other location especially the Cloud Storage Provider. Data is encrypted in-line at the Coronado V-NAS Global Access Point as it is written, thus protecting data both in transit and in Cloud Storage.
BridgeSTOR’s CSFS creates a second key, the “XTS Encryption Key”. This key is never stored and is calculated on demand when encryption is turned on and new data is written. The formula for calculating the “XTS Encryption Key” is BridgeSTOR proprietary and will never be released.
Why XTS Encryption? Without this extra added ProtectedCloud Security it’s possible for a hacker to attack your organization’s encrypted data by observing the contents of two identical blocks of data, such as two zeroed blocks. The hacker can use that information to reverse engineer the data and determine your key. With ProtectedCloud Security using XTS, two blocks of the same data will look different. The hacker in this case would not be able to determine the key, and your data remains safe.
Since the “Encryption Key” must be maintained locally, BridgeSTOR’s near-term roadmap for CSFS includes the ability to be integrated into enterprise Key Management systems.