Insights · Engineering · Sep 14, 2026 · 7 min read
Security tips for small teams in 2026: passkeys, MFA, backups and AI-era phishing
Attackers now write flawless emails, clone voices and automate reconnaissance, which means the old advice to “look for spelling mistakes” is dead. The good news is that the defences that work are cheap and mostly configuration. Seven things to do this month.
Copilot · fine-tuned on your data
Live0.94
F1 score
86ms
Inference
12k/d
Requests
Illustrative product interface — not client data.
LJBy Lovi Joshi·Founder & Digital Strategy Lead·
Two things changed the security picture for small organisations in the last two years. Attackers use AI to write convincing messages, clone voices and automate the boring parts of a break-in. And the defences that actually stop them — passkeys, phishing-resistant multi-factor authentication, tested backups — became cheap and mostly a matter of switching them on. This is the list we work through with clients, in the order that removes the most risk for the least effort.
Key takeaways
- Passkeys and phishing-resistant MFA on email, identity and admin accounts remove the most common way in.
- A password manager for everyone, with shared vaults for team credentials, ends password reuse.
- Backups only count when someone has restored from them this quarter.
- Write a call-back rule for money and access requests; AI voice cloning makes “it sounded like the CEO” meaningless.
- Least privilege and an offboarding checklist close the accounts that attackers find first.
1. Passkeys and phishing-resistant MFA first
Start with the accounts that unlock everything else: email, your identity provider (Microsoft 365 or Google Workspace), your domain registrar, cloud console and banking. Turn on passkeys where they are offered and hardware keys or authenticator apps where they are not. SMS codes are better than nothing and worse than everything else; move away from them for admin accounts. A phished password with a passkey behind it is a near miss instead of an incident.
2. A password manager for everyone
Buy a business password manager, require it, and move shared credentials into shared vaults with access by role. This ends password reuse, gives you an audit trail, and makes offboarding a matter of removing one person from the vaults rather than guessing what they knew.
3. Backups you have actually restored
Every client we ask has backups. Far fewer have restored from them in the last year. Schedule a quarterly restore test of one real system — the website, the CRM export, the shared drive — and time it. Keep one copy that a compromised admin account cannot delete. Our backups and disaster recovery guide has the checklist.
4. A call-back rule for money and access
AI voice cloning and flawless AI-written email mean that “it sounded like them” and “the email looked right” no longer protect you. Write a one-line rule: any request to move money, change bank details, or grant access is confirmed by calling the person back on a number you already have. Print it. Tell suppliers you do it. It costs nothing and it is the single most effective control against business email compromise.
| Step | Effort | Risk it removes |
|---|---|---|
| Passkeys / phishing-resistant MFA on core accounts | An afternoon | Credential phishing, password stuffing |
| Business password manager with shared vaults | A week to roll out | Reuse, sticky notes, unknown shared logins |
| Quarterly restore test | One hour per quarter | Ransomware, accidental deletion, vendor failure |
| Call-back rule for money and access | Ten minutes | Business email compromise, voice-clone fraud |
| Least privilege and offboarding checklist | Half a day, then ongoing | Stale admin accounts, ex-staff access |
| Patch and update cadence | Ongoing, mostly automatic | Known exploits in CMS, plugins, devices |
5. Least privilege and a real offboarding list
Most people do not need admin rights, and most ex-employees still have some. Review who is an admin on each system, reduce it to those who need it, and keep an offboarding checklist that lists every system a person could hold access to: email, drive, CRM, website, social accounts, ad accounts, domain, cloud, password vaults. Run it the day someone leaves.
6. Keep the website and devices patched
For WordPress and other CMS sites, keep core and plugins updated on a schedule, remove plugins you do not use, and put the site behind a web application firewall. For laptops and phones, turn on automatic updates and disk encryption, and use device management if you have more than a handful. See what website maintenance includes.
7. Rules for AI tools and data
Decide what may be pasted into AI assistants, require business tiers with no-training terms, and treat AI-generated links, invoices and attachments with the same suspicion as any other. A short written policy beats an unwritten assumption; we outline one in writing an internal AI policy.
Most small-business breaches are not clever. They are a reused password and an email that looked fine.
None of the steps above requires a security team. They require an afternoon, a decision, and a quarterly reminder. If you want an outside pair of eyes on your accounts, website and processes, our cybersecurity services start with exactly this review.
FAQ
Questions on this topic.
Yes. Microsoft, Google, Apple and most major SaaS tools support them, and they remove the phishing risk that passwords and SMS codes carry. Start with email, identity, domain, cloud and banking accounts, then expand.
With process, not technology: any request to move money, change payment details or grant access is confirmed by calling the requester back on a number you already hold. Write it down, share it with suppliers, and never make exceptions for urgency.
Restore one real system every quarter and time it. A backup that has never been restored is a hope, not a control. Keep at least one copy that a compromised admin account cannot delete.
Often yes, and insurers increasingly require the basics on this list — MFA, backups, patching — before they will write a policy. Doing the list first makes the insurance cheaper and the claim, if it comes, simpler.
Keep reading
More from the studio.
Content tips for the AI-answer era: pages that get cited and still convert
Writing for AI answers and writing for people who buy are not in conflict, but they are not the same job either. Twelve tips for pages…
How to evaluate an AI vendor before you buy: a twelve-question checklist
Every software vendor now says “AI-powered.” Twelve questions separate a product you can rely on from a demo with a subscription attached: what the model does,…
The web stack worth standardising on for 2027: frameworks, hosting and databases
Most of the churn in web tooling has settled. For the next couple of years a small set of frameworks, hosts and databases will cover nearly…
Let’s connect
Want this applied to your business?
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote.
Thanks — we’ll reply within one business day.