SSPM from the buyer's side: what Snowflake and the Salesforce OAuth thefts teach, free checks in your top five SaaS apps, and an honest SSPM vs CASB comparison.

SSPM (SaaS Security Posture Management) is a category of tool that connects to business applications such as Microsoft 365, Google Workspace, Salesforce, Slack and GitHub, reads their security settings, user permissions and connected third-party apps, and flags anything that departs from an approved baseline. It finds the risky setting. It does not block attacks in progress.
Every few weeks we get the same call. A 60 person SaaS company has just received an enterprise security questionnaire with a line asking how it "continuously monitors SaaS configuration," and a vendor has already sent a quote. The founder wants to know whether to sign. Our answer is almost always "not yet," and this post explains why, what to do first, and the point at which buying a tool genuinely makes sense.
Across our assessments, the SaaS findings that matter fall into three buckets, and the two best-known recent incidents map onto them cleanly.
In mid-2024 a financially motivated group Mandiant tracks as UNC5537 logged into Snowflake customer accounts using credentials stolen by infostealer malware, some dating back to 2020. Mandiant and Snowflake notified about 165 potentially exposed organizations. Mandiant found that at least 79.7% of the accounts used had prior credential exposure, and named three root causes: no MFA on the affected accounts, credentials that had not been rotated for years, and no network allow lists. Snowflake itself was not breached. CISA issued an alert on 3 June 2024, and Snowflake has since moved to block single-factor password sign-ins.
Every one of those three root causes is a setting.
In 2025 the attack shifted from passwords to tokens. An FBI FLASH alert of 12 September 2025 described two groups targeting Salesforce. One, UNC6040, phoned staff posing as IT support and talked them into approving a malicious connected app, often a modified Data Loader, which sidestepped MFA and bulk-exported records. The other, UNC6395, used stolen OAuth tokens from the Salesloft Drift chatbot integration to pull data from customers' Salesforce instances until Salesloft and Salesforce revoked all Drift tokens on 20 August 2025.
Your MFA can be perfect and a single "Allow" click, or an integration nobody remembers installing, still opens the door.
The third bucket is less dramatic and far more common: former contractors still active in Slack, a dozen people with global admin, Google Drive or SharePoint links set to "anyone with the link," a GitHub organization where anyone can install apps. The Verizon 2026 DBIR puts credential abuse in 39% of breaches and third-party involvement in 48%.
Before you look at any tool, open the admin console of the five apps that hold your customer data, source code or money. Every check below is built into products you already pay for. If you have not done these, an SSPM tool will only hand you a longer list of the same findings.
App | Built-in place to look | What to confirm |
|---|---|---|
Microsoft 365 / Entra ID | Secure Score; Entra ID enterprise app consent settings | MFA enforced for every user, legacy authentication off, users cannot consent to new apps without admin approval, two to four global admins at most |
Google Workspace | Security health page; API controls and app access control | 2-Step Verification enforced, third-party app access restricted to an allow list, external Drive sharing defaulted to off or warning |
Salesforce | Health Check in Setup; Connected Apps OAuth Usage | Session and password settings at or above baseline, every connected app has a known owner, unused apps and integration users removed, login IP ranges set |
Slack | Workspace settings for app management and guest access | App installs require approval, guests expire, public channel sharing and Slack Connect limited to named partners |
GitHub | Organization settings for OAuth app access and member privileges | OAuth app access restrictions on, 2FA required for members, base permissions read-only, outside collaborators reviewed |
For Microsoft 365 and Google Workspace there is a better yardstick than vendor defaults. CISA's Secure Cloud Business Applications (SCuBA) project publishes secure configuration baselines for both suites, plus free open-source assessment tools (ScubaGear for Microsoft 365 and ScubaGoggles for Google Workspace) that produce a pass/fail report. Under Binding Operational Directive 25-01, issued in December 2024, US federal civilian agencies must apply the mandatory SCuBA policies, and CISA strongly recommends that every organization adopt them. It is the closest thing to a neutral, public SaaS baseline, and Canadian companies can use it just as easily.
Buyers often treat these as interchangeable. They are not. Some vendors will dispute our view.
Approach | What it is good at | Where it falls short | Our view for a 30 to 200 person company |
|---|---|---|---|
Native admin consoles | Free and authoritative | One app at a time, no history | Mandatory first step. Most risk reduction happens here. |
Quarterly manual review | Cheap, forces a human to ask who has access and why | Misses drift between reviews | Enough for most companies with under 10 critical apps |
SSPM tool | Continuous drift detection, connected-app inventory, evidence on demand | Subscription cost, needs an owner to triage | Worth it at roughly 15+ critical apps, several admins, or a contract demanding continuous monitoring |
CASB | Shows which cloud apps staff use, inline data controls | Weaker at configuration checks, heavier to deploy | Usually overkill at this size. Use SSO plus app approval first. |
One opinion that surprises people: under 100 staff, the most valuable SSPM feature is not configuration scanning. It is the inventory of third-party apps and OAuth grants on your core platforms, exactly the gap the Salesforce campaigns exploited. If a tool is weak there, keep your money. Our shadow AI guide covers the same discovery problem for AI tools.
You do not need an SSPM tool when:
You run fewer than about 10 business-critical SaaS apps and one or two people administer all of them. A baseline per app, a quarterly review and an offboarding checklist cover most of the risk.
You have not yet enforced SSO and MFA, restricted app consent, or defaulted sharing to internal. A tool reporting 300 findings against apps with no baseline gives you a backlog, not a posture.
Nobody owns the findings. An SSPM dashboard nobody triages is a liability in discovery, because it proves you knew.
Your biggest exposure is your own product, not the tools you subscribe to. Start with our DevSecOps guide.
SSPM also does not stop a user socially engineered into approving an app in real time, does not scan files for malware, and does not replace incident response. If a token is stolen today, you need a tested revoke-and-rotate plan, which our small business incident response guide covers.
List every SaaS app holding customer data, code or financials, with a named owner.
Enforce SSO and MFA everywhere it is supported. Rotate any shared or service account passwords older than a year.
Turn off user consent for new third-party apps in Microsoft 365 and Google Workspace, and require app approval in Slack and GitHub.
Run ScubaGear or ScubaGoggles and Salesforce Health Check. Record the results as your baseline.
Review every connected app and OAuth grant. Remove anything ownerless or unused for 90 days. Set login IP ranges on admin and integration accounts.
Write a one-page baseline per app and store it with your governance, risk and compliance documents.
Run your first quarterly access review and time it. If it took under a day, manual is fine for now.
If it took a week, or your app count is heading past 15, or a customer contract requires continuous monitoring, shortlist SSPM tools on connected-app coverage for your specific stack.
Map the controls to your framework so the evidence serves SOC 2 and privacy obligations at the same time.
This matters on both sides of the border. A misconfiguration that exposes personal information can trigger reporting under PIPEDA where there is a real risk of significant harm, a confidentiality incident register entry under Quebec Law 25, and US state breach notification duties. A configuration baseline is part of the safeguards regulators expect, so we treat it as part of data security and privacy work.
No. CSPM (cloud security posture management) checks infrastructure you build on AWS, Azure or Google Cloud: storage buckets, security groups, IAM roles. SSPM checks applications you subscribe to: Microsoft 365, Salesforce, Slack. Many SaaS companies need both.
It helps produce evidence for access and change controls, but SOC 2 does not require a tool. A documented quarterly review with screenshots satisfies most auditors at this size.
For a company with five to ten core apps, the 30-day steps above usually take an experienced admin two to four working days. Our Cybersecurity Baseline Assessment covers the same ground if you would rather have an outside view.
One named person, usually the head of IT or engineering, with executive oversight. If nobody has the time, a virtual CISO can own the baseline and quarterly review; our Crawling tier starts from $2,000 a month. See all options on our pricing page, or book a call and we will tell you honestly whether you need a tool yet.
Our diverse industry experience and expertise in AI, Cybersecurity & Information Risk Management, Data Governance, Privacy and Data Protection Regulatory Compliance is endorsed by leading educational and industry certifications for the quality, value and cost-effective products and services we deliver to our clients.