When your users transfer files to your file transfer server. Those files are usually stored in plain text. The risk is that if an attacker somehow obtains unauthorized access to that server, he could simply take those files and then view their content. If any of those files contain personal data or other confidential information, that information may be compromised and could end up with a data breach in your hands.
One way to prevent that from happening is by using data encryption at rest on the J scape MFT server. Data encryption at rest is provided through integrations with open PGP; you can configure MFT servers. For uploaded files to be automatically encrypted with PGP open as. There are several ways to use PGP open on the J scape MFD server.
Data encryption at rest, both the way Google encrypts data by default and the options we provide to encrypt data as a GCP developer. Google utilizes a few layers of encryption to protect data. First, in the hardware device layer, we encrypt hard drives and solid state drives with a device level key. Then, we encrypt the data in the storage system layer.
Let’s dive a little deeper into that. To understand how Google storage layer encryption works, you must understand how Google stores your data. For example, when you upload a cat video to Google, it is divided into sub file fragments for storage and distributed through Google storage systems. Each piece of data is encrypted with an individual encryption key so that there are not two pieces of data that have the same encryption key, even if they are part of the same Google Cloud Storage object, owned by the same client or stored on the same machine.
This gives us a very low level cryptographic data isolation. Access control lists ensure that each fragment can be decrypted only by authorized Google services, using data encryption keys. These keys encrypt data fragments and are stored with the data fragments themselves. And, we never store unencrypted keys on disk. In fact, data encryption keys are encrypted with another storage key, called key encryption key.
This is commonly known as envelope encryption because one key is wrapping another. Key encryption keys are stored centrally in Google’s internal key management service. The use of a central key management service makes the storage and encryption of data at Google scale manageable and allows us to track and control access to data from a central point.
The data stored in Google Cloud is encrypted at the storage level, using AES-256 or AES-128. As a customer, you can use our default Google encryption simply using Google Cloud. We already encrypt your data stored at rest by default, using one or more encryption mechanisms.