This document in the Google Cloud Architecture Framework provides best practices for implementing privacy requirements.
Privacy regulations help define how you can obtain, process, store, and manage your users' data. Many privacy controls (for example, controls for cookies, session management, and obtaining user permission) are your responsibility because you own your data (including the data that you receive from your users).
Google Cloud includes the following controls that promote privacy:
- Default encryption of all data when it's at rest, when it's in transit, and while it's being processed.
- Safeguards against insider access.
- Support for numerous privacy regulations.
For more information, see Google Cloud Privacy Commitments.
Classify your confidential data
You must define what data is confidential and then ensure that the confidential data is properly protected. Confidential data can include credit card numbers, addresses, phone numbers, and other personal identifiable information (PII).
Lock down access to sensitive data
Place sensitive data in its own service perimeter using VPC Service Controls, and set Google Identity and Access Management (IAM) access controls for that data. Configure multi-factor authentication (MFA) for all users who require access to sensitive data.
Monitor for phishing attacks
Ensure that your email system is configured to protect against phishing attacks, which are often used for fraud and malware attacks.
If your organization uses Gmail, you can use advanced phishing and malware protection. This collection of settings provides controls to quarantine emails, defends against anomalous attachment types, and helps protect against from inbound spoofing emails. Security Sandbox detects malware in attachments. Gmail is continually and automatically updated with the latest security improvements and protections to help keep your organization's email safe.
Extend zero trust security to your hybrid workforce
A zero trust security model means that no one is trusted implicitly, whether they are inside or outside of your organization's network. When your IAM systems verify access requests, a zero trust security posture means that the user's identity and context (for example, their IP address or location) are considered. Unlike a VPN, zero trust security shifts access controls from the network perimeter to users and their devices. Zero trust security allows users to work more securely from any location. For example, users can access your organization's resources from their laptops or mobile devices while at home.
On Google Cloud, you can configure BeyondCorp Enterprise and Identity-Aware Proxy (IAP) to enable zero trust for your Google Cloud resources. If your users use Google Chrome and you enable BeyondCorp Enterprise, you can integrate zero-trust security into your users browsers.
Learn more about security and privacy with the following resources:
- Implement logging and detective controls (next document in this series)
- Privacy Center