One Touch Configuration is a feature that persists the Cloud Xtender configuration on a commercial cloud service. The benefits of this are
a) Complex cloud connections and placement rules are not lost in the event of an OS re-installation.
b) Replicating the configuration on more than one machine is possible.
How is this information protected?
All sensitive information retained locally, such as storage keys and secrets etc are encrypted using AES 256, using an internally derived password. When using this feature, any changes made to the configuration are further encrypted using AES 256 and a user defined password, however we use an entirely different encryption engine to perform this phase of the encryption. The final blob is stored against the users hashed (salted) email address, the email address must be verified before this feature can be enabled.
Is it possible the my information could be compromised?
Well anything is possible, and while we have gone to great lengths to ensure data integrity and security, we can not guarentee this. If you wish to use this feature, you do so knowing the (very limited) risks.
Can I store this configuration information on my own cloud service?
This is a feature we will be adding in feature releases.
Article is closed for comments.