How sensitive data must be protected

This documentation typically states for such data as passwords and secret keys to be stored in the encrypted form. There are folowing ways to protect senstive data.

• Protect password as encrypted UTF16 string with the server (global) key, see Tasks::ProtectPassword and DataProtectionApi::ProtectUtf16StringGlobally
• Protect password as encrypted UTF16 string with the host key, see DataProtectionApi::ProtectUtf16StringForHost
• Protect password as encrypted UTF8 string with the server (global) key, see DataProtectionApi::ProtectUtf8StringGlobally
• Protect password as encrypted UTF8 string with the host key, DataProtectionApi::ProtectUtf8StringForHost
• Protect binary data with server (global) key, see DataProtectionApi::ProtectDataGlobally
• Protect binary data the key of the specified host, see DataProtectionApi::ProtectDataForHost

One should select correct way to protect data as specified in the documentation for each particular case.

See also:

• DatabaseInfo::CheckBackupCloudPath
• DatabaseInfo::CheckBackupCloudPath2
• Section KLSRV_MASTER_SRV attributes
• PackagesApi::CreateExecutablePkgAsync
• List of deployment task attributes
• Authentication settings of the cloud