Your suppliers are part of your cybersecurity: 10 tips to stop them becoming the way in

17th November 2026, 1:45 pm

Most small businesses have never been the direct target of a cyber-attack. Many are being reached through someone they trust instead: an IT provider, a software plug-in, a carrier, or a supplier’s email account. When Jaguar Land Rover was attacked in 2025, the Cyber Monitoring Centre estimated the cost of that breach at around £1.9bn, and 5,000 UK businesses in its supply chain felt the pain too. Yet only 15% of UK organisations review the cyber risk of their immediate suppliers according to the latest Government UK Cyber Security Breaches Report. Our latest supply chain cyber security white paper “Why trust is not a supply chain control” has just been published, from it we share our ten tips to help you close the most common gaps.

1. Know the five suppliers you couldn’t trade without
Start with a list, not a tool. Write down the five suppliers, platforms or service providers that would stop you trading if they went offline tomorrow. For most SMEs that’s your IT provider, the accounting or payroll system, the e-commerce, website or booking platform, your bank, and a key logistics or materials supplier.
For each one, note what they can access (your systems, your data, your money) and who you’d call if something went wrong. This takes an afternoon. It’s also the list every other tip in this article builds on, so it’s worth doing properly. Most businesses that are hurt by a supplier’s breach had never written this list down, so they spent the first day of a cyber incident working out who was affected.

2. Ask for evidence, not just a certificate
A supplier’s security certificate tells you how they were assessed last year, its a point in time. It doesn’t tell you whether they had an issue this morning.
You don’t need a huge security questionnaire. For your top five, ask them three things.
1. Will you tell us within 24 hours if you have a security incident that could affect us?
2. Who is our contact if that happens?
3. What has changed in your security since your last certificate?
Put the first one in your contract or terms when they’re next renewed.
The answers matter less than how they answer. A supplier who responds quickly and plainly is usually one who has thought about it. One who goes quiet for three weeks is telling you something too.

3. Find out how your IT provider resets a password
Many attacks now start with a phone call, not a piece of code. A call to a help desk, pretending to be a member of your staff, they sound convincing and ask for a password reset. In 2025 a third-party help desk was at the centre of the attack on M&S, which showed just how much damage one successful call can do. That call may not now even be human as AI voice cloning is more sophisticated than ever and fraudsters need only 3 seconds to produce a realistic clip.
If an IT provider runs your help desk, ask them a simple question: if someone calls claiming to be me, how do you check if it’s really me?
Proving identity can’t be left to names, dates of birth, and other information that can be found on the web. Better processes include calling back on a number already on file or confirming through an app the real person has on their phone. Agree the process with them and write it down.

4. Make sure one email can’t change who you pay
Invoice fraud is one of the most common ways small businesses lose money. A supplier’s email account is hacked, or a near-identical address is set up, and a genuine-looking message arrives: “We’ve changed banks, please update our details.”
The fix is a process, not better spotting. Make it a rule that any change to a supplier’s bank details is confirmed by phone, using a number you already hold, never one in the email. Where you can, have a second person approve the change before any payment goes out. Tell your suppliers you work this way. It means a fraudster has to beat two people and a phone call, not one inbox.

5. Turn on stronger sign-in everywhere a supplier connects
Multi-factor authentication, or MFA, means a password alone isn’t enough to log in. You also need a second proof, usually a code or a prompt on your phone. It stops the large majority of attacks that rely on stolen passwords.
Most SMEs now use MFA on email. Fewer use it on supplier portals, banking platforms, website admin accounts and the remote access tools their IT provider uses to reach their systems. Those are exactly the doors attackers will try. Go through your supplier list and switch MFA on for every account that touches them. Where you have a choice, an authenticator app is stronger than a text message.

6. Know what’s plugged into your website and systems
Most businesses now run on connected software. Your website talks to your payment provider, your stock system talks to your courier, your accounts package talks to your bank. Those connections are often called APIs, which simply means a way for one piece of software to request information from another.
Each connection is a doorway. Website plug-ins and add-ons are a common route, especially old ones nobody remembers installing. Once a year, ask whoever runs your website and systems for a list of every plug-in and connection. Remove anything you no longer use, make sure the rest are kept up to date, and ask what each one can see. If nobody can produce the list, that’s your first job.

7. Get AI-built tools checked before they touch customer data
AI assistants now make it possible to build a customer portal, a booking form or an internal tool in an afternoon, sometimes without writing any code. This is often called “vibe coding”: describing what you want and accepting what the AI produces.
It’s genuinely useful, and the results often work well in testing. The problem is that independent studies keep finding security flaws in a large share of AI-generated code, most often in who is allowed to see what. A portal can look fine while letting one customer view another customer’s orders by changing a number in the web address.
If anyone in your business, or a freelancer you use, has built something this way that handles customer or payment data, have someone with security experience review it. An AI security check alone isn’t enough.

8. Keep passwords and keys out of shared places
Passwords end up in some surprising places: spreadsheets on a shared drive, sticky notes, team chat threads, emails to a new starter. The same goes for the “keys” that let software connect to other software, which often sit in website settings or code that a developer has shared.
Use a password manager for the business, so passwords are stored securely and shared only with the people who need them. When someone leaves, or a supplier relationship ends, change the passwords they had access to immediately, not next quarter. If a password or key has ever been posted somewhere it shouldn’t have been, assume it’s been seen and change it. Research by GitGuardian found most leaked keys were still working years later.

9. Keep a person in charge of anything AI can do with money
More SMEs are using AI tools that don’t just answer questions but take actions: processing invoices, replying to customers, issuing refunds, booking deliveries. That can save real time.
But an AI tool that reads emails and documents can be tricked by instructions hidden inside them. A fake invoice could include text telling the tool to update a bank account. So keep a simple rule: any action that moves money, changes bank details, changes a delivery address or issues a refund needs a person to approve it. Give each AI tool access only to what it needs for its job and know who in the business switched it on. The technology can do the legwork but a person should make decisions that can’t be undone.

10. Rehearse a bad day with your key suppliers
Most businesses only find out how they’d cope with an incident when it happens. A tabletop exercise is a way to find out first. It’s a structured conversation where you walk through a realistic scenario, for example “our IT provider has been hacked and our systems are down”, and talk through who does what, who you call and what you tell customers.
It takes an hour or two around a table, and nothing gets switched off. The gaps it shows up are usually simple: nobody knows where the backup phone numbers are, or two people both think the other one calls the insurer. If you can, invite your most important supplier to take part. Then write down what you’d do differently and fix those things first.

Want to go deeper? These tips are drawn from CloudGuard’s white paper, Why Trust Is Not a Supply Chain Control, which includes ten questions to take to your next board meeting and a 90-day plan. Download it free here: https://cloudguard.ai/resources/supply-chain-white-paper/?utm_source=pro-manchester&utm_medium=referral&utm_campaign=supply-chain-white-paper-2026

Rachel Mcelroy, Head of Marketing, CloudGuard. CloudGuard is a Manchester-based cyber security business and Microsoft Security specialist.

Next Article

Ten Tips for Safe, Secure and Compliant AI Adoption

AI is moving incredibly quickly … AI is moving incredibly quickly and, for SMEs, the opportunity is significant. Used well, […]
Read Article