[[["容易理解","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-07-11 (世界標準時間)。"],[[["Endpoint Verification can be configured to collect detailed device attributes, including metadata of files, folders, binaries, registry entries, and plist properties."],["Administrators can leverage these collected device attributes to establish and manage access levels based on specific device configurations."],["Configuration involves logging into the Google Admin console and navigating to the Endpoint Verification settings to add specific file, folder, binary, registry, or plist configurations."],["When configuring file, folder, or binary attribute collection, administrators must specify the path and, if applicable, indicate whether the item is executable, and respect the file size limit of 1GB."],["When configuring registry or plist attribute collection, administrators need to specify the path, and for Windows they may optionally input a subkey, while for macOS, nested keys in plists are supported using dot notation."]]],[]]