# Verified Access

Verified Access as the name suggests, is a feature which ensures every device connecting to the enterprise network is unmodified and complies with the enterprise policies. Verified Access serves as the entry point for a network entity to get a hardware-backed cryptographic guarantee of both the device identity as well as the identity of the device user. You can know more about [Verified Access here](https://cloud.googleblog.com/2016/09/pushing-the-boundary-of-Chrome-OS-Security-with-Verified-Access.html). This profile can be applied either as a user profile or device profile, with the configurations getting applied to user or device based on the profile type.

## Profile Description

| Profile Specification | Description |
|---|---|
| Verified Access for Enterprise Extensions | Allow/Restrict interaction of Chrome extensions in user sessions with [Trusted Platform Module](https://www.chromium.org/developers/design-documents/tpm-usage) |
| Verified Access for Content Protection | Allow/Restrict protected content from being played on the device |
| Service Accounts Allowed to verify device | Specify the list of e-mail address that have limited access to the Verified Access APIs to verify device |
| Service Accounts Allowed to verify device and access device data | Specify the list of e-mail address that have limited access to the Verified Access APIs to verify device and access device data. |