Skip to content
Ryan James
Menu

← Newsletter5 min read

The Door You Left Open: OAuth Scopes and the Security Debt Hiding in Your Google Workspace

In rock climbing, accidents rarely happen because of a single catastrophic mistake. More often, they’re the result of a series of small decisions that each seemed fine in isolation — until they weren’t. The climbing community takes those incidents seriously. They investigate, they share findings, and they ask the hard question: what could we have done differently?

That’s the posture we need to bring to cybersecurity — especially when a breach happens that turns out to be preventable.

A recent incident involving a developer platform made headlines when a data breach exposed private API keys belonging to thousands of customers. The root cause wasn’t a sophisticated, months-long exploit. It was something far more mundane: an employee had granted broad OAuth access to a third-party AI tool, that tool’s systems were compromised, and suddenly private credentials were in the wrong hands. The door wasn’t kicked in. It was left open.

For those of us managing technology in K-12 schools, this should land as a direct warning.

What Is OAuth, and Why Should You Care?

OAuth is the mechanism behind that familiar “Sign in with Google” button. When a staff member clicks it to create an account with a third-party app, they’re not just creating an account — they’re authorizing that app to access certain parts of their Google account on their behalf. Those authorized pieces are called scopes.

At its most harmless, a scope might just confirm identity: this is who they say they are. That’s the single sign-on (SSO) use case, and it’s mostly benign.

But the Google API — the system that powers these integrations — supports hundreds of different scopes. And not all of them are harmless.

Some scopes allow an app to read your emails. Others can access your calendar, your contacts, your administrative directory. And some — particularly around Google Drive — can grant permissions that should make any IT administrator uncomfortable. There are Drive scopes that allow a third party to download every file a user has access to. Not just files they own. Every file shared with them.

In a school environment, that could mean student records, IEPs, HR documents, financial data, or confidential communications — all potentially accessible to an external system you don’t control and whose security practices you can’t verify.

The Convenience Trap

Here’s what makes this problem particularly tricky in education: convenience is genuinely valuable.

Google SSO reduces password fatigue, simplifies account management, and removes friction for staff who are already stretched thin. When a new ed-tech tool shows up with a “Sign in with Google” button, it feels like a feature, not a risk. And most of the time, the staff member clicking that button isn’t thinking about OAuth scopes — they’re thinking about whether the tool will help them do their job.

The problem is that third-party apps can request access far beyond what they actually need to function. And users, understandably, just click through.

Worse, the permissions granted at signup aren’t necessarily fixed. A trusted app that only requested SSO access today can request additional scopes later — and depending on how your domain is configured, that expanded access might be granted without any admin review.

What This Looks Like at Scale

If you manage a Google Workspace domain for a school, here’s an uncomfortable exercise: open your Google Admin console and navigate to Security > API Controls > App Access Control. Look at how many third-party apps currently have access to your domain. Then look at what they have access to.

If you haven’t done this audit recently, you may find apps that haven’t been used in years still holding active permissions. You may find tools that requested — and received — scopes far broader than their stated purpose. You may find apps approved by admins who no longer work at your school.

This is what security debt looks like. It accumulates quietly, one “Sign in with Google” at a time.

A Practical Roadmap

Cleaning this up isn’t a single afternoon project, but it’s absolutely manageable if you approach it in phases.

1. Shut down self-service OAuth access.

Your first move is to restrict the ability for staff and students to independently authorize third-party apps using Google SSO. In Google Admin, you can configure App Access Control to block all third-party app access by default and require admin approval for anything new. This immediately stops the bleeding — no new apps get OAuth access without someone reviewing what they’re actually asking for.

2. Audit what’s already been granted.

This is the harder work, and it takes time. Go through your existing authorized apps and evaluate each one against a simple framework: Is this app still in use? What scopes does it hold? Do those scopes match what the app actually needs to function? Is there a vendor security policy or SOC 2 report you can reference?

Work with your instructional and administrative leadership to decide which apps stay, which get scoped down, and which get revoked entirely. You don’t have to do this alone — and you shouldn’t.

3. Establish clear ownership and accountability.

Too many admins on a domain without clear accountability creates its own problems. If any admin can approve OAuth access, it becomes impossible to audit who approved what. Define who has the authority to approve third-party integrations, make sure admin actions are tied to individual named accounts rather than shared credentials, and document your approval decisions.

4. Educate your staff — and lead with “why.”

When you start requiring approvals for tools that used to be self-service, you will get pushback. That’s normal. The key is to get ahead of it by explaining the reasoning before people hit the wall. Help your staff understand that you’re not trying to block useful tools — you’re making sure that when they sign into something with their school Google account, they’re not inadvertently handing over access to sensitive student data.

Frame it the way you’d frame physical building security: we put locks on the doors not because we don’t trust our people, but because we’re responsible for what’s inside.

Give Yourself Some Grace

If this audit reveals that your current state isn’t where it should be, you’re not alone — and beating yourself up about it won’t move the work forward.

Most K-12 IT administrators are managing an enormous surface area with limited staff, limited time, and a constant stream of immediate priorities. OAuth scope management is exactly the kind of important-but-not-urgent work that gets deferred when servers are down, classrooms need support, and the board wants a new initiative stood up by Monday.

The goal isn’t perfection. It’s progress, intentionality, and a clear direction. Document where you are, build toward where you want to be, and communicate openly with your leadership about both.

The Takeaway

The breach that prompted this article happened because broad access was granted without enough scrutiny, to a system whose security couldn’t be independently verified. That’s a story that could play out in any school district running Google Workspace — and the sensitive data at stake makes the consequences far more serious than exposed API keys.

OAuth scopes aren’t glamorous. They don’t make for exciting professional development. But they represent a real, manageable risk sitting quietly inside your domain right now.

Lock the door. Then figure out who else has a key.

Keep coding!
Ryan

This post first went out on Substack. Join the conversation there or subscribe to get the next one by email.