For a small business, SaaS security comes down to three things: knowing which cloud apps hold your customer data, knowing who and what can log into them, and having someone check that list on a schedule. The education breach below didn't start with malware on a PC. Instructure says the unauthorized actor exploited an issue related to its Free-For-Teacher accounts. Your CRM, client portal, scheduling tool and file-sharing app can be attacked the same way. The fix starts with ownership and housekeeping, not new hardware.
Two breaches, and neither started with malware on a laptop
Canvas: a free tier was the way in
Instructure detected unauthorized activity in Canvas on April 29. It revoked the intruder's access and started an investigation. When a vendor confirms a breach, read its notice for which user data was involved, and assume names, email addresses, and messages could be exposed until you hear otherwise. It also said it had found no evidence that passwords, dates of birth, government identifiers or financial information were involved. The ShinyHunters extortion gang claimed responsibility.
Then things got worse. On May 7, Instructure identified more unauthorized activity tied to the same incident. ShinyHunters defaced about 330 Canvas school login portals, also exploiting the same Free-for-Teacher vulnerability, and that caused the ed-tech firm to take Canvas offline and into maintenance mode.
The timing made it hurt more. According to OPB, Canvas went offline after a data breach, leaving students and faculty at thousands of U.S. colleges and K-12 schools without access to course materials and communications during finals period. OPB's reporting notes that thirty million users rely on Canvas, according to its parent company, Instructure. According to OPB, several schools affected by the breach postponed or outright scrapped some final exams, and the University of Illinois postponed all final exams and assignments scheduled through Sunday.
The size of the theft is still the attackers' word. ShinyHunters claims it took 3.65 TB of data, including about 275 million records from about 8,800 schools. Instructure has not confirmed those numbers. Be cautious about any claim that stolen data was destroyed, because a deletion promise from an attacker is hard to verify. When a vendor says certain data was not affected, ask what was checked and how before you rely on that.
7-Eleven: the franchise documents, not the cash registers
The second case is smaller but closer to how a regular business runs. 7-Eleven says that on April 8, 2026, an unauthorized third party got into certain systems it uses to store franchisee documents. ShinyHunters claims it stole more than 600,000 Salesforce records with personal and corporate information, as Security Affairs reports. Treat record counts that attackers claim as unverified until the affected company confirms them. When BleepingComputer asked 7-Eleven to confirm ShinyHunters' claims, a spokesperson did not reply.
Neither story is about a stolen laptop. Both are about data in a cloud app someone else hosts. Security Affairs notes that ShinyHunters has been going after the Salesforce instances of major organizations since mid-2025.
How SaaS data theft works: free tiers, old accounts, broad tokens
You don't need to be a school or a convenience-store chain for this to apply to you. Organizations increasingly rely on cloud providers, managed service providers, SaaS platforms and outsourced payroll systems. Include vendor and third-party risk in your own security reviews, not just your internal systems.
Patch internet-facing systems promptly, because unpatched vulnerabilities give attackers an easy way in. The Canvas case fits that pattern. SaaS data theft usually comes through one of the doors below.
Door 1: the "side" account nobody treats as production
Bitdefender says Free-For-Teacher accounts were production Canvas tenants with lower-friction onboarding. That is the key point. A free, trial or test tier is easy to sign up for, so it gets less scrutiny. It can still sit on the same platform as the real data.
Look for your own versions: a free CRM trial a past employee set up, a "sandbox" booking system with real client names in it, a file portal from one project that never got closed. OWASP warns that without an asset inventory and a retirement plan, organizations end up running unpatched systems that leak sensitive data.
Door 2: people handing over the keys
In incidents spanning early to mid-January 2026, one cluster, UNC6661, pretended to be IT staff and called employees at targeted victim organizations, claiming the company was updating MFA settings. It then sent them to look-alike login pages that captured their credentials and codes. Those fake domains often follow patterns like or .
Once inside, the attackers go after cloud SaaS applications to pull out sensitive data and internal communications they can use for extortion. Google points out that this is not a flaw in the vendors' products. It is social engineering, and it shows why organizations should move to phishing-resistant MFA where possible.
Hypothetical: someone calls your office manager, says they are "from IT" and that the payroll portal is moving to a new MFA app, and asks them to log in at a link that looks like your company name plus "sso." Make a rule now: nobody gives a code or logs in from a link during an unexpected call. They hang up and call back on a number they already have.
Door 3: connected apps and API tokens with too much reach
Every "Connect to Salesforce" or "Sign in with Google" button creates a lasting key. Google's threat intelligence group says a prevalent tactic in UNC6040's operations is deceiving victims into authorizing a malicious connected app to their organization's Salesforce portal. Review which third-party apps hold OAuth tokens to your Salesforce and other SaaS instances, and be ready to revoke them quickly if a vendor is compromised.
The Canvas cleanup shows how far one token's reach can spread. Instructure rotated its privileged API keys, and any third-party tool connected to a Canvas instance by API had to be re-authorized.
Inventory every cloud app holding customer data
You can't protect an app you've forgotten. Start here, before you buy anything.
Build the list
Open a spreadsheet with one row per cloud app. Look in these places:
- Card statements: every recurring software charge, including small ones.
- Your email and office suite's admin console: third-party apps users approved with "Sign in withβ¦"
- The password manager: every saved login under a work email.
- Each team lead: "What do you log into to do your job?"
- Free sign-ups: search email for "welcome to," "verify your account" and "your trial."
Record what matters for each app
OWASP's API guidance recommends documenting each system's environment (production, staging, test, development), who should have network access to it, and its version. For a small office we'd simplify that to these columns:
| Column | What to write | Why it matters |
|---|---|---|
| App and tier | "HubSpot β free," "Clio β paid" | Free and trial tiers get forgotten |
| Data inside | Client names, SSNs, medical notes, card data | Tells you what a breach would cost you |
| Owner | One named person | Someone has to review it |
| Admins | Every admin login | Admins can export everything |
| Connected apps / tokens | Zapier, QuickBooks sync, marketing tools | Each one is a back door |
| MFA on? | Yes / No / Phishing-resistant | Passwords alone are no longer enough |
| Last reviewed | Date | If it's blank, it's overdue |
Retire what you don't use
Export what you need, delete the data inside the app, then close the account. Don't just stop paying; many vendors keep a free tier running with the data still in it.
Token and admin-account hygiene: rotate, scope, remove
Watch tokens and admin accounts closely; they tend to drift. GitHub's documentation lays out the principles in plain terms, and they apply to almost any app:
- Scope it down. GitHub says to choose the minimal permissions necessary for your needs, and recommends fine-grained personal access tokens instead of classic tokens whenever possible. Give a reporting tool that only reads invoices read-only access, not the power to delete clients.
- Delete what you don't need. GitHub says to delete a token once it's no longer needed. GitHub also removes personal access tokens automatically if they haven't been used in a year. Don't count on your other tools doing that for you; put token cleanup on your own calendar.
- Deny by default. OWASP advises that access should be denied by default, with every function granted explicitly to specific roles. Otherwise, attackers can reach functions they shouldn't.
- Rotate after any incident. After the Canvas breach, Bitdefender advised removing and re-adding integrations with fresh API credentials, and rotating any locally held OAuth tokens, LTI secrets or API keys that touched Canvas between 30 April and 7 May 2026. Google gave similar advice after the Drift incident: revoke and rotate the API keys, credentials and tokens tied to the affected integrations.
Admin accounts and MFA
CISA says strong passwords alone are no longer enough to keep accounts safe. MFA adds protection by requiring two or more ways to prove who you are. Google's guidance adds that MFA should be robustly implemented across the organization, and users should be educated on MFA fatigue tactics and social engineering attempts.
Our advice for a small office: keep admins to two people per app, give them app-based or hardware-key MFA rather than text codes, and when someone leaves, remove them from every app on the inventory the same day.
If [your business runs on Microsoft 365 or Google](https://www.cisa.gov/resources-tools/services/secure-cloud-business-applications-scuba-project) Workspace, the Secure Cloud Business Applications (SCuBA) project provides secure configuration baselines for both, and all organizations can use SCuBA to strengthen SaaS security. Don't let the government framing put you off; it's a solid starting point for a clinic or law office too.
Testing your own SaaS exposure before someone else does
A worked example
Hypothetical: a 15-person accounting office in the Inland Empire runs a paid practice-management system, Microsoft 365, a client upload portal and a free e-signature account a former bookkeeper opened. When they build the inventory, they find the e-signature account still has two years of signed engagement letters with client SSNs in it, no MFA, and the former bookkeeper's login still active. The client portal has an API key connected to a marketing tool that was cancelled last year. None of that would show up in an antivirus scan of their laptops.
Fixing it takes an afternoon. The harder part is finding everything else like it, and repeating the check after every new hire, new tool and departure.
What a SaaS exposure test looks at
When we run this kind of review, we check:
- Forgotten tenants and tiers. Free, trial and test accounts under your domain or brand name.
- Look-alike domains. Registrations that copy your company name plus words like "sso" or "internal," a common pattern for credential harvesting domains.
- Token reach. What each connected app and API key can actually read, write or export, compared with what it needs.
- Stale identities. Former staff, shared logins and admin accounts without phishing-resistant MFA.
- Exposed portals. Client upload links, public file shares and login pages reachable from the internet.
- A help-desk call test, if you approve it in writing: could a fake support call talk someone into reading out a code?
Our pentesting automation service, Script Tiger, is built for this work: it runs the repeatable checks on a schedule, not as a one-off. If you want the inventory and token reviews built into your daily systems, our custom software development team can wire alerts into the tools you already use. For a sense of how we build security tooling, see our Mal-Mon case study.
Pitfalls we see
- "The vendor handles security." The vendor secures the platform; who has access, which apps are connected and what data you put in are on you.
- Rotating passwords but not tokens. A changed password doesn't revoke a connected app's OAuth token.
- Skipping the inventory. If an extortion note arrives, the inventory is how you know which app it came from and what was in it.
Your SaaS security checklist
- [ ] One spreadsheet listing every cloud app, its tier and the customer data inside it
- [ ] A named owner for each app
- [ ] Free, trial and test accounts closed or cleaned of real data
- [ ] Every connected app and API token reviewed, scoped down or revoked
- [ ] No more than two admins per app, all using app-based or hardware-key MFA
- [ ] Offboarding covers every app on the list, the same day
- [ ] A rule for staff: never give out a code or log in from a link during an unexpected "IT" call
- [ ] A quarterly review date on the calendar
- [ ] A yearly (or automated) external test of your SaaS exposure
What we'd do next
If you run a clinic, law or accounting office, agency or restaurant group anywhere in Southern California, start with the inventory now. It's worth doing even if you think you know every account. If you want a second set of eyes, or you'd rather have the checks run automatically, book a Free Automation Audit. We'll look at where your customer data lives in the cloud, tell you plainly what we find, and recommend what's worth fixing first.
Sources
- Bitdefender β Technical Advisory: ShinyHunters Breach of Instructure Canvas LMS (May 8, 2026)
- CISA β Require Multifactor Authentication (May 26, 2026)
- CISA β Secure Cloud Business Applications (SCuBA) Project (September 1, 2025)
- GitHub Docs β Managing your personal access tokens (May 26, 2026)
- Google Cloud (Google Threat Intelligence Group) β Voice phishing data extortion campaign targeting Salesforce (June 4, 2025)
- Google Cloud (Google Threat Intelligence Group) β Widespread data theft targets Salesforce instances via Salesloft Drift (August 26, 2025)
- Google Cloud Threat Intelligence β ShinyHunters-branded SaaS data theft expansion (January 30, 2026)
- Instructure β Security Incident Update (May 8, 2026)
- OWASP β API9:2023 Improper Inventory Management (June 5, 2023)
- OWASP β API5:2023 Broken Function Level Authorization (June 5, 2023)
- BleepingComputer β Instructure confirms data breach, ShinyHunters claims attack (May 3, 2026)
- BleepingComputer β Instructure confirms data breach, ShinyHunters claims attack (May 3, 2026)
- BleepingComputer β 7-Eleven data breach exposes personal information of 185,000 people (May 26, 2026)
- Help Net Security β Lessons for organizations from the Verizon 2026 Data Breach Investigations Report (May 25, 2026)
- TechCrunch β Hackers deface school login pages after claiming another Instructure hack (May 7, 2026)
- The Register β Double Canvas breach acknowledged as ShinyHunters sets new pay-or-leak deadline (May 11, 2026)
- Bitdefender β Technical Advisory: ShinyHunters Breach of Instructure Canvas LMS (May 8, 2026)
- OPB β Canvas is back online, but questions β and final exam disruptions β linger (May 8, 2026)
- Security Affairs β ShinyHunters hack 7-Eleven: franchisee data and Salesforce records exposed (May 18, 2026)
- TechTarget β Verizon 2026 DBIR: 6 key takeaways for CISOs (May 22, 2026)