[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-01。"],[[["\u003cp\u003eAdministrative access refers to Google personnel accessing customer content using internal tools, which differs from explicitly granted user permissions.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud's core principle is to deny access to customer content by default, emphasizing that user data belongs exclusively to the user organization.\u003c/p\u003e\n"],["\u003cp\u003eAdministrative access to customer content requires an auditable justification, and can be optionally subject to explicit approval, ensuring accountability.\u003c/p\u003e\n"],["\u003cp\u003eAll administrative access is logged by default, with Access Transparency providing near real-time audit logs of Google personnel's access to user content.\u003c/p\u003e\n"],["\u003cp\u003eEmergency access can override Access Approval policies when there is an urgent threat to Google's or customer services, and these instances are logged as \u003ccode\u003eauto-approved\u003c/code\u003e in Access Approval.\u003c/p\u003e\n"]]],[],null,["# Overview of administrative access controls\n==========================================\n\nThis page provides an overview of the core underlying principles based on which\nGoogle Cloud's administrative access controls are designed.\n\nWhat is administrative access\n-----------------------------\n\nAdministrative access includes access to Customer Data by Google personnel by\nadministrative means. For example, a Google employee utilizing an internal\nsupport tool to access the contents of a Spanner database to diagnose a\ncustomer-raised support case that cites database issues.\n\nAn example of non-administrative access is granting a Google employee direct\nIAM access at the project-level by assigning standard user\npermissions in the user space. Access by this Google employee in the project\nwhere you explicitly granted access doesn't constitute administrative access.\n\nThe objective of the administrative access controls is to ensure that Customer\nData on Google Cloud isn't accessible to Google employees without an auditable\njustification, and optionally, an explicit approval.\n\nCore principles\n---------------\n\nThis section describes the core principles that Customer Data access at\nGoogle Cloud adheres to.\n\n### Deny access by default: User content belongs explicitly to the user organization\n\nGoogle Cloud is strongly committed to ensuring that Customer Data belongs to\nthe customers. This stance is the default posture of every Google employee\ntowards Customer Data.\n\n### Content owner's control over administrative access is a core commitment\n\nAccess events are a standard operational element of any cloud-based business.\nFor example, support personnel might need to access Customer Data to provide\nthe requested support, and engineers might need to do it to dig deeper to\nresolve an issue discovered during the support request investigation.\nGoogle Cloud's philosophy is to provide complete logging and approval support\nfor content access with the Access Transparency and Access Approval features.\n\nThe following table explains the difference between automated and human access:\n\nThe following table explains the difference between emergency and non-emergency\naccess:\n\n### Every access requires a justification\n\nAdministrative access is gated behind an auditable, valid business justification\nwith some exceptions.\n\nFor the complete list of business justifications for accessing Customer Data,\nsee [Justification reason codes](/assured-workloads/access-transparency/docs/reading-logs#justification_reason_codes).\n\n### Access logging is universal\n\nAdministrative access to Customer Data is logged by default. After you have\n[enabled Access Transparency](/assured-workloads/access-transparency/docs/enable), near real-time audit logs of any access by\nGoogle personnel to user content in the organization are published to each\nproject's logs. These accesses are monitored internally by Google's auditors and\nare visible externally through Access Transparency logs. For information about viewing\nthese logs, see [Understanding and using Access Transparency logs](/assured-workloads/access-transparency/docs/reading-logs).\n\n### Use Assured Workloads for further coverage\n\nAssured Workloads can provide administrative controls that meet the\nmore stringent guidelines laid out by US government certifications, including\nrestrictions on data access by non-US personnel.\n\nFor more information, see\n[Personnel\ndata access and support controls](/assured-workloads/docs/personnel-access-data-controls).\n\nWhat's next\n-----------\n\n- [Privileged access at Google Cloud](/assured-workloads/access-transparency/docs/privileged-access)\n- [Whitepaper about managing and safeguarding your content stored on Google Cloud](https://services.google.com/fh/files/misc/072022_google_cloud_trust_whitepaper.pdf)\n- [Whitepaper about data residency, operational transparency, and privacy for European customers](https://services.google.com/fh/files/misc/googlecloud_european_commitments_whitepaper.pdf)\n- [Overview of Key Access Justifications](/assured-workloads/key-access-justifications/docs/overview)\n- [Overview of Access Transparency](/assured-workloads/access-transparency/docs/overview)\n- [Overview of Access Approval](/assured-workloads/access-approval/docs/overview)"]]
