This document describes the basic concepts of Endpoint Verification.

Endpoint Verification lets security administrators or security operations
professionals secure Google Cloud, on-premises apps and resources, and
Google Workspace apps.

Endpoint Verification is part of Google Cloud
[Chrome Enterprise Premium](https://docs.cloud.google.com/chrome-enterprise-premium/docs/overview.md.txt) and is available to all
Google Cloud, Cloud Identity, Google Workspace for Business, and
Google Workspace for Enterprise customers.

## When to use Endpoint Verification

Use Endpoint Verification when you want an overview of the security posture of the
devices that are used to access your organization's resources, such as laptops
and desktops.

As a security administrator or security operations professional, your goal is to
manage secure access to your organization's resources. The employees of your
organization can use either the company-owned devices or their unmanaged
personal devices to access the organization's resources. When Endpoint Verification
is installed on the devices that access your organization's resources, it
collects and reports device inventory information. You can use this device
inventory information to manage secure access to your organization's resources.

When paired with the other offerings of Chrome Enterprise Premium, Endpoint Verification helps
enforce fine-grained access control on your Google Cloud resources.

## How Endpoint Verification works

Endpoint Verification consists of a Chrome extension that collects and reports
device inventory information by constantly syncing with Google Cloud.
Endpoint Verification creates an inventory of devices with Chrome browser that
access your organization's data.

For example, after Endpoint Verification is deployed on devices that are used to
access Google Cloud resources, Endpoint Verification populates information
about those devices. As an administrator, you can review the
device information including encryption status, OS, and other details, and use
this information to manage access control.

For more information, see [Device attributes collected by Endpoint Verification](https://docs.cloud.google.com/endpoint-verification/docs/device-information.md.txt).

## How Endpoint Verification works with Access Context Manager

[Access Context Manager](https://docs.cloud.google.com/access-context-manager/docs.md.txt), which is part of Google Cloud
[Chrome Enterprise Premium](https://docs.cloud.google.com/chrome-enterprise-premium/docs/overview.md.txt),
lets security administrators or security operations professionals define
fine-grained and attribute-based access control for projects and resources in
Google Cloud and resources in Google Workspace.

Access Context Manager references the device attributes collected by Endpoint Verification to
enforce fine-grained access control with [access levels](https://docs.cloud.google.com/access-context-manager/docs/overview.md.txt#access-levels).

The following diagram shows how Endpoint Verification works with Access Context Manager:

![Endpoint Verification flow](https://docs.cloud.google.com/endpoint-verification/images/endpoint-verification-flow.png)

## How Endpoint Verification works with third-party clients

In [Chrome Enterprise Premium and third-party client integrations](https://docs.cloud.google.com/chrome-enterprise-premium/docs/integration-docs.md.txt),
third-party clients such as CrowdStrike and Microsoft Intune collect
real-time device information. Endpoint Verification communicates with these
third-party clients to collect their device information and makes them available
for [Access Context Manager](https://docs.cloud.google.com/access-context-manager/docs.md.txt).

Access Context Manager references the device attributes collected by Endpoint Verification and
third-party clients to enforce fine-grained access control with [access levels](https://docs.cloud.google.com/access-context-manager/docs/overview.md.txt#access-levels).

The following diagram shows how Endpoint Verification and third-party clients work
with Access Context Manager:

![Endpoint Verification with 3rd party client integrations](https://docs.cloud.google.com/endpoint-verification/images/ev-partner.svg)

## What's next

- [Quickstart: Set up Endpoint Verification on your devices](https://docs.cloud.google.com/endpoint-verification/docs/quickstart.md.txt)
- [Device attributes collected by Endpoint Verification](https://docs.cloud.google.com/endpoint-verification/docs/device-information.md.txt)
- [Deploy Endpoint Verification](https://docs.cloud.google.com/endpoint-verification/docs/deploying-with-admin-console.md.txt)