Third-party risk management for SMEs: a step-by-step guide
Your IT service provider has remote access to your servers, your accounting runs in the cloud and your customer data sits in a third-party CRM. Every one of these suppliers extends your attack surface. This article shows how an SME can use lean third-party risk management to record, assess and regularly review supplier risk, and what to do when something goes wrong at a supplier.
- Suppliers with access to your data or systems are part of your attack surface. Responsibility for your data stays with you.
- A supplier register with criticality, data access and system access is the foundation. Without a list there is no prioritisation.
- If a supplier processes personal data on your behalf, the Swiss FADP requires a contractual basis and assurance that the supplier can guarantee data security.
- Plan for the failure of critical suppliers in advance: an immediate measure, contacts, your own backups and a way to revoke access quickly.
Why suppliers are part of your attack surface
An attacker does not need to get through your firewall if they can come in through a supplier. The IT service provider with remote maintenance access, the agency with access to your website backend, the SaaS provider holding your customer data: every access you grant to a third party is access you do not control yourself.
This matters especially for SMEs. 99.7 per cent of Swiss companies are SMEs (FSO, STATENT 2023), and a company without its own IT department outsources operations, software and hosting. Part of your security moves to the supplier with it. Responsibility does not: towards customers, employees and authorities, you remain accountable for your data.
Supplier risk typically takes three forms:
- Data leakage: a supplier with access to personal data or trade secrets is compromised.
- Intrusion via access: a service provider's remote maintenance or admin accounts are misused to get into your network.
- Outage: a cloud service is unavailable, a provider shuts down or goes bankrupt, and your processes come to a halt.
The Swiss ICT Minimum Standard devotes a separate category to supply chain risk management (ID.SC). The article ICT Minimum Standard for SMEs explains how the standard is structured.
The supplier register as the foundation
Without a complete list there is no prioritisation. So start with a supplier register. Good sources are the accounts payable list, company credit card statements (that is where SaaS subscriptions show up) and a short survey of your departments.
For each supplier, the register should contain at least:
- name, category (for example cloud and SaaS, IT infrastructure, software development, data processing, telecommunications) and status
- country of registration or data storage
- contact person for the contract and for security incidents
- scope of services in one or two sentences
- Data access: does the supplier see company or personal data?
- System access: does it have accounts, VPN or remote maintenance access to your systems?
If systems in your asset register depend on a supplier, record that dependency. This lets you see later which systems and services are affected when a provider fails.
In CyberTell Third-Party Management you add suppliers one by one or via CSV import. The list shows status, risk level, system access and overdue backup tests at a glance.
Assessing supplier risk: criticality, access and location
Not every supplier deserves the same effort. The assessment answers two questions: what happens if something goes wrong at this supplier? And how likely is that?
For impact, three criteria matter most:
- Data access: which data does the supplier see, and does it include sensitive personal data such as health data?
- System access: can the supplier change systems, for example with admin rights or remote maintenance?
- Dependency: how long can you work without this supplier, and how quickly could you replace it?
For likelihood, evidence such as security policies, certificates or audit reports helps, along with the quality of the contracts and the location. With providers in countries under sanctions or embargoes, the risk of business interruption also rises.
This gives you a criticality level. The review intervals in the table are a suggestion to adapt to your situation.
| Level | Characteristics | Example | Review |
|---|---|---|---|
| Critical | outage stops the core business, or admin access to central systems | IT service provider with remote maintenance, cloud ERP | annually and with every contract change |
| High | access to personal data or systems, outage painful but bridgeable | payroll provider, CRM provider | annually |
| Medium | limited data access, replacement possible within weeks | print shop with address data for a mailing | every two years |
| Low | no data or system access, easy to replace | office supplies vendor | at contract renewal |
In CyberTell you set likelihood and impact for each supplier on four levels each, plus a risk level from low to critical. The risk overview turns this into a 4×4 matrix, a distribution by level, the number of suppliers with data or system access and those based in countries with elevated geopolitical risk.
On request, the AI creates a risk profile from category, country, access and the provider's website. The resulting level is only a suggestion: your risk level changes only when a user accepts it. This is deliberate, because a provider controls the content of its own website.
Contracts and processors under the Swiss FADP
As soon as a supplier processes personal data on your behalf, for example as a cloud provider, payroll bureau or IT service provider with access to your servers, the revised Federal Act on Data Protection (FADP) treats it as a processor. Under Art. 9 FADP you may delegate processing if a contract or the law provides for it, the supplier processes the data only in the way you yourself would be permitted to, and you have made sure that it can guarantee data security. If the supplier passes the work on to a third party, it needs your prior authorisation.
For critical and high suppliers, review at least these documents:
- data processing agreement (DPA)
- terms and conditions and service level agreement (SLA)
- privacy policy and list of sub-processors
- security policy or certificates, for example ISO 27001
For cloud and SaaS contracts, five questions are worth asking. What happens if the provider loses your data, and is liability capped? Who is responsible for backups? Where is the data stored, and is it disclosed abroad? What availability is promised? How do you get your data back in a usable format when the contract ends?
If data is stored outside Switzerland, the rules on disclosure abroad also apply (Art. 16 FADP). If you keep a record of processing activities, list your suppliers there as recipients. Data Protection Management keeps the record and your processing agreements in one place.
In CyberTell you store contracts and evidence as links on the supplier. The AI document analysis checks terms, SLAs or DPAs against the questions above and suggests a risk level. It does not replace legal advice, but it shows you where to look more closely.
Setting up third-party risk management in five steps
Working supplier management does not need a dedicated team. It needs one responsible person, a list and a fixed rhythm. The five steps follow what the ICT Minimum Standard describes in category ID.SC: identify and prioritise suppliers, set out obligations in contracts, monitor compliance and agree incident procedures together. The free ICT Quick Check with 14 questions shows where you stand today.
-
Record suppliers
Check the accounts payable list, credit card statements and departments. Enter each supplier in the register with category, country, contact, data access and system access.
-
Rate criticality
Assess impact and likelihood and assign a level from low to critical. Start with the critical suppliers.
-
Request evidence
Ask critical and high suppliers for contracts, DPAs and security evidence. In CyberTell a compliance request goes to the supplier by email, and the supplier confirms the requirements via a link.
-
Set the rules
Write down in a supply chain policy what you expect from suppliers, such as incident reporting and handling of access. CyberTell creates a draft, exports it as PDF or Word and collects confirmations from your suppliers.
-
Review regularly
Update the register and ratings at the interval for each level, renew expired evidence, and deactivate suppliers you no longer use and remove their access.
When something happens at a supplier
An incident at a supplier is also your incident. Whether it is a data leak at the SaaS provider, a compromised remote maintenance account or a cloud service that is down for days: if you only start thinking when it happens, you lose time.
Settle in advance
- Reporting in the contract: the supplier reports security incidents to you without delay and names a reachable contact. The FADP requires processors to report data security breaches as soon as possible (Art. 24 para. 3).
- Immediate measure per critical supplier: what do you do if this supplier fails or is compromised? In CyberTell you can record this measure with the supplier's risk.
- Your own backups: clarify who is responsible for backups and test the restore. CyberTell flags a backup test as overdue if it is missing or older than six months.
When it happens
- Block or restrict the supplier's access and change the passwords of affected accounts.
- Clarify which of your data and systems are affected. The register and dependencies give you the answer.
- Check whether you, as controller, must report to the FDPIC. That is the case if the data security breach is likely to result in a high risk for the persons concerned (Art. 24 FADP). Since 1 April 2025, operators of critical infrastructure must also report cyber attacks to the Federal Office for Cyber Security (BACS) within 24 hours of discovery.
- Document the incident and then review the supplier's rating.
The article Incident response for SMEs describes what a structured process for security incidents looks like.
Frequently asked questions
What is third-party risk management?
Which suppliers are critical?
Do I need a data processing agreement with every cloud provider?
How often should suppliers be reviewed?
Can AI assess supplier risk?
Third-Party Management. Assess supplier risks and ensure compliance
Everything this article describes can be put into practice in CyberTell — in the demo with sample data or in your own account.