This content was last updated in May 2022, and represents the status quo as of the time it was written. Google's security policies and systems may change going forward, as we continually improve protection for our customers.
Traditionally, businesses have looked to the public cloud to save costs, experiment with new technology, and provide growth capacity. Increasingly, businesses are also looking to the public cloud for their security, realizing that cloud providers can invest more than the businesses can in technology, people, and processes to deliver a more secure infrastructure.
As a cloud innovator, Google understands security in the cloud. Our cloud services are designed to deliver better security than many on-premises approaches. We make security a priority in our operations—operations that serve billions of users across the world.
Security drives our organizational structure, culture, training priorities, and hiring processes. It shapes the design of our data centers and the technology that they house. It's central to our everyday operations and to disaster planning, including how we address threats. It's prioritized in the way we handle customer data, our account controls, our compliance audits, and our certifications.
This document describes our approach to security, privacy, and compliance for Google Cloud, which is our suite of public cloud products and services. The document focuses on the physical, administrative, and technical controls that we have deployed to help protect your data.
Google's security and privacy-focused culture
Google has created a vibrant and inclusive security culture for all employees. The influence of this culture is apparent during the hiring process, employee onboarding, and ongoing training. It's also apparent in company-wide events that raise awareness of security and privacy.
Our dedicated security team
Our dedicated security team includes some of the world's foremost experts in information security, application security, cryptography, and network security. This team maintains our defense systems, develops security review processes, builds security infrastructure, and implements our security policies. The team actively scans for security threats using commercial and custom tools. The team also conducts penetration tests and performs quality assurance and security reviews.
Members of the security team review security plans for our networks and services, and they provide project-specific consulting services to our product and engineering teams. For example, our cryptography engineers review product launches that include cryptography implementations. The security team monitors for suspicious activity on our networks and addresses information security threats as needed. The team also performs routine security evaluations and audits, which can involve engaging outside experts to conduct regular security assessments.
Collaboration with the security research community
We have long enjoyed a close relationship with the security research community, and we greatly value their help with identifying potential vulnerabilities in Google Cloud and other Google products. Our security teams take part in research and outreach activities to benefit the online community. For example, we run Project Zero, which is a team of security researchers who are dedicated to researching zero-day vulnerabilities. Some examples of this research are the discovery of the Spectre exploit, the Meltdown exploit, the POODLE SSL 3.0 exploit, and cipher suite weaknesses.
Google's security engineers and researchers actively participate and publish in the academic security community and the privacy research community. They also organize and participate in open source projects and academic conferences. Google's security teams have published an in-depth account of our practices and experience in the Building Secure and Reliable Systems book.
Our Vulnerability Reward Program offers rewards in the tens of thousands of dollars for each confirmed vulnerability. The program encourages researchers to report design and implementation issues that might put customer data at risk. In 2021, we awarded researchers over 7 million dollars in prize money. To help improve open-source code, the Vulnerability Reward Program also provides subsidies to open-source projects. For more information about this program, including the rewards that we've given, see Bug Hunters Key Stats.
Our world-class cryptographers participate in industry-leading cryptography projects. For example, we co-designed the COVID-19 Exposure Notification API, which notifies users of positive COVID-19 cases around them, while maintaining strict privacy measures. In addition, to protect TLS connections against quantum computer attacks, we developed the combined elliptic-curve and post-quantum (CECPQ2) algorithm. Our cryptographers developed Tink, which is an open source library of cryptographic APIs. We also use Tink in our internal products and services.
For more information about how you can report security issues, see How Google handles security vulnerabilities.
Internal security and privacy events
All Google employees undergo security and privacy training as part of the orientation process, and they receive ongoing security and privacy training throughout their Google careers. During orientation, new employees agree to our Code of Conduct, which highlights our commitment to keep customer information safe and secure.
Depending on their job role, employees might be required to take additional training on specific aspects of security. For instance, the information security team instructs new engineers on secure coding practices, product design, and automated vulnerability testing tools. Engineers attend regular security briefings and receive security newsletters that cover new threats, attack patterns, mitigation techniques, and more.
Security and privacy are an ever-changing area, and we recognize that dedicated employee engagement is a key means of raising awareness. We host regular internal conferences that are open to all employees to raise awareness and drive innovation in security and data privacy. We host events across global offices to raise awareness of security and privacy in software development, data handling, and policy enforcement.
Our dedicated privacy team
Our dedicated privacy team supports internal privacy initiatives that help improve critical processes, internal tools, products, and privacy infrastructure. The privacy team operates separately from product development and security organizations. It participates in every Google product launch by reviewing design documentation and performing code reviews to ensure that privacy requirements are followed. The team helps release products that incorporate strong privacy standards around the collection of user data.
Our products are designed to provide users and administrators with meaningful privacy configuration options. After products are launched, the privacy team oversees ongoing automated processes to verify that data collected by the products is used appropriately. In addition, the privacy team conducts research on privacy best practices for our emerging technologies. To understand how we stay committed to user data privacy and to compliance with applicable privacy regulations and laws, see Data Protection Law Compliance.
Internal audit and compliance specialists
We have a dedicated internal audit team that reviews our products' compliance with security laws and regulations around the world. As new auditing standards are created and existing standards are updated, the internal audit team determines what controls, processes, and systems are needed in order to help meet them. This team supports independent audits and assessments by third parties. For more information, see Support for compliance requirements later in this document.
Data privacy and sovereignty in Google Cloud
Google Cloud includes security controls that you can use to help protect the privacy and sovereignty of your business data. For example, we provide Access Transparency, Access Approval, Shielded VMs, and Confidential Computing to enable you to do the following:
- Review and approve Google access to your customer data.
- Create and deploy hardened workloads that are designed to comply with global privacy standards.
- Protect data privacy throughout the data lifecycle by using strong encryption.
For more information about data privacy and sovereignty in Google Cloud, see Implement data residency and sovereignty requirements.
Security is an integral part of our cloud operations, not an afterthought. This section describes our vulnerability management programs, malware prevention program, security monitoring, and incident management programs.
Our internal vulnerability management process actively scans for security threats across all technology stacks. This process uses a combination of commercial, open source, and purpose-built in-house tools, and includes the following:
- Quality assurance processes
- Software security reviews
- Intensive automated and manual penetration efforts, including extensive Red Team exercises
- External audits
The vulnerability management organization and its partners are responsible for tracking and following up on vulnerabilities. Because security improves only after issues are fully addressed, automation pipelines continuously reassess the state of a vulnerability, verify patches, and flag incorrect or partial resolution.
To help improve detection capabilities, the vulnerability management organization focuses on high-quality indicators that separate noise from signals that indicate real threats. The organization also fosters interaction with the industry and with the open source community. For example, they run a Patch Reward Program for the Tsunami network security scanner, which rewards developers who create open source detectors for vulnerabilities.
For more about vulnerabilities that we have mitigated, see Google Cloud security bulletins and Compute Engine security bulletins.
Our malware prevention strategy begins by preventing infection using manual and automated scanners to scour our search index for websites that might be vehicles for malware or phishing. Every day we discover thousands of new unsafe sites, many of which are legitimate websites that have been compromised. When we detect unsafe sites, we show warnings in Google Search results and on web pages.
In addition, we use multiple antivirus engines in Gmail, Google Drive, servers, and workstations to help identify malware.
In your Google Cloud environment, you can use Chronicle and VirusTotal to monitor and respond to many types of malware. Google Cloud Threat Intelligence for Chronicle is a team of threat researchers who develop threat intelligence for use with Chronicle. VirusTotal is an online service that analyzes files and URLs to identify viruses, worms, trojans, and other malicious content that's detected by antivirus engines and website scanners.
We also help you detect and mitigate the impact of ransomware, which is a disruptive form of malware that is combined with digital extortion. For more information, see Mitigating ransomware attacks using Google Cloud.
Our security monitoring program is focused on information that's gathered from internal network traffic, from employee actions on systems, and from outside knowledge of vulnerabilities. A core Google principle is to aggregate and store all security telemetry data in one location for unified security analysis.
At many points across our global network, internal traffic is inspected for suspicious behavior, such as the presence of traffic that might indicate botnet connections. We use a combination of open source and commercial tools to capture and parse traffic so that we can perform this analysis. A proprietary correlation system built on top of our technology also supports this analysis. We supplement network analysis by examining system logs to identify unusual behavior, such as attempts to access customer data.
Our security engineers review inbound security reports and monitor public mailing lists, blog posts, and wikis. Automated network analysis and automated analysis of system logs helps determine when an unknown threat might exist; if the automated processes detect an issue, they escalate it to our security staff.
For information about how you can monitor your workloads in Google Cloud, see Cloud Monitoring, Security Command Center, and Monitoring integrity on Shielded VMs.
We have a rigorous incident-management process for security events that might affect the confidentiality, integrity, or availability of systems or data. Our security incident-management program is structured around the NIST guidance on handling incidents (NIST SP 800–61). Key members of our staff are trained in forensics and in handling evidence in preparation for an event, including the use of third-party and proprietary tools.
We test incident response plans for key areas, such as systems that store customer information. These tests consider various scenarios, including insider threats and software vulnerabilities. To help ensure the swift resolution of security incidents, the Google security team is available 24/7 to all employees. If an incident involves your data, Google or its partners will inform you and our support team will investigate. For more information about our data incident response process, see Data incident response process.
Technology with security at its core
Google Cloud runs on a technology platform that is designed and built to operate securely. We are an innovator in hardware, software, network, and system management technologies. We design our servers, our proprietary operating system, and our geographically distributed data centers. Using the principles of defense in depth, we've created an IT infrastructure that is more secure and easier to manage than more traditional technologies.
State-of-the-art data centers
Our focus on security and protection of data is among our primary design criteria. The physical security in Google data centers is a layered security model. Physical security includes safeguards like custom-designed electronic access cards, alarms, vehicle access barriers, perimeter fencing, metal detectors, and biometrics. In addition, to detect and track intruders, we use security measures such as laser beam intrusion detection and 24/7 monitoring by high-resolution interior and exterior cameras. Access logs, activity records, and camera footage are available in case an incident occurs. Experienced security guards, who have undergone rigorous background checks and training, routinely patrol our data centers. As you get closer to the data center floor, security measures also increase. Access to the data center floor is only possible through a security corridor that implements multi-factor access control using security badges and biometrics. Only approved employees with specific roles may enter. Less than one percent of Google employees will ever set foot in one of our data centers.
Powering our data centers
To keep things running 24/7 and provide uninterrupted services, our data centers have redundant power systems and environmental controls. Every critical component has a primary and alternate power source, each with equal power. Backup generators can provide enough emergency electrical power to run each data center at full capacity. Cooling systems maintain a constant operating temperature for servers and other hardware, which reduces the risk of service outages while minimizing environmental impact. Fire detection and suppression equipment help prevent damage to hardware. Heat detectors, fire detectors, and smoke detectors trigger audible and visible alarms at security operations consoles and at remote monitoring desks.
We are the first major internet services company to get external certification of our high environmental, workplace safety, and energy management standards throughout our data centers. For example, to demonstrate our commitment to energy management practices, we obtained voluntary ISO 50001 certifications for our data centers in Europe. For more information about how we reduce our environmental impact in Google Cloud, see Sustainability.
Custom server hardware and software
Our data centers have purpose-built servers and network equipment, some of which we design ourselves. While our servers are customized to maximize performance, cooling, and power efficiency, they are also designed to help protect against physical intrusion attacks. Unlike most commercially available hardware, our servers don't include unnecessary components such as video cards, chipsets, or peripheral connectors, all of which can introduce vulnerabilities. We vet component vendors and choose components with care, working with vendors to audit and validate the security properties that are provided by the components. We design custom chips, such as Titan, that help us securely identify and authenticate legitimate Google devices at the hardware level, including the code that these devices use to boot up.
Server resources are dynamically allocated. This gives us flexibility for growth and lets us adapt quickly and efficiently to customer demand by adding or reallocating resources. This homogeneous environment is maintained by proprietary software that continually monitors systems for binary-level modifications. Our automated, self-healing mechanisms are designed to enable us to monitor and remediate destabilizing events, receive notifications about incidents, and slow down potential compromises on the network.
Hardware tracking and disposal
We meticulously track the location and status of all equipment within our data centers using barcodes and asset tags. We deploy metal detectors and video surveillance to help make sure that no equipment leaves the data center floor without authorization. If a component fails to pass a performance test at any point during its lifecycle, it's removed from inventory and retired.
Our storage devices, including hard drives, solid-state drives, and non-volatile dual in-line memory modules (DIMM), use technologies like full disk encryption (FDE) and drive locking to protect data at rest. When a storage device is retired, authorized individuals verify that the disk is erased by writing zeros to the drive. They also perform a multiple-step verification process to ensure the drive contains no data. If a drive cannot be erased for any reason, it's physically destroyed. Physical destruction is done by using a shredder that breaks the drive into small pieces, which are then recycled at a secure facility. Each data center adheres to a strict disposal policy and any variances are immediately addressed. For more information, see Data deletion on Google Cloud.
Software development practices
We proactively seek to limit the opportunities for vulnerabilities to be introduced by using source control protections and two-party reviews. We also provide libraries that prevent developers from introducing certain classes of security bugs. For example, we have libraries and frameworks that are designed to eliminate XSS vulnerabilities in web apps. We also have automated tools for automatically detecting security bugs; these tools include fuzzers, static analysis tools, and web security scanners.
For more information, see Safe software development.
Key security controls
Google Cloud services are designed to deliver better security than many on-premises solutions. This section describes the main security controls that we use to help protect your data.
Encryption adds a layer of defense for protecting data. Encryption ensures that if an attacker gets access to your data, the attacker cannot read the data without also having access to the encryption keys. Even if an attacker gets access to your data (for example, by accessing the wire connection between data centers or by stealing a storage device), they won't be able to understand or decrypt it.
Encryption provides an important mechanism in how we help protect the privacy of your data. It allows systems to manipulate data—for example, for backup—and engineers to support our infrastructure, without providing access to content for those systems or employees.
Securing data at rest
By default, Google Cloud uses several layers of encryption to protect user data that's stored in Google production data centers. This default encryption occurs at the application or storage infrastructure layer.
For more information about encryption at rest, including encryption key management and Keystore, see Encryption at rest in Google Cloud.
In addition to default encryption, you can manage your own encryption keys for your workloads using Cloud Key Management Service (Cloud KMS). You can add customer-managed encryption keys (CMEK) and use Cloud HSM, our hardware security module service, to protect your keys.
Securing data in transit
Data can be vulnerable to unauthorized access as it travels across the internet or within networks. Traffic between your devices and the Google Front End (GFE) is encrypted using strong encryption protocols such as TLS.
You can take advantage of this encryption for your services by using Cloud Load Balancing. Google Cloud also offers you additional transport encryption options, including Cloud VPN for establishing virtual private networks using IPsec.
For more information, see Encryption in Transit in Google Cloud.
Supply chain integrity
Supply chain integrity ensures that the underlying code and binaries for the services that process your data are verified and that they pass attestation tests. In Google Cloud, we developed Binary Authorization for Borg (BAB) to review and authorize all production software that we deploy. BAB helps ensure that only authorized code can process your data. In addition to BAB, we use hardware security chips (called Titan) that we deploy on servers, devices, and peripherals. These chips offer core security features such as secure key storage, root of trust, and signing authority.
To help secure your software supply chain, you can implement Binary Authorization to enforce your policies before deploying your code. For information about securing your supply chain, see SLSA.
Securing data in use
Google Cloud products support data encryption for data in use with Confidential Computing. Confidential Computing protects your data in use by performing computation in cryptographic isolation and maintains confidentiality for workloads in a multi-tenant cloud environment. This type of cryptographically isolated environment helps prevent unauthorized access or modifications to applications and data while the applications or data are in use. A trusted execution environment also increases the security assurances for organizations that manage sensitive and regulated data.
In Google Cloud, you can enable Confidential Computing to protect your VM instances using Confidential VM, use Confidential Google Kubernetes Engine Nodes for your GKE nodes, or use Dataproc Confidential Compute to run Hadoop, Spark, or MapReduce for sensitive analytics jobs.
Security benefits of our global network
In other cloud services and on-premises solutions, customer data travels between devices across the public internet in paths known as hops. The number of hops depends on the optimal route between the customer's ISP and the data center. Each additional hop introduces a new opportunity for data to be attacked or intercepted. Because our global network is linked to most ISPs in the world, our network limits hops across the public internet, and therefore helps limit access to that data by bad actors.
Our network uses multiple layers of defense—defense in depth—to help protect the network against external attacks. Only authorized services and protocols that meet our security requirements are allowed to traverse it; anything else is automatically dropped. To enforce network segregation, we use firewalls and access control lists. All traffic is routed through GFE servers to help detect and stop malicious requests and distributed denial-of-service (DDoS) attacks. Logs are routinely examined to reveal any exploitation of programming errors. Access to networked devices is restricted to only authorized employees.
Our global infrastructure allows us to run Project Shield, which provides free, unlimited protection to websites that are vulnerable to DDoS attacks that are used to censor information. Project Shield is available for news websites, human rights websites, and election-monitoring websites.
Low latency and highly available solutions
Our IP data network consists of our own fiber, of publicly available fiber, and of undersea cables. This network allows us to deliver highly available and low-latency services across the globe.
We design the components of our platform to be highly redundant. This redundancy applies to our server design, to how we store data, to network and internet connectivity, and to the software services themselves. This "redundancy of everything" includes exception handling and creates a solution that is not dependent on a single server, data center, or network connection.
Our data centers are geographically distributed to minimize the effects of regional disruptions on global products, such as when natural disasters or local outages occur. If hardware, software, or a network fails, platform services and control planes are automatically and swiftly shifted from one facility to another so that platform services can continue without interruption.
Our highly redundant infrastructure also helps you protect your business from data loss. You can create and deploy Google Cloud resources across multiple regions and zones to build resilient and highly available systems. Our systems are designed to minimize downtime or maintenance windows for when we need to service or upgrade our platform. For more information about how Google Cloud builds resilience and availability into its core infrastructure and services, from design through operations, see Infrastructure design for availability and resilience.
Google Cloud service availability
Some of our Google Cloud services might not be available across all geographies. Some service disruptions are temporary (due to an unanticipated event, such as a network outage), but other service limitations are permanent due to government-imposed restrictions. Our comprehensive Transparency Report and status dashboard show recent and ongoing disruptions of traffic to Google Cloud services. We provide this data to help you analyze and understand the availability of online information.
Data access and restrictions
This section describes how we restrict access to data and how we respond to data requests from law enforcement agencies.
The data that you put into our systems is yours. We do not scan it for advertisements and we do not sell it to third parties. The Cloud Data Processing Addendum for Google Cloud describes our commitment to protecting your data. That document states that we will not process data for any purpose other than to meet our contractual obligations. If you choose to stop using our services, we provide tools that make it easy for you to take your data with you, without penalty or additional cost. For more information about our commitments for Google Cloud, see our trust principles.
Administrative access for Google employees
Our infrastructure is designed to logically isolate each customer's data from the data of other customers and users, even when it's stored on the same physical server. Only a small group of our employees have access to customer data. For our employees, access rights and levels are based on their job function and role, using the concepts of least privilege and need-to-know that match access privileges to defined responsibilities. Our employees are granted only a limited set of default permissions to access company resources, such as employee email and Google's internal employee portal. Requests for additional access must follow a formal process that involves a request and an approval from the data or system owner, manager, or other executives, as dictated by our security policies.
Approvals are managed by workflow tools that maintain audit records of all changes. These tools control both the modification of authorization settings and the approval process to help ensure that approval policies are consistently applied. An employee's authorization settings are used to control access to all resources, including data and systems for Google Cloud products. Support services are provided only to authorized customer administrators. Our dedicated security teams, privacy teams, and internal audit teams monitor and audit employee access, and we provide audit logs to you through Access Transparency for Google Cloud. Also, when you enable Access Approval, our support personnel and our engineers require your explicit approval to access your data.
Customer administrator access
Your project owner configures and controls your organization's administrative roles and privileges for Google Cloud. You can use Identity and Access Management (IAM) to manage your team members' access to certain services and their ability to perform specific administrative functions, without needing to grant access to all settings and data.
Law enforcement data requests
As the data owner, you are primarily responsible for responding to law enforcement data requests. However, like many technology companies, we receive direct requests from governments and courts to disclose customer information. Google has operational policies and procedures and other organizational measures in place to help protect against unlawful or excessive requests for user data by public authorities. When we receive such a request, our team reviews the request to make sure that it satisfies legal requirements and Google's policies. Generally speaking, for us to comply, the request must be made in writing, issued under an appropriate law, and signed by an authorized official of the requesting agency.
We believe that the public deserves to know the full extent to which governments request information from us. We became the first company to start regularly publishing reports about government data requests. Detailed information about data requests and our response to them is available in our Transparency Report. It's our policy to notify you about requests for your data unless we are specifically prohibited by law or court order from doing so. For more information, see Government Requests for Cloud Customer Data.
For most data-processing activities, we provide our services in our own infrastructure. However, we might engage some third-party suppliers to provide services related to Google Cloud, including customer support and technical support. Before onboarding a supplier, we assess their security and privacy practices. This assessment checks whether the supplier provides a level of security and privacy that is appropriate for their access to data and for the scope of the services that they are engaged to provide. After we have assessed the risks that are presented by the third-party supplier, the supplier is required to enter into appropriate security, confidentiality, and privacy contract terms.
For more information, see the Supplier Code of Conduct.
Support for compliance requirements
Google Cloud regularly undergoes independent verification of its security, privacy, and compliance controls, and receives certifications, attestations, and audit reports to demonstrate compliance. Our information security includes specific customer data privacy-related controls that help keep customer data secure.
Some key international standards that we are audited against are the following:
- ISO/IEC 27001 (Information Security Management)
- ISO/IEC 27017 (Cloud Security)
- ISO/IEC 27018 (Cloud Privacy)
- ISO/IEC 27701 (Privacy)
In addition, our SOC 2 and SOC 3 reports are available to our customers.
We also participate in sector and country-specific frameworks, such as FedRAMP (US government), BSI C5 (Germany), and MTCS (Singapore). We provide resource documents and mappings for certain frameworks where formal certifications or attestations might not be required or applied.
If you operate in regulated industries, such as finance, government, healthcare, or education, Google Cloud provides products and services that help you be compliant with numerous industry-specific requirements. For example, if you must comply with Payment Card Industry Data Security Standard (PCI DSS), see PCI Data Security Standard compliance for information about how you can implement its requirements in Google Cloud.
For a complete listing of our compliance offerings, see the Compliance resource center.
Risk management and insurance
We maintain a robust insurance program for many risk types, including cyber and privacy liability insurance coverage. These policies include coverage for Google Cloud in events such as unauthorized use or access of our network; regulatory action where insurable; failure to adequately protect confidential information; notification costs; and crisis management costs, including forensic investigation.
We also use our position as a leader in the cyber space to help our customers access cyber insurance solutions. With the Risk Protection Program, Google Cloud announced a first-of-its-kind collaboration between a major cloud provider and two leading cyber insurance companies: Munich Re and Allianz Global & Corporate Speciality. The Risk Protection Program provides data-driven insights and lets customers who are seeking cyber insurance coverage share their cloud security posture directly with our insurance partners. This feature helps customers get favorable insurance terms with broader coverage for Google Cloud workloads.
With the creation of the Risk Protection Program, we have linked cyber insurance directly to cloud security, using Center for Internet Security (CIS) benchmarks. The program was designed to use our position as a cloud provider and a security leader to help improve our customers' security. It helps save our customers significant time and effort through streamlined insurance purchasing, and provides access to specialized insurance coverage for Google Cloud customers.
Google Cloud security products and services
On Google Cloud, security is a continuum of shared responsibilities for both you and us. Generally, you are responsible for securing what you bring to the cloud, whereas we are responsible for protecting the cloud itself. Therefore, while you're always responsible for securing your data, we are responsible for securing the underlying infrastructure. The following image visualizes this relationship as the shared responsibility model, which describes the responsibilities that we and you have in Google Cloud.
In the infrastructure as a service (IaaS) layer, only the hardware, storage, and network are our responsibility. In the software as a service (SaaS) layer, the security of everything except the data and its access and usage are our responsibility.
Google Cloud offers a range of security services that you can take advantage of to secure your cloud environment at scale. For more information, see Security and Identity Products in Google Cloud. You can also find more information in our security best practices center.
The protection of your data is a primary design consideration for all our infrastructure, products, and operations. Our scale of operations and our collaboration with the security research community enable us to address vulnerabilities quickly, and often to prevent them entirely. We run our own services, such as Search, YouTube, and Gmail, on the same infrastructure that we make available to our customers, who benefit directly from our security controls and practices.
We believe that we can offer a level of protection that few public cloud providers or private enterprise IT teams can match. Because protecting data is core to our business, we can make extensive investments in security, resources, and expertise at a scale that others cannot. Our investment frees you to focus on your business and innovation. Our strong contractual commitments help you maintain control over your data and how it's processed. We do not use your data for advertising or any purpose other than to deliver Google Cloud services.
For these reasons and more, many innovative organizations trust us with their most valuable asset: their information. We will continue to invest in our platform to let you benefit from our services in a secure and transparent manner.
- To learn more about our security culture and philosophy, read Building Secure and Reliable Systems (O'Reilly book).
- For information about our novel approach to cloud-native security, read BeyondProd, which describes how to protect code change and access to user data in microservices.
- To adopt similar security principles for your own workloads, deploy the security foundations blueprint or other blueprints that are available from the security best practices center.
- To learn more about Google Workspace security, see Google Workspace security.