Skip to content

Blog

SaaS security for small businesses

SaaS security for a small business is five habits: MFA, removing access on time, few admins, controlled integrations and safe sharing. Here's how.

· 9 min read

SaaS security, for a small business, is five habits: strong sign-in on every account, removing access the day it is no longer needed, few admins, control over the apps and tokens connected to your tools, and sensible sharing settings. Your vendors secure their servers. Who can get into your account on those servers, and what they can do there, is your side of the deal.

That split matters, because the incidents a small company can actually prevent are rarely about a vendor being hacked. They are a phished password, an ex-employee who still has a login, an admin role nobody needed, or a link set to "anyone can view". Below, the practices that prevent those, in order of what they prevent, with a checklist at the end.

Who secures what

When you use a SaaS tool, the vendor runs the infrastructure, patches the software and encrypts the data centers. You control four things. Identities: who has an account, how they sign in, and when that account goes away. Permissions: which role each account has. Configuration: sharing defaults, integrations, retention and security settings. And data: what people put in, and who they share it with.

A vendor's security certifications cover their part only. Nothing they do protects you from giving admin to the wrong person.

1. Account security: MFA

What it prevents: someone signing in with a stolen or guessed password.

Multi-factor authentication (MFA) means a login needs something besides the password: a code from an app, a push prompt, or a security key. The US Cybersecurity and Infrastructure Security Agency puts it plainly on its MFA page: "any MFA is better than no MFA." The same page calls FIDO/WebAuthn, the standard behind security keys and passkeys, the only widely available phishing-resistant method, because it refuses to work on a fake login page.

The order matters. Start with your directory. If everyone signs in to other tools with Google or Microsoft, MFA there protects the most; the Google Workspace security checklist shows how to enforce it. Then cover every admin account, in every tool, admins first and then everyone with access to customer data or money. Then turn it on in every tool that offers it, for the tools people log into with a password.

Is MFA enough? No. It stops the stolen-password attack. It does nothing about people who should not have access at all, such as leavers, contractors whose work ended, or admins who never needed to be. That is the next four sections. SSO vs MFA covers how MFA and single sign-on fit together.

2. SaaS access control: who has it, and removing it

What it prevents: former employees, contractors and forgotten accounts keeping a way in.

Every account that should not exist is a working login nobody is watching. Accounts usually outlive their owners for one of three reasons: the tool was not on the offboarding list, the person signed up with a password rather than through Google, or removing them was nobody's job.

The fix has three parts. First, know who has what: for each tool, a list of accounts matched to people in your directory, where anything that matches nobody is a question to answer. Second, remove on the day. When someone leaves, that means every tool, not only email. Suspending a Google account stops new Google sign-ins but does not delete the person's accounts elsewhere, so the employee offboarding checklist walks through the rest. Third, check regularly: a quarterly user access review catches what offboarding missed.

This is what people mean by "SaaS access control": not the login screen, but the list behind it.

Contractors and guests deserve a sentence of their own. They are often invited straight into a tool, never appear in your directory, and have no last day that anyone records. Give every contractor account an end date when you create it, and treat a guest who matches nobody in your directory the same as any other unknown account. Contractor access management covers the details.

3. Admin rights

What it prevents: one compromised or careless account changing everything.

An admin can export all data, invite new users, change security settings, connect integrations and remove other admins. Every extra admin is extra blast radius. Two named admins per important tool is enough: one primary, one backup. Everyone else gets the lowest role that does their job. The principle of least privilege explains how to cut admin access in a small company without slowing anyone down.

Also check who owns the account and who receives billing and security emails. If it is a leaver's address, you may not hear about problems at all.

4. Integrations and API tokens

What it prevents: access that bypasses your people entirely.

Integrations are the quiet risk. When someone connects a third-party app with "Sign in with Google" and approves access to their mail or files, or creates an API token in a tool, that access does not need MFA again, does not show up as a person, and usually survives the person leaving.

Review connected apps. In Google Workspace, the API controls page lists apps your users have authorized and what each one requests; the post on finding shadow IT shows how to read it.

Limit what unreviewed apps can do. Google lets admins mark apps as trusted, limited or blocked, and restrict apps you have not reviewed.

Give tokens owners and narrow scopes. Read-only where possible. Tie them to a role or service account, not to one employee's personal account, where the tool allows it.

Revoke on departure. Tokens and app connections created by leavers belong in offboarding, right after their accounts.

5. Data sharing settings

What it prevents: data leaving through the front door.

A document shared with "anyone with the link" leaks as surely as a breach, and it takes one click. Look at each tool's defaults in this order. Link sharing defaults come first: new files and documents should be private, or company-only, until someone chooses otherwise. Next, external sharing: warn on, or restrict, sharing outside your domain for tools that hold customer data. Then guest access: guests in chat, documents and project tools should be time-limited and reviewed. Last, public pages. Many tools can publish to the web, and you should know which documents are public.

What SSPM is

SaaS security posture management (SSPM) is a category of products that connect to your SaaS tools' APIs and check their settings against a baseline: is MFA enforced, are there too many admins, is public sharing on, which third-party apps are connected. They alert when something drifts. Some also cover identities and data.

For a large company with hundreds of tools, that is the only way to keep up. For a company of 5 to 50 people, the products are usually more than the problem needs, and many only connect to tools on plans with admin APIs. The checklist below is the manual version: run it every quarter and you have most of what SSPM would tell you.

Common mistakes

Treating SSO as the whole answer. Single sign-on controls how people log in to connected tools. It does not remove the accounts, catch password logins that were set up before SSO, or touch tools on plans without it. Most tools also put it on their most expensive plan, which is the SSO tax.

Securing logins and forgetting tokens. A leaver whose accounts are all removed can still have an API token running a script, or an app with access to the shared drive.

One admin per tool. It feels tidy until that person leaves or loses their phone, and nobody can get in to remove them.

Checking once. Every setting above drifts. People get promoted to admin for a task and stay admin; a sharing default gets loosened for one project. The quarterly pass is what keeps the first pass true.

A 5-person company and a 50-person company

At five people, the whole job fits in an afternoon. Enforce MFA in Google Workspace, put security keys on the two super admins, check that the payment provider, bank portal and domain registrar are owned by a company address, and look at the connected apps list once. Most of the risk sits in those few accounts.

At fifty people, the list of tools is too long to hold in your head. The same five habits apply, but each needs an owner: someone who keeps the tool list, someone who runs offboarding, and someone who signs off the quarterly review. Write down who. A practice without an owner stops the first busy month.

The checklist

Run this every quarter. Each line is a question you should be able to answer yes to.

MFA is enforced in your directory. Google Workspace or Microsoft 365, for everyone, with no exceptions you cannot name.

Every admin account has MFA. In every tool, with security keys or passkeys on the most important ones.

There is one list of tools, each with a named owner. If a tool has no owner, it has no one to answer the next question.

Each tool's accounts match current people. Unknown accounts are explained or removed.

Leavers lost every account on their last day. Check last quarter's leavers against each tool, not just Google.

Each important tool has two named admins. Everyone else is on the lowest role that works.

Owner and billing contacts belong to current people. Not to a leaver's address.

Connected third-party apps were reviewed. Risky scopes are restricted or the app is blocked.

API tokens have owners and narrow scopes. Tokens created by leavers are revoked.

Link sharing defaults are private or company-only. External sharing has been reviewed in the tools that hold customer data.

Shared logins live in a password manager with an owner. The post on shared accounts covers how to run them.

The access review is recorded. Who ran it, when, and what changed.

What should a small business do first? Enforce MFA on your directory and admin accounts, then make sure leavers lose every account. Those two close the widest doors for the least effort. If you only have an hour this week, spend it there.

Where SmashSSO fits

SmashSSO handles section 2 and part of section 3. It reads your people from Google Workspace with read-only access, reads who has an account in each tool and with which role, and shows it in one access grid matched by email. Unknown accounts are flagged, admins are visible at a glance, and anyone suspended in Google Workspace shows every tool where they still have access. Removals and role changes run from there, through a tool's member API where you have added a token or an agent in your own Chrome otherwise, with an audit log of every change.

It does not enforce MFA, check sharing settings or review OAuth apps, and it is not SSO. It needs Google Workspace as your directory, and it has no SOC 2 report of its own (security). It costs a flat fee from $199 a month, billed annually (pricing).

FAQ

What is SaaS security?
It is securing your side of the cloud tools you use: who has accounts, how they sign in, what roles they hold, which apps and tokens are connected, and how data is shared. The vendor secures its infrastructure; account access and configuration are yours to manage.
What is SSPM?
SaaS security posture management is a category of products that connect to your SaaS tools' APIs and check their settings against a baseline, such as MFA enforcement, admin counts, public sharing and connected apps, and alert on drift. For a small company, a quarterly manual checklist covers much of the same ground.
Is MFA enough?
No. MFA stops someone signing in with a stolen password, but it does nothing about accounts that should not exist, such as leavers and finished contractors, or about admin roles nobody needed. Access removal, few admins, integration control and sharing settings cover the rest.
What should a small business do first?
Enforce MFA in your directory and on every admin account, then make sure people who leave lose access to every tool, not just email. Those two steps close the widest doors for the least effort.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google