Data in transit
Coarse-grained encryption of data in transit is necessary when one side of the communication channel is not able to encrypt the individual elements of the request or response. For example, user interfaces are not able to encrypt data elements because they cannot secure the private key. Therefore, clients will send the data as-is through an encrypted channel, such as HTTPS, and the server-side will decrypt the data for the client before sending it on the encrypted channel.
Fortunately, value-added cloud services make it very easy for cloud-native systems to enforce the encryption of data in transit. For example, API gateways, function-as-a-service, event streams, and cloud-native databases typically only support HTTPS, therefore ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access