From the mapping to the work itself
Mapping suppliers ends with a classified list: who is critical, who is significant, who is minor and who holds personal information. This article deals with the stage after that, the work with the suppliers themselves, and mainly with the critical ones. Four tools do most of the work: checking, the contract, limiting access and a fallback plan.
It is worth understanding what each tool gives you. Checking and the contract reduce the chance that something will happen at the supplier, and make clear what the supplier owes you when it happens anyway. Limiting access and a fallback plan determine how much it will hurt you. You manage the last two yourself, without waiting for anyone.
Checking the supplier: questionnaire and evidence
The check starts with a security questionnaire, with a scope that fits the supplier’s level. From a critical supplier you want to know, among other things:
- How permissions are managed there, and whether there is multi-factor authentication (MFA) for everyone who accesses your information.
- Where the information is stored, how it is backed up, and whether the backup has been tested by restoring from it.
- Which suppliers it relies on itself (sub-processors).
- How it handles a security incident (incident response), and when and how it notifies customers.
- What happens to the information when the engagement ends.
A questionnaire alone is a declaration, so you also ask for evidence when it exists. A SOC 2 report, especially Type II, describes an external audit of the supplier’s controls over a period of time. ISO 27001 certification shows that the supplier has an organized information security management system (ISMS). In both cases, read the details: what the scope of the certification is, whether the service you receive is included in it, and when the last audit took place.
Small suppliers usually do not have such reports, and that does not disqualify them. With them, the questionnaire, the contract and limiting access do the work, and sometimes a conversation with whoever manages their IT teaches you more than any document.
What goes in the contract
A contract with a supplier usually deals with price and scope of service. With a critical supplier, it is worth adding clauses on security and continuity:
- A duty to report an incident: the supplier notifies you of a security incident involving your information or your service, within the time and to the person defined in the contract.
- Security measures: MFA, encryption, backup and security updates. It is better to refer to a recognized standard such as ISO 27001 than to write everything from scratch.
- Service level (SLA): what counts as a fault, how it is reported and what the supplier commits to do.
- Right to audit: the option to request evidence or carry out a check, to a reasonable extent.
- Subcontractors: the supplier gives advance notice before passing your information to another party.
- Ending the engagement: returning the information in a format you can work with, and documented deletion afterwards.
The legal wording is finalized with a lawyer. The role of whoever manages IT and security is to make sure the clauses match what actually happens in the systems.
Data processing agreement (DPA)
A supplier that holds or processes personal information on behalf of the business, for example a payroll provider, a CRM system in the cloud, a courier company or an advertising agency that receives the customer list, is a data processor. Your responsibility as the database owner does not pass to it.
The Privacy Protection Regulations (Data Security) explicitly address this kind of engagement (outsourcing): you review the information security risks before contracting, and set out in the agreement what the supplier may do with the information, for which purposes, which security measures it takes and what happens to the information at the end. A data processing agreement is the document that arranges all of this. Amendment 13 to the law, in force since August 2025, expanded the supervision and enforcement powers of the Privacy Protection Authority, so the agreement should be signed and up to date, and not amount to a general confidentiality clause.
The supplier’s access to the network
This is the part that depends most on you. An IT provider, a software company or a technician for a dedicated system who connect remotely (remote access) sometimes receive the broadest permissions on the network. If their account is breached, or the technician’s computer is infected, the attacker uses the same door. These are the rules that reduce the risk:
- A personal account for each person: no shared accounts that all the supplier’s technicians know. That way you know who connected, and you can revoke one person’s access without stopping everyone.
- Multi-factor authentication (MFA) on all supplier access, with no exceptions.
- Minimal permissions (least privilege): the payroll system supplier reaches the payroll system’s server, not the whole network.
- Access as needed (just-in-time access): the connection opens when there is work, with approval, and closes when it is done, instead of a connection that is open all the time.
- Network separation: supplier access reaches a defined zone (segmentation, VLAN), or goes through identity-based access without a classic VPN (ZTNA).
- Logging (audit log): every supplier sign-in is recorded, and anomalies are checked.
There is also access that goes through email. A breached mailbox of a regular supplier is a convenient tool for payment fraud (BEC). A procedure under which every change in a supplier’s bank account details is verified by phone with a known contact, at a number you saved in advance, greatly reduces this risk.
A fallback plan for a critical supplier
For every critical supplier, ask what you do on the day it is unavailable. The answer is usually built from several parts, depending on the type of supplier:
- A second supplier or a temporary alternative: an additional internet line from another provider, with automatic switchover in the firewall (failover), an additional payment processor, or an agreed manual work procedure for a few hours.
- An offline copy: the customer list, open orders, contacts and supplier details, kept up to date and stored with you, so you can keep providing service even when the system is unavailable.
- A separate backup for cloud services: for email and files in the cloud, the provider is responsible for the service working, and not always for restoring what was deleted or encrypted (shared responsibility model). A backup of your own closes the gap.
- An exit plan: how you get the information out and move to another supplier if the engagement ends, if the supplier closes or if it no longer meets the requirements. Check in advance in which format the information comes out, and who knows how to carry out the move.
The alternatives are built into the business continuity plan (BCP) and the disaster recovery plan (DRP), and tested in an exercise. An alternative nobody has tried is an assumption, not yet a plan.
When a supplier reports an incident
One day an email arrives from a supplier: we had a security incident, we are investigating. What you do in the first hours depends on what you prepared. When there is a supplier register and a procedure, the response looks like this:
- Check in the register what the supplier holds, which systems it is connected to and who in the business is responsible for it.
- Suspend or restrict its access to the network until it becomes clear what happened.
- Change passwords and access keys (API keys) that the supplier held or used.
- Check the logs for unusual activity from its accounts.
- Check with the legal adviser whether personal information was affected, and whether there is a duty to report to the Privacy Protection Authority.
- If the service is unavailable, activate the fallback plan.
All of these are part of the incident response plan, with a dedicated scenario for an incident at a supplier. When the scenario is written and exercised, you do not discover in the middle of the incident that nobody knows which systems the supplier is connected to.
Summary: a checklist for every critical supplier
- A security questionnaire and evidence, and a check that they cover your service.
- A contract with a duty to report, security measures, a right to audit and an orderly end of engagement.
- A signed data processing agreement (DPA) with every supplier that processes personal information.
- Remote access with a personal account, MFA, minimal permissions and logging.
- A second supplier or a temporary alternative, an offline copy and an exit plan.
- A response scenario for an incident at a supplier, and an exercise of it.