This document shows how administrators can enable Endpoint Verification to collect granular device attributes called configurable device attributes , such as metadata attributes of files, folders, and binaries; registry entries; and properties in a plist. Administrators can use these configurable device attributes to create access levels.
Before you begin
Configure the Endpoint Verification settings
To enable Endpoint Verification to collect the device configuration attributes , do the following:
-
Log in to the Google Admin consoleby using your Google Workspace administrator account.
-
In the navigation menu, click Devices > Mobile & endpoints > Settings > Universal.
-
Expand the Endpoint Verification configurationtab.
-
From the Organizational Unitspane, select your organization unit.
-
Depending on the type of configurable device attributes you want Endpoint Verification to collect, configure the settings:
-
To collect metadata attributes of a file, folder, or binary, do the following:
- In the File or folder configurationsection, click Add configuration.
-
In the Add configurationdialog, enter the following details:
- Name for the configuration.
- Operating system of the devices.
- Path to the file, folder, or binary.
-
If you entered the path for a binary, then select Is executable.
-
Click Add configuration.
-
To collect registry or plist configuration attributes, do the following:
- In the Registry or plist configurationssection, click Add configuration.
-
In the Add configurationdialog, enter the following details:
- Name for the configuration.
- Operating system of the devices.
- Path to the registry or plist file.
-
Key (optional for Windows):
-
Windows: a subkey of the registry, for example:
IsClipboardSignalProducingFeatureAvailable. If you don't enter a value, then the default value is taken. -
macOS: keys in the plist file, which can be a number, string, or a boolean value. You can also provide nested keys by using
.as the delimiter.For example, if there is a dictionary B inside dictionary A and dictionary B contains a string or number with key
key1, the final key would beA.B.key1. Arrays are supported in the following manner:A.B.key[0]orA.B.key[1].C. Only hard-coded indexes are supported.
-
-
Click Add configuration.
-

