Google Cloud 系統的設計重點是透過控管和監控機制保護您的內容。您儲存在 Google Cloud上的內容完全屬於您。Google 人員有時可能需要存取您的內容，但這些存取行為必須有正當的商業理由。
Google 人員要求存取客戶資料的原因
Google 人員要求存取客戶資料最常見的原因，是為瞭解決客戶支援單。如果您建立客戶支援要求，Google 人員可能會要求存取您的資料。資料存取透明化控管機制可讓客戶瞭解這些存取權。無論機構是否已啟用資料存取透明化控管機制，Google 都提供各種控制項，以支援資料隱私權。如要進一步瞭解這些控制項，請參閱 Google 基礎架構安全性設計總覽。
什麼是特殊存取權
Google 人員為了履行提供合約服務的義務，而存取您的資料，稱為特權存取權。系統通常會因為下列原因在 Google Cloud 中存取您的資料：
您正在存取自己的資料。
您使用的服務代表您存取資料。
當 Google 人員以特權管理員身分提供合約服務時，他們可以存取您的資料。
特殊權限存取權管理的基本原則
Google Cloud的特殊權限存取管理策略會嚴格限制單一 Google 員工可查看的資料，以及可對資料採取的動作。 Google Cloud的特殊權限存取管理理念建立在下列原則之上：
最小權限：根據預設，所有 Google 人員都無法存取客戶資料。授予存取權的時間應為暫時性，且不得超過提供合約服務所需的時間。
限制單一資料存取權：任何 Google 人員都很難單獨存取客戶資料，不涉及其他人員。
所有存取權都必須有正當理由：根據預設，Google 人員無法存取客戶資料。Google 人員只能在有有效的業務正當理由下，存取您的資料。Google 人員無法存取客戶資料，以便取得不公開的理由，或是 Google 人員並非直接連結的協作者。如需有效業務理由的清單，請參閱「理由代碼」。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eGoogle personnel may require temporary access to customer content, but only with a valid business justification, such as resolving a customer support ticket.\u003c/p\u003e\n"],["\u003cp\u003ePrivileged access refers to Google personnel accessing customer data to fulfill a contracted service, which is strictly limited and managed.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud's privileged access management is based on principles such as least privilege, limiting singular access, requiring justification for all access, and employing monitoring and alerting.\u003c/p\u003e\n"],["\u003cp\u003eAccess to customer data is denied by default for Google personnel, and any granted access is temporary and no greater than what is absolutely necessary.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud undergoes third-party audits to ensure data protection practices align with their controls and commitments.\u003c/p\u003e\n"]]],[],null,["# Privileged access at Google Cloud\n=================================\n\nGoogle Cloud systems are built with a focus on protecting your content\nusing controls and monitoring. Your content stored on Google Cloud\ncompletely belongs to you. Occasionally, Google personnel might need to access\nyour content but these accesses are never without a valid business\njustification.\n\nWhy Google personnel request access to Customer Data\n----------------------------------------------------\n\nThe most common reason why Google personnel request access to\n[Customer Data](/terms/service-terms) is to resolve a customer support ticket.\nIf you create a customer support request, then a Google personnel might be\nrequired to request access to your data. Access Transparency exists to provide\ncustomers visibility into these accesses. Google provides various controls\nto support the private of your data, regardless of whether Access Transparency is\nenabled on an organization. For more information about these controls, see\n[Google infrastructure security design overview](/docs/security/infrastructure/design).\n\nWhat is privileged access\n-------------------------\n\nGoogle personnel's access to your data to fulfill an obligation of providing\na contracted service is called *privileged access*. Access to your data\nin Google Cloud is usually because of the following reasons:\n\n- You are accessing your own data.\n- A service you are using is accessing data on your behalf.\n\nWhen requested to provide a contracted service, Google personnel acting as a\nprivileged administrator can access your data.\n\nFoundational principles of privileged access management\n-------------------------------------------------------\n\nGoogle Cloud's privileged access management strategy strictly limits what a\nsingle Google staff member can view and do with your data. Google Cloud's\nprivileged access philosophy is based on the following principles:\n\n- **Least privilege**: Access to Customer Data is denied by default for all\n Google personnel. When access is granted, it is temporary and no greater than\n what is absolutely necessary to provide the contracted service.\n\n- **Limit singular access to data**: Singularly accessing Customer Data without\n another individual involved is extremely difficult for any and every\n Google personnel.\n\n- **All access must be justified** : By default, Google personnel don't have\n access to Customer Data. Google personnel can access your data only with an\n **active** , valid business justification. Google personnel can't access\n Customer Data for justifications that are closed or where the Google person is\n not a directly linked collaborator. For the list of valid business\n justifications, see [Justification reason codes](/assured-workloads/access-transparency/docs/reading-logs#justification-reason-codes).\n\n- **Monitor and alerting**: Monitoring and response processes exist to identify,\n triage, and remediate violations of these principles.\n\nFor more information about Google Cloud's privileged access philosophy, see\n[Privileged access in\nGoogle Cloud](/docs/security/privileged-access-management).\n\nGoogle Cloud products regularly undergo independent, third-party audits and\ncertifications to verify that their data protection practices match their\ncontrols and commitments. For more information about how Google Cloud products\nprovide customers with transparency and control over their content, see the\nwhitepaper on [Trusting your data with Google Cloud](https://services.google.com/fh/files/misc/072022_google_cloud_trust_whitepaper.pdf).\n\nWhat's next\n-----------\n\n- To know more about Google Cloud's commitment toward protecting the privacy\n of Customer Data, see\n [Google Cloud and common privacy principles](/privacy/common-privacy-principles).\n\n- To learn about the core principles upon which controls that prevent\n unauthorized administrative access are based, see\n [Overview of administrative access controls](/assured-workloads/cloud-provider-access-management/docs/administrative-access).\n\n- To see the list of business justifications for which Google personnel can\n request to access customer data, see\n [Justification reason codes](/assured-workloads/access-transparency/docs/reading-logs#justification-reason-codes)."]]
