You clicked “authorize” on that project management integration in about 30 seconds. You didn’t read what you were agreeing to. And if you’ve been running your business for more than two years, you’ve done that at least a dozen times. The apps are still connected. You’ve forgotten most of them. Some of them have access to your email, your customer list, your financial data, or all three.

third-party app security audit small business

A third-party app security audit is a systematic review of every external tool connected to your core systems: what data access each one has, whether that access is still necessary, and whether the vendor can actually be trusted with it. It takes a few hours, requires no IT background, and will almost certainly surface at least one thing that shouldn’t still be there.

01Why Your Permission Grants Are Basically Blank Checks

When you click “authorize” on a new integration, you’re signing off on a permission scope written by a product team optimizing for functionality, not for your data hygiene. “Read and manage your email” doesn’t mean “occasionally check your inbox.” It means the app can read every email you’ve ever sent or received, delete messages, send on your behalf, and in some configurations, forward everything to an external server automatically.

The app asks for the broadest permission that makes its features functional, because narrow permissions create friction if they ever want to expand later. You accept because you want the integration working in five minutes. Nobody reads the permission screen. The app knows nobody reads the permission screen.

The exposure isn’t hypothetical. A reporting dashboard connected to your Google Workspace can access every document, spreadsheet, and email in your organization. A CRM integration connected to Stripe can read your full transaction history. An email automation tool with calendar access can see every meeting on your schedule, including who you’re meeting with and what you discussed in the invite. You agreed to all of it. You just didn’t know you agreed to all of it.

02The Audit You Can Run in an Afternoon (Without IT Help)

The goal is an inventory: every app with active access to your core systems, what it can do, and when it last touched anything. You need a few hours and the patience to click through some settings menus.

Where to Find Your Connected Apps

  • Google Workspace: Go to myaccount.google.com → Security → Third-party apps with account access. Every app ever granted OAuth access to any Google account in your org shows up here, including ones installed by employees who left two years ago.
  • Microsoft 365: Admin Center → Settings → Integrated apps. Also check myapplications.microsoft.com for individual-user grants that might not surface in the admin view.
  • Stripe: Dashboard → Developers → Connected applications. Accounting tools, invoicing apps, and “financial dashboards” often have full read access to your transaction history. This one tends to surprise people.
  • Your CRM: Check the marketplace or integrations tab directly in the app. Salesforce, HubSpot, and Pipedrive all have dedicated views for connected apps and their permission levels.
  • Zapier / Make: Every connection in these tools represents a permission grant somewhere else. Pull your full list of active zaps or scenarios and trace each one back to its source and destination.

As you go through each platform, flag three things: apps you don’t recognize, apps you’ve stopped using but never disconnected, and apps whose permission scope looks broader than what the tool actually does. A grammar checker with access to your entire Google Drive is worth a closer look. A “read-only” reporting tool with write permissions is worth a very close look.

Document everything in a simple spreadsheet: app name, connected platform, permission level, last active date, and a column for “keep / revoke / investigate.” It doesn’t need to be beautiful. It needs to exist.

03The Apps That Have More Access Than They Deserve

Some categories are consistently worse offenders, not because they’re malicious but because they asked for everything and expected you to sort it out.

Email automation tools are the most common culprit. To send email on your behalf, they need mail access. But many also request calendar access, contact management permissions, and occasionally full Google Drive or OneDrive access for “attachment features” that 90% of users never touch. You’re using it to send a welcome sequence. It can read your board meeting notes.

CRM integrations are second. Most CRM-to-Gmail integrations request full mailbox access when they only need to log sent emails and read replies. The difference between those two permission scopes is the difference between a tool that can see one thread and a tool that can see everything.

Reporting and analytics dashboards connect to everything at once: Stripe, QuickBooks, your CRM, your Google Analytics. Read-only sounds safe until you consider that read access to your full financial history, held by a vendor you’ve never audited, is not actually the same as safe.

04Revoking Access Breaks Less Than You Think

The anxiety keeping dangerous integrations alive is straightforward: you’re not sure what breaks if you disconnect, so you leave it. Fully authorized, mostly forgotten, occasionally doing something you’ve stopped caring about. This is how a small accounting firm ends up with ransomware traced back to a CRM integration nobody had touched in eight months.

When you revoke an app’s access, it stops being able to read or write to your connected systems. It doesn’t delete your account, break other tools, or wipe anything. If the app was doing something you still need, you’ll find out immediately when that thing stops working. The feared cascade of broken workflows almost never materializes. What materializes is one email from someone saying their sync stopped, which you fix in four minutes.

What doesn’t happen: your data disappears from the vendor’s servers. If an app has already copied your customer database to its own infrastructure, revoking OAuth access doesn’t reach any of that. Revoking limits future exposure. It doesn’t undo past exposure.

Revoke aggressively on anything you don’t recognize, haven’t used in 90 days, or can’t explain the purpose of. The workflow disruption will be minimal. The cleanup if you don’t is not.

05Is Your Vendor Actually Safe, or Just Confident About It?

“We take security seriously” is not an answer. Every company that has ever been breached said that, usually on the same webpage that’s now serving as evidence in a class action lawsuit. When evaluating a vendor, you need specifics.

  • Do you have a SOC 2 Type II report? Type II means an external auditor reviewed their controls over a period of time, not just a snapshot. Type I is not equivalent.
  • What’s your incident response plan? It should include a timeline for notifying customers. Hesitation means they don’t have one.
  • What’s your data retention policy after contract termination? Some vendors keep customer data indefinitely because it feeds their analytics or trains their models.
  • Any security incidents in the last 24 months? A vendor who says no with zero hesitation is either lying or not looking hard enough.

A surprising number of businesses rely entirely on their vendors to proactively flag a breach. That’s roughly equivalent to expecting a burglar to call you when they’ve broken in. Build your own visibility instead of outsourcing that responsibility to the people who benefit most from you not looking closely.

Small businesses are disproportionately targeted because attackers know the security hygiene is inconsistent. The vendor who tells you “we’re too small to be a target” hasn’t thought about it seriously. You are the target. Their weak security is the entry point.

06The 90-Minute Quarterly Check That Keeps You Off the Incident Report

An audit you run once is a snapshot. An audit you run every quarter is a posture. New apps get connected constantly: by you, by whoever manages your tools, by the one person who signs up for things on behalf of the company and doesn’t tell anyone. By the time you remember to check, there are six new integrations you didn’t explicitly approve and one of them has full mailbox access.

  • Pull the connected app list from every core platform (Google, Microsoft, Stripe, your CRM, your automation tools)
  • Flag anything connected in the last 90 days that you didn’t explicitly approve
  • Revoke access for anything you’ve stopped using
  • Check for former employee accounts still active in vendor tools — one of the most consistently overlooked attack surfaces in small teams
  • Review permission scopes on your five highest-access tools and ask whether that scope is still appropriate
  • Verify that your two or three most sensitive vendors have been reviewed in the last 12 months

The whole thing takes 90 minutes if you did it last quarter. Two to three hours if you didn’t. Assign it to one person. Put it on the calendar. “Someone will get to it” is the same as “nobody will get to it.”

Before you connect anything new, the question isn’t “does this seem useful?” The question is “what does this actually need access to, and is that worth it?” A tool that connects to your email, your CRM, and your calendar to do something you could do in a spreadsheet in 20 minutes is probably not worth it.

07The Breach Nobody Sees Coming Is Already in Your Integrations List

The goal isn’t a locked-down stack with zero integrations. Integrations are useful. Some of them are load-bearing parts of how your business runs. The goal is knowing what you’ve actually invited in and making a deliberate choice about the risk, rather than discovering it during an incident.

Small businesses that suffer a major breach often don’t recover — not because the attack was sophisticated, but because the damage to customer trust, the legal exposure, and the operational disruption compound faster than a small team can absorb. It doesn’t require a nation-state actor. It requires one overlooked integration, one vendor with weak security, one OAuth token sitting dormant on a forgotten app that still has full mailbox access.

Block an afternoon, pull the list, and find out what’s actually in there. You’ll probably find three things that shouldn’t be. That’s three fewer open doors than you had this morning, and you didn’t hire anyone or buy anything to close them.

You’re going to finish reading this and still not do it this week. Put it on the calendar for next Tuesday instead of deciding right now. The apps will still be connected. They’re not going anywhere.

Frequently asked questions
What’s the fastest way to see every app connected to my Google account?Go to myaccount.google.com, click Security, then scroll to “Third-party apps with account access.” You’ll see every app that’s been granted OAuth access, including ones installed by other users in your org if you’re an admin. Filter by access level to find the high-permission ones first.
Does revoking an app’s access delete my data from their servers?No. Revoking OAuth access stops the app from accessing your systems going forward. Any data already copied to the vendor’s servers stays there unless you separately request deletion under whatever data retention policy they have. Always ask about data retention before you sign up, not after.
What’s SOC 2 and do I actually need to ask vendors for it?SOC 2 is a third-party audit standard that verifies a vendor’s security controls. Type II is the more rigorous version, covering controls over a period of time rather than a single point in time. For any vendor handling customer data, payment information, or email, yes: ask for it. A vendor that can’t produce one is a vendor worth reconsidering.
How do I handle apps that former employees connected?When someone leaves, pull their connected app list from Google and Microsoft before you deprovision their account. Any app they connected personally may have organization-wide access depending on permission scopes. Revoke those before closing the account. After the fact, the connected apps audit will surface any that slipped through.
How often should a small business actually run this audit?Quarterly is the right cadence for most small teams. More often than that and it becomes noise. Less often and you’ll consistently miss newly connected apps and dormant integrations. Set a calendar event, assign one owner, and block 90 minutes. That’s the whole system.