Virtue Technology Solutions logo

Cybersecurity

Your Vendors Could Be Your Weakest Security Link

• Virtue Technology Solutions

Most small businesses have spent the last few years getting better at their own security. Multi-factor authentication is on. Staff have been trained. Patching is less chaotic than it was. Then a vendor with a standing account and no MFA becomes the way in, and none of that hardening matters.

This is the part of security that lives outside your building, and it is the part most SMBs have never written down.

Vendor security risk

How a Vendor Becomes the Breach

Nobody sets out to give a vendor dangerous access. It accumulates.

An accountant needs into the finance share, so they get an account. A booking or scheduling tool needs to read your calendar, so it gets an integration token. A vendor's helpdesk installs remote support software that stays installed after the ticket closes. A marketing agency asks for access to your email domain so it can send on your behalf, and that access is never removed.

Each of those is reasonable on its own. Together they mean a dozen outside organisations hold credentials or tokens that reach into your systems, and your security posture is now the weakest of all of them.

The reason attackers like this path is efficiency: compromising one supplier can yield access to every customer that supplier serves. One compromise, many victims, and the victims have no visibility into how it happened.

The Question Worth Asking Every Vendor

Not "are you secure" — every vendor says yes. Ask instead what access they actually hold:

  • Which accounts do they have, and are they named people or a shared login?
  • What can those accounts reach — one folder, or the whole tenant?
  • Is access permanent or does it expire when the project ends?
  • Who at the vendor can use it, and can they tell you when someone did?
  • Can they prove MFA on the accounts that reach you?

If a vendor cannot answer those five, that is your answer. It is not a reason to panic, but it is a reason to scope the access down before something happens.

Least Privilege Applies to Them Too

You already apply this to your own staff: give people what the job needs and nothing more. Vendors deserve exactly the same treatment, and usually get far less scrutiny.

Give them a named account rather than a shared one, so activity traces to a person. Scope it to the specific systems or folders the work requires. Set an end date if the work has one. Remove it the day the contract ends — not "when someone remembers". Turn on logging and check it occasionally, because an account nobody has used in eight months is either unnecessary or already compromised.

For integrations, review which applications have been granted access to your email or file storage. OAuth consent screens are approved in ten seconds and forgotten for years, and they survive password changes.

Put It in the Contract

Security expectations belong in writing before an incident, not in a conversation afterwards.

Reasonable things to ask for: a description of what data they hold and where, a commitment to notify you promptly after a breach affecting your data, evidence of their controls such as a completed security questionnaire or an audit report, disclosure of subcontractors who may touch your data, and confirmation that your data is returned or destroyed when you leave.

If you handle regulated data — patient information, card payments, personal data — the vendor relationship changes your obligations rather than removing them. Data you are responsible for does not stop being your responsibility because a supplier holds it. That is worth a conversation with your compliance obligations in mind before you sign, not after.

What You Can Actually Control

You cannot audit a vendor. You can, however, do four things that materially reduce the risk.

Write the list down. Most SMBs cannot name every third party with access to their systems. Start with a spreadsheet: who, what access, who approved it, when it was last reviewed. The exercise itself usually turns up two or three accounts nobody owns.

Cut the access you do not need. Anything standing that is not actively used should go. This is the cheapest risk reduction available and needs no vendor cooperation at all.

Consolidate. Every additional vendor is another set of credentials and another organisation to trust. Fewer suppliers, with better-scoped access, is easier to govern than a long tail nobody is watching.

Ask annually. Controls decay. The vendor who answered well two years ago may have been acquired, outsourced their support, or quietly dropped the practice they described. A short annual re-check catches that.

Where This Fits

Vendor risk is not a separate programme. It is the same disciplines you already apply — least privilege, MFA, logging, offboarding — pointed outward. The businesses that handle it well are not the ones with the biggest security budgets; they are the ones who know who has access to what.

At Virtue Technology Solutions we help Southern California SMBs get a grip on cybersecurity and managed IT — including the unglamorous work of finding and removing access nobody is using.

Not sure which vendors can reach your systems? Contact Virtue Technology Solutions for a no-pressure consultation.

Need help with your IT strategy?

We help businesses plan, secure, and manage their technology. Reach out for a no-pressure conversation.