Abstract: In an embodiment, persistent storage contains one or more cryptographic keys. One or more processors may be configured to perform operations comprising: receiving a request for an encrypted record stored within a computational instance, wherein the request includes a plaintext value related to the encrypted record; obtaining a hash value by applying a hash function to the plaintext value; transmitting, to the computational instance, the hash value; receiving, from the computational instance, the encrypted record, wherein the encrypted record includes one or more encrypted values; obtaining an unencrypted version of the encrypted record by applying a cryptographic function to the encrypted record, wherein applying the cryptographic function includes use of a cryptographic key of the one or more cryptographic keys; and transmitting at least part of the unencrypted version of the encrypted record.

Abstract: Embodiments are disclosed herein that provide users of a cloud computing system with the ability to determine, display, prioritize, and/or handle error messages, e.g., using a system-wide standardized naming format. In some embodiments, the appropriate system-wide standardized error messages may be determined, even in situations where at least some of the data underlying the error is encrypted and remains unknown to the hosted cloud computing system. The system-wide standardized error messages may include, e.g., an indication of a company's name, an application name, as well as a unique error code. The standardized error message may also include information as to how the error may potentially be remediated. Using these embodiments, users may be able to more quickly understand which errors to address first and what possible solutions may be employed in order to resolve those errors—while remaining confident that any encrypted information has remained uncompromised.

Abstract: Embodiments are disclosed herein that provide users of a cloud computing system with the ability to determine, display, prioritize, and/or handle error messages, e.g., using a system-wide standardized naming format. In some embodiments, the appropriate system-wide standardized error messages may be determined, even in situations where at least some of the data underlying the error is encrypted and remains unknown to the hosted cloud computing system. The system-wide standardized error messages may include, e.g., an indication of a company's name, an application name, as well as a unique error code. The standardized error message may also include information as to how the error may potentially be remediated. Using these embodiments, users may be able to more quickly understand which errors to address first and what possible solutions may be employed in order to resolve those errors—while remaining confident that any encrypted information has remained uncompromised.