Why start with mapping
When supplier risk comes up, the first impulse is to send a security questionnaire to everyone. That wastes time on both sides. A supplier that delivers office supplies does not need to fill out a long questionnaire, and the software vendor that holds all of the business’s orders needs much more than a questionnaire.
The mapping answers one simple question: if this supplier goes down tomorrow morning, what happens to the business. The answer determines how much work to invest in each supplier and exactly what to do with it. In professional terms this is classifying suppliers by criticality (supplier criticality), and it is the basis of third-party risk management.
The mapping relies on a business impact analysis (BIA): which processes the business cannot work without, and how long it can be without each system (RTO). If you have already done a BIA, much of the work is ready. If not, mapping suppliers is a good way to start one.
Step 1: a list of every supplier
The first list is almost always incomplete. Suppliers come into the business in different ways, and not all of them go through whoever is responsible for IT. To catch them all, look in several places:
- Accounting: anyone who receives a monthly or annual payment. This is usually the most complete source.
- IT: the internet provider, cloud and email services, the hosting company, software licenses and anyone who connects remotely (remote access).
- Department managers: tools a particular team started using without telling anyone (Shadow IT), and consultants or advertising agencies that were given access to systems.
- The accounts themselves: external users in the cloud email service, on the website and in systems, and apps that were granted permission to the business account.
At this stage, do not filter. Even a supplier that seems marginal goes on the list, and the decision about what matters comes later.
Step 2: four questions about each supplier
For each supplier on the list, answer four short questions. The answers are recorded in a supplier register, which can start out as a simple spreadsheet:
- Availability: what happens to the work if the supplier is not available, and how long you can manage without it.
- Data: what information it holds. Personal data of customers or employees, financial data, business documents, or nothing.
- Access: whether it is connected to the network or the systems. Remote access, an account in a system, an automated connection between systems (API), or no access at all.
- Owner: who in the business is responsible for the relationship, makes decisions about it and gets the phone call when there is a problem.
The fourth question looks administrative, but it matters. A supplier with no owner in the business is a supplier nobody will notice when it needs to be reviewed, when its contract needs updating or when the engagement needs to end.
Step 3: classification by impact
With the answers in hand, each supplier gets a tier (supplier tiering). For most businesses three are enough:
- Critical: the business stops without it. You cannot work, sell or provide service until it is back.
- Significant: work is disrupted. You can continue partially or manually, at the cost of delays, mistakes and extra load.
- Minor: noticeable, but you manage. There is a substitute available, or it can wait.
Alongside the impact on service, mark data sensitivity separately. A supplier that holds personal data of customers or employees needs a contract, a DPA and a review, even if its failure would not stop work. The result is a table with two axes: how much the supplier affects operations, and how sensitive the data it holds is.
What each tier requires
The classification is only worth something when it is translated into actions. This is a common breakdown:
Critical supplier
- A full review: a security questionnaire and evidence such as a SOC 2 report or ISO 27001 certification where they exist, and a check that the certification scope covers your service.
- A contract with security clauses, a duty to report incidents and a defined service level (SLA).
- A fallback: a second supplier, a backup line or a manual work procedure, and an exit plan.
- An offline copy of the data you cannot work without.
- Inclusion in the business continuity plan (BCP) and in drills, and a periodic review.
Significant supplier
- A shortened questionnaire and a contract with basic security clauses.
- A work procedure for when it is not available, even if the procedure is manual.
- A review when the service or the contract changes.
Minor supplier
- An entry in the register and an owner in the business.
- A check that it has no access or data it does not need.
Some rules apply to every tier. Every supplier that connects to the network gets a personal account, two-factor authentication (MFA), least privilege and logging of its sign-ins (audit log). And every supplier that processes personal data on behalf of the business needs a data processing agreement (DPA), in line with the Privacy Protection Regulations (Data Security), 2017 issued under the Privacy Protection Law.
Dependencies you do not see at first glance
The first mapping almost always reveals dependencies nobody had thought about:
- Concentration on one supplier (concentration risk): email, files, sign-in to systems and some of the applications all rely on the same cloud account. One failure there is felt everywhere.
- The supplier’s supplier (fourth-party risk): the accounting software runs on another company’s cloud service, and the payroll provider uses a subcontractor. An incident at their end reaches you through your direct supplier.
- The domain: the domain registrar and the DNS service. If the domain is not renewed, or the account at the registrar is compromised, email and the website stop working together.
- One person: a small supplier where all the knowledge about your system sits with one of its employees. That is a single point of failure, exactly like a server without a backup.
Add these dependencies to the register next to the relevant supplier, and check whether they change its classification.
A living register, not a one-time file
A supplier register that is built once and forgotten loses its value quickly. Suppliers change, services expand, and an advertising agency that started with access to one account gradually gets access to several more. So set two fixed points in the process:
- Supplier onboarding: before a new supplier gets access or data, it goes into the register, gets a tier and goes through the review its tier requires.
- Supplier offboarding: when the engagement ends, revoke its access, change passwords it knew and make sure the data was returned or deleted.
Beyond that, review the critical suppliers periodically. The register is also what you present when a large customer sends a security questionnaire, in an ISO 27001 audit or in an inquiry by the Privacy Protection Authority. Amendment 13 to the Privacy Protection Law, in force since August 2025, expanded the Authority’s supervision and enforcement powers, and such an inquiry may also ask what was checked at the suppliers.
Summary: the mapping on one page
- Collect all suppliers from accounting, IT and department managers.
- For each supplier, record what happens if it is not available, what data it holds, whether it is connected to the network and who is responsible for it.
- Classify each supplier as critical, significant or minor, and separately mark suppliers that hold personal data.
- Turn each tier into actions: a review, a contract, access restrictions and a fallback.
- Look for hidden dependencies: concentration on one supplier, suppliers’ suppliers, the domain, one person.
- Set an onboarding and offboarding procedure, and a periodic review for critical suppliers.