7 results · ● Live web index
docs.cloud.google.com article

Encryption in transit for Google Cloud  |  Security  |  Google Cloud Documentation

https://docs.cloud.google.com/docs/security/encryption-in-transit

Encryption in transit helps protect your data if communications are intercepted while data moves between the end user and Google Cloud or between two services. Encryption in transit authenticates the endpoints and encrypts the data before transmission. On arrival, the receiver decrypts the data and verifies that it was not modified during transit. [...] Record protocol: Service-to-service data is encrypted in transit using the shared traffic key. By default, ALTS uses AES-128-GCM encryption for all traffic. Data in transit within Google's lowest-level storage system uses AES-256 encryption, and ALTS provides AES message authentication. Encryption in ALTS is provided by BoringSSL or PSP. This encryption is validated at FIPS 140-2 level 1 or FIPS 140-3 level 1. [...] When a user sends a request to a Google Cloud service, we secure the data in transit (providing authentication, integrity, and encryption) using HTTPS with a certificate from a web (public) certificate authority. Any data the user sends to the GFE is encrypted in transit with TLS or QUIC. GFE negotiates a particular encryption protocol with the client depending on what the client can support. GFE negotiates more modern encryption protocols when possible.

Visit
cloud.google.com article

Encryption For Cloud Security | Google Cloud

https://cloud.google.com/security/encryption

Learn more Video: Google Cloud encryption at rest ### Encryption in transit Encryption in transit protects your data if communications are intercepted while data moves between your site and the cloud provider or between two services. This protection is achieved by encrypting the data before transmission, authenticating the endpoints, and decrypting and verifying the data on arrival. Learn more Video: Google Cloud encryption in transit ### Encryption in use [...] # Data encryption Google Cloud encrypts data in transit between our facilities and at rest, which ensures the data can be accessed only by the authorized roles and services with audited access to the encryption keys. Get started for free ### Encryption at rest Cloud Storage always encrypts your data on the server side, before it is written to disk, at no additional charge. Besides this standard, Google-managed behavior, there are additional ways to encrypt your data when using Cloud Storage. [...] Google Cloud encrypts all customer content stored at rest and in transit between our facilities, without any action required from the customer, using one or more encryption mechanisms. Learn more ### Hardware-backed encryption keys

Visit
censinet.com article

Encryption at Rest vs. Encryption in Transit: Differences | Censinet

https://censinet.com/perspectives/encryption-at-rest-vs-encryption-in-transit…

Google Cloud provides a clear explanation: "Encryption in transit authenticates the endpoints and encrypts the data before transmission. On arrival, the receiver decrypts the data and verifies that it was not modified during transit." ( [...] Encryption at rest and encryption in transit address different aspects of data security. Encryption at rest focuses on protecting static data stored on physical media like hard drives, databases, or cloud storage. On the other hand, encryption in transit secures data as it moves between locations, such as during email exchanges, web traffic, or file transfers. [...] ### Implementation Guidelines Healthcare organizations should prioritize encryption by default, starting with cloud storage systems. Configuring these systems to automatically encrypt new volumes using AES-256 with customer-managed keys (CMKs) helps maintain a secure baseline. For data in transit, enforcing bucket policies that deny access over HTTP and blocking insecure protocols at the network level ensures secure communication.

Visit
ncsc.gov.uk official

Principle 1: Data in transit protection | National Cyber Security Centre

https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/princi…

Your cloud provider should be responsible for the encryption and key management used to protect data in transit. For example, terminating the TLS connection and managing the certificates (and the corresponding private keys) used to authenticate the service. We discuss why a cloud provider can be trusted to take responsibility for key management in our cloud key management services guidance. [...] Encryption is usually implemented to provide additional confidentiality and integrity of data over and above that provided by network layer protections. All approaches should include encryption between endpoints and components of the cloud service. If relying on a protocol that uses TLS, such as HTTPS, ensure that it is configured according to our TLS guidance. [...] Data flows between physical data centres or availability zones usually rely on network connectivity that does not fall within the scope of the cloud provider’s usual physical security measures (such as those described in Principle 2.2: data centre security). You will need to ensure that the cloud provider encrypts all data that is transiting between data centres as described above. This includes data flows initiated by your application and those initiated by the underlying cloud platform,

Visit
jumpcloud.com article

What Is Data in Transit Encryption?

https://jumpcloud.com/it-index/what-is-data-in-transit-encryption

Data in transit encryption protects data as it moves between devices, servers, or networks, preventing unauthorized access.

Visit
imperva.com article

What is Data in Transit | The Key to Safe Data Exchange | Imperva

https://www.imperva.com/learn/data-security/data-in-transit

## Encrypting Data in Transit There are several methods for encrypting data in transit, which can help to protect sensitive information and prevent unauthorized access or tampering. By implementing the appropriate encryption method, organizations can better secure their data in transit and reduce the risks of data breaches and other security incidents. The primary methods include: [...] Encrypted data in transit, on the other hand, is data that has been protected using encryption algorithms. This means that only those who have the decryption key can view or access the data. Encrypted data in transit is much more secure than unencrypted data, as it makes it much more difficult for attackers to intercept and manipulate the data. [...] Implement encryption algorithms—encrypting data in transit helps to prevent unauthorized access, as only those with the proper decryption keys can view the data. Use secure communication protocols—communication protocols such as HTTPS and SSH help to secure data in transit by encrypting the data and verifying the identity of the parties involved in the transmission.

Visit
learn.microsoft.com article

Encryption for data-in-transit - Microsoft Service Assurance | Microsoft Learn

https://learn.microsoft.com/en-us/compliance/assurance/assurance-encryption-i…

In addition to protecting customer data at rest, Microsoft uses encryption technologies to protect customer data in transit. Data is in transit: When a client machine communicates with a Microsoft server When a Microsoft server communicates with another Microsoft server When a Microsoft server communicates with a non-Microsoft server (for example, Exchange Online delivering email to a third-party email server) [...] Inter-datacenter communications between Microsoft servers take place over TLS or IPsec, and all customer-facing servers negotiate a secure session using TLS with client machines. For example, Exchange uses TLS 1.2 with 256-bit cipher strength (FIPS 140-2 Level 2-validated). See Technical reference details about encryption for a list of TLS cipher suites supported by Microsoft 365. This information applies to the protocols that clients such as Outlook, Microsoft Teams, and Outlook on the web use [...] Microsoft IT SSL issues the public certificates by using SSLAdmin, an internal Microsoft tool that protects the confidentiality of transmitted information. All certificates issued by Microsoft IT have a minimum length of 2,048 bits. Webtrust compliance requires SSLAdmin to make sure that certificates are issued only to public IP addresses owned by Microsoft. Any IP addresses that don't meet this criterion go through an exception process.

Visit