For the complete documentation index, see llms.txt. This page is also available as Markdown.

OAuth Security

Overview

Material monitors third-party app access in your Google Workspace environment in real time. Advanced plans include the OAuth Remediation Agent, which adds AI-powered investigation, automated classification, and recurring audits.

Why OAuth Security Matters

OAuth is how most third-party apps, and increasingly AI agents, connect to your Google Workspace. When a user connects to a tool or authorizes a new AI assistant, they're granting that app an OAuth token: a persistent, programmatic key to their Gmail, Drive, Calendar, or other Google data.

The problem is threefold:

The Approval Bottleneck Every new app install is a potential risk that someone needs to evaluate. In practice, that means admins spend hours researching obscure vendors, chasing users to understand why they installed something, and manually deciding whether to allow or block it. For lean security teams, this backlog never shrinks.

The Silent Breach OAuth tokens don't expire when a user changes their password or enables MFA. A token granted months ago to a vendor that has since been compromised is still active, and your team likely doesn't know. The typical discovery timeline is months, often triggered by a manual audit or a breach announcement from the vendor.

The Transparency Gap Existing automation tools try to solve this but fail for a simple reason: they're black boxes. Admins disable them because they can't answer the questions that matter: "What breaks if I revoke this?" and "Who's actually using it right now?" Without transparency, automation feels like a liability.

Meanwhile, the risk is growing. As organizations adopt AI tools that connect to the enterprise stack via OAuth, every new agent installation is another persistent access point that often carries broader permissions than the task actually requires.

Take a look at our CISO's recent LinkedIn post demonstrating these risks.

How Material address OAuth Risk

Material's approach is built around a coordinated model: the agent handles the high-volume work of research, outreach, and triage, while you retain oversight for decisions that carry real business risk.

This means:

  • Real-time detection instead of hourly polling. The agent catches new OAuth activity as it happens, not after the fact.

  • AI-powered investigation that answers the questions admins actually need: who's using this, what can it access, and should I be concerned?

  • Automated remediation based on policies you define. The agent acts, so you don't have to.

spinner

Two tiers of capability are available depending on your plan:

  • Essentials: Real-time OAuth inventory, scope visibility, and account blast radius. The Application was granted OAuth access for the first time detection fires when a user connects a new app, creating an issue for review. You can manually classify apps and configure responses per classification, including token revocation.

  • Advanced: Everything in Essentials, plus the OAuth Remediation Agent, which adds AI-powered investigation, automated classification (coming soon), end-user notifications, and recurring 90-day audits.

Note: This feature is not available for customers who have opted out of Material’s GenAI capabilities.


How the OAuth Remediation Agent Works

The OAuth Remediation Agent is a collection of detections that fire when OAuth activity occurs in your environment, paired with an AI investigation agent that researches each app, scores it across four risk factors, and recommends a classification.

At a high level, here's how it works:

  1. A detection fires: real-time event monitoring catches new or changed OAuth activity in your environment

  2. The agent investigates: researches the app across four risk factors and produces a classification and plain-language summary

  3. A response executes: based on policies you configure, the agent automatically revokes tokens, notifies users, or takes no action

  4. An issue surfaces: if human review is needed, it appears in your dashboard with the investigation already done. Accepting the agent's suggested classification automatically resolves the issue.

The result: your team spends less time chasing down app justifications and more time on the work that actually requires your judgment.

Apps Dashboard

The Apps dashboard located in the Explorer gives you a high level view of all your connected apps, their classifications, active issues, active accounts etc.

Apps dashboard showing connected OAuth apps, classifications, active issues, and account counts
Apps dashboard in Explorer

To narrow the list to the apps specific people use, apply the Accounts filter. Select one or more accounts to see only the apps those accounts have granted, including grants that were later revoked. CSV export respects the filter, so you can export exactly the apps you've filtered to.

Click the Accounts tab on any app detail view to see all connected users. The tab opens filtered to active accounts, with a count that matches what's shown, and includes a Scope Level column and filters so you can narrow the list. The App status column shows whether each account's token is active or revoked, with the revoke date on the badge itself and the full timestamp on hover. If a token can't be revoked, a tooltip explains why. The Remediation column is hidden by default to keep the view uncluttered; you can turn it back on from the table's display options. You can also select multiple accounts and revoke their tokens at once.

Four more columns show what each account has at stake, so you can judge a grant without leaving the app:

  • Email Redaction: whether sensitive emails are redacted from this app's access. Filter the tab by this column to separate the accounts that are covered from the ones that aren't.

  • Sensitive Emails and Sensitive Files: how much sensitive content the account holds. These are account-wide counts, rather than only what this app can reach.

  • VIP: whether the account belongs to a VIP.

All four are included in the CSV export, so you can pull an account list with its risk context attached.

App detail view with the Accounts tab showing connected users for an OAuth app
Accounts connected to an OAuth app
OAuth app Accounts tab filtered to active accounts, with the matching account count
Accounts tab filtered to active accounts

Expand an account row to display the specific OAuth scopes that user granted. Scopes can differ between users, giving you a precise view of each account's actual access.

Expanded account row showing OAuth scopes granted by a specific user
Granted OAuth scopes for one account

Getting Started

If you're just getting started with the OAuth Remediation Agent, complete these tasks:

Last updated

Was this helpful?