[[["易于理解","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-02。"],[[["\u003cp\u003eChrome Enterprise Premium uses a zero-trust approach, dynamically granting access based on user and device information via its Access Context Manager.\u003c/p\u003e\n"],["\u003cp\u003eAccess Context Manager enables administrators to establish fine-grained, attribute-based access controls for applications and Google Cloud resources, organizing trust into tiers, such as \u003ccode\u003eHigh_Level\u003c/code\u003e and \u003ccode\u003eMedium_Level\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eEnterprise certificates serve as a critical context-aware signal to identify corporate-owned devices, and they can be assessed in custom access levels using macros like \u003ccode\u003e.exists(e,p)\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eAdministrators must upload trust anchors (root CA and intermediary certificates) in the Admin console to allow Chrome Enterprise Premium to validate device certificates.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring the AutoSelectCertificateForUrls Chrome policy is essential for Endpoint Verification to search for and collect device certificates, ensuring proper policy application and status.\u003c/p\u003e\n"]]],[],null,["# Configuring enterprise certificate conditions\n\nA key principle of Chrome Enterprise Premium is \"Access to services is granted based on what\nwe know about you and your device.\" The level of access given to a single user\nor a single device is dynamically inferred by interrogating multiple data\nsources. Chrome Enterprise Premium uses this level of trust as part of its decision process.\n\nAccess Context Manager is Chrome Enterprise Premium's zero-trust policy engine. Access Context Manager allows\nadministrators to define fine-grained, attribute based access control for\napplications and Google Cloud resources.\n\nUse access levels to permit access to resources based on contextual information\nabout the request. By using access levels, you can start to organize tiers of\ntrust. For example, you might create an access level called `High_Level` that\npermits requests from a small group of highly-privileged individuals. You might\nalso identify a more general group to trust, such as an IP range that you want\nto permit requests from. In that case, you might create an access level called\n`Medium_Level` to permit those requests.\n\nOne of the key requirements for zero trust access is to only allow access when\nthe device is managed or owned by the company. There are many ways to determine\nwhether a device is corporate-owned, and one way is to determine if a valid\ncertificate, issued by the company, exists on the device. The existence of an\nenterprise certificate on a device can be used to indicate that the device is\ncorporate-owned.\n\nEnterprise certificates for context-aware access is a feature of the overall\nChrome Enterprise Premium certificate-based access solution. This feature leverages device\ncertificates as an alternative context-aware signal to determine if a device is\na corporate-owned asset. This feature is supported on Chrome browser 110 or\nlater.\n\nBecause a device can have more than one certificate, enterprise certificates can\nbe accessed in the custom access level through macros `.exist(e,p)`: \n\n device.certificates.exists(cert, predicate)\n\nIn the example, `cert` is an identifier to be used in `predicator` which\nbinds to the device certificate. The `exist()` macro combines per-element\npredicate results with the \"or\" (\\|\\|) operator, meaning that macros return true\nif at least one certificate satisfies the `predicate` expression.\n\nThe certificate has the following attributes that can be checked together. Note\nthat string comparisons are case-sensitive.\n\nThe following table contains examples of policies that you can set:\n\n| **Important:** Endpoint Verification reports a single enterprise device certificate to the Admin console, even if multiple certificates are present on a device. This means that, regardless of how many enterprise certificates your device has, the Admin console displays only one.\n\nConfiguring enterprise certificates\n-----------------------------------\n\nBefore configuring enterprise certificates, ensure you have configured custom\naccess levels. For instructions, see [Creating a custom access\nlevel](/access-context-manager/docs/create-custom-access-level).\n\nYou can use an Access Context Manager custom access level definition to set the\nappropriate policies. Custom access levels use boolean expressions written in a\nsubset of [Common Expression Language\n(CEL)](https://opensource.google/projects/cel) to test the attributes of a\nclient making a request.\n| **Important:** For Windows devices, install the client certificate in the user certificate store, not in the computer certificate store. If the client certificate is installed in the computer certificate store, authenticated users must be able read but not export its private key container for mTLS signing.\n\n### Uploading trust anchors in the Admin console\n\nIn order for Chrome Enterprise Premium to collect and validate the device enterprise\ncertificate, you must upload the trust anchors and any intermediary certificates\nthat are used to issue the device certificate. The trust anchors here refer to\nthe self signed root CA (Certification Authority) certificate and the relevant\nintermediate and subordinate certificates. Complete the following steps to\nupload the trust anchors:\n\n1. Go to the [Admin console](https://admin.google.com/) and navigate to **Devices \\\u003e Networks \\\u003e Certificates**.\n2. Select the appropriate organizational unit.\n3. Select **Add Certificate**.\n4. Enter the certificate name.\n5. Upload the certificate.\n6. Enable the **Endpoint Verification** checkbox.\n7. Click **Add**.\n8. Ensure users belong to the organizational unit for which the trust anchors are uploaded.\n\n### Configure an AutoSelectCertificateForUrls policy\n\nFor Endpoint Verification to search the device certificate and collect it\nthrough Chrome, you must configure the AutoSelectCertificateForURLs chrome\npolicy by completing the following steps:\n\n1. Ensure that the Chrome browser is managed by Chrome Browser Cloud Management.\n\n - \\[Win/OSX/Linux\\] Setup for managed chrome browser using CBCM \u003chttps://support.google.com/chrome/a/answer/9301891\u003e.\n - \\[Chrome\\] Enroll the device to the enterprise.\n2. In the Admin console, add the AutoSelectCertificateForUrls policy:\n\n 1. Go to the [Admin console](https://admin.google.com/) and navigate to **Devices \\\u003e Chrome \\\u003e Settings \\\u003e User \\& Browser Settings \\\u003e Client certificates**.\n 2. Select the appropriate organizational unit.\n 3. Add a policy [AutoSelectCertificateForUrls](https://chromeenterprise.google/policies/?policy=AutoSelectCertificateForUrls),\n as demonstrated in the following example:\n\n {\"pattern\":\"https://[*.]clients6.google.com\",\"filter\":{\"ISSUER\":{\"CN\":\"\u003cvar translate=\"no\"\u003eCERTIFICATE_ISSUER_NAME\u003c/var\u003e\"}}}\n\n Replace \u003cvar translate=\"no\"\u003eCERTIFICATE_ISSUER_NAME\u003c/var\u003e with the common name\n of the root CA.\n Do not modify the value of `pattern`.\n\n| **Note:** The filter should refer to an issuer certificate, uploaded in the previous steps.\n\nTo verify the policy configuration, complete the following steps:\n\n1. Navigate to chrome://policy in the browser.\n2. Verify the configured value for **AutoSelectCertificateForUrls**.\n3. Ensure that the policy **Applies to** value is set to **Machine** . On the Chrome operating system, the value is applied to **Current User**\\*.\n4. Ensure that the **Status** for the policy does not have a **Conflict**.\n\nTroubleshooting your configuration\n----------------------------------\n\nReview the certificate attributes on the device details page to ensure that\ncertificate attributes are listed correctly.\n\nYou can use the Endpoint Verification logs to help you troubleshoot any issues. To\ndownload the Endpoint Verification logs, complete the following steps:\n\n1. Right-click on the Endpoint Verification extension and then go to **Options**.\n2. Select **Log level \\\u003e All \\\u003e Download Logs**.\n3. Open a support case with Cloud Customer Care and share the logs for further debugging."]]