Set up the Secure Access Monitor plugin for Google Chrome
The Secure Access Monitor (SAM) plugin is a managed Chrome extension used to monitor unmanaged OAuth grants and transfer the collected data to Okta ISPM.
About this task
The SAM plugin is available by default with an Okta for AI Agents license. If you have the Okta ISPM license only, contact Support for plugin access.
Okta for AI Agents - Core excludes Okta Privileged Access, Identity Security Posture Management, and any features that have not yet received a FedRAMP Moderate, FedRAMP High, or U.S. Department of Defense Impact Level authorization. For a current list of excluded features, refer to the Okta US Public Sector Limitations or Exceptions documentation. The Okta for AI Agents - Core SKU is the version that's available to Okta for Government Moderate, Okta for Government High, and Okta for US Military customers.
For the current plugin version and past releases, see Okta Secure Access Monitor plugin version history.
Before you begin
- Your ISPM tenant is in the same region as your Okta tenant. This feature isn't enabled for cross-region access.
- Your org is connected to Google Chrome Enterprise. The plugin only works on managed browsers. See Integrate Okta with Chrome Enterprise.
- Your browsers are enrolled in Chrome Enterprise Core. See Enroll cloud-managed Chrome browsers. Third-party MDM solutions alone are insufficient. On Windows, you also need the required registry or MDM settings.
- You have the super admin role.
- You have access to the Google Admin Console.
- You have an active Okta ISPM tenant (ISPM or Okta AI license).
- Your security policies don't block OAuth grants.
-
You know that the SAM client certificate interferes with manual certificate selection flows (Smart Card, PIV, Legacy Device Trust).
-
If you use a SASE solution, you've configured it to exempt the Okta URL from TLS inspection.
-
Your browser policies don't pin the browser to a specific client certificate.
Procedure
What to do next
Have end users sign in to their managed Chrome profiles and to the Okta End-User Dashboard using the org URL.
Then, verify your installation.