Supplier and Supply Chain Risk

Everything on your side is protected and up to date, but the business also runs through suppliers: the internet provider, the cloud email service, the accounting software and the company that connects remotely for support, and when one of them is hit, the impact on you is immediate. We map your suppliers and your dependence on them (third-party risk), identify which of them could stop the business, and put in place restrictions, a contract and a fallback plan that are under your control.

A team working together on laptops

The attacker didn’t break in.
They walked in with the supplier’s key

An IT provider sometimes has a remote management tool (RMM) with access to every computer in the business. Whoever takes over the provider gets the same access, and the defenses see a familiar supplier doing routine work. What is critical depends on the business, so every business is mapped separately.

  • Mapping suppliers and dependencies and classifying them by business impact
  • Limiting remote access and eliminating shared accounts
  • A fallback plan (exit plan) and an offline copy of critical data

Call +972-3-3801180

Who it’s for

  • Businesses that depend on external systems

    Cloud accounting, payroll, payment processing, email and a website, each with a different supplier, and no single place to see all of them and how dependent you are on each one.

  • Businesses that hold personal data

    Clinics, accounting and law firms and service companies. When a supplier processes the data on your behalf (data processor), your responsibility as the database owner doesn’t pass to it.

  • Businesses whose suppliers connect to their network

    A software company that connects remotely for updates, a technician for a specialized system or an advertising agency with access to the customer list. Each such access is a door, and you need to know who holds the key.

Sound familiar?

These are situations we see in businesses whose IT is in order, but whose suppliers stayed out of the picture.

  • There’s no organized list of suppliers, and it’s unclear which of them hold customer data
  • The support provider connects remotely with a shared account and a password that hasn’t been changed in years
  • There’s a supplier without whom work stops, and there’s no ready alternative
  • A supplier the business stopped working with still has access and data (supplier offboarding)
  • Word came that a supplier was breached, and nobody knows what it held or what to do now
  • An email came from a regular supplier with new bank account details, and there was no procedure to verify it by phone (BEC)

What supplier risk management includes

The scope depends on how many suppliers the business has and how much it depends on them.

  • Mapping suppliers and dependencies (supplier inventory)

    One list of all suppliers: what each one provides, what data it holds, which systems it is connected to and who in the business owns the relationship.

  • Classification by impact (supplier tiering)

    Critical: the business stops without it. Significant: work is disrupted. Minor: you feel it, but you manage. The classification sets how much work goes into each supplier.

  • Security questionnaires and evidence

    A security questionnaire matched to the risk level, and checking evidence such as a SOC 2 report or ISO 27001 certification where relevant, including checking that it covers the service you receive.

  • Contract and data processing agreement (DPA)

    Security clauses in the contract, a data processing agreement for suppliers that hold personal data, a duty to report incidents and return or deletion of the data at the end.

  • Supplier access to the network (third-party access)

    Remote access only with MFA, a personal account for each technician instead of a shared account, least privilege and access opened as needed, with documentation.

  • An alternative and continuity for every critical supplier

    An exit plan, a second supplier or a backup line where possible, and an offline copy of the data you can’t work without.

  • Monitoring incidents and leaks

    Tracking security incidents and leaks published about suppliers (threat intelligence), and a procedure for what to do when a supplier reports an incident or when your data shows up where it shouldn’t.

  • Supplier onboarding and offboarding

    A check before a new supplier gets access or data, and on the day the engagement ends: revoking access, changing passwords and checking that the data was returned or deleted.

What we take care of, in detail

Mapping and classification

  • Supplier register: the service, the relationship owner in the business, the data the supplier holds and the systems it is connected to
  • Dependency mapping against business processes, based on a business impact analysis (BIA) and RTO/RPO targets
  • Classification by impact (supplier tiering): critical, significant, minor, plus marking the sensitivity of the data
  • Identifying single points of failure and the concentration of several services with one supplier (concentration risk)
  • Suppliers’ suppliers (fourth-party risk): cloud services and subcontractors the supplier itself relies on
  • Common types of suppliers: internet provider, cloud and email service, hosting company, accounting or ERP software, payroll, payment processing, an IT or software provider with remote access, couriers, an advertising agency with access to customer data

Review, contract and permissions

  • Security questionnaires scaled to the classification level
  • Checking evidence: a SOC 2 Type II report, an ISO 27001 certificate and the certification scope, penetration test reports where relevant
  • Security clauses in the contract: incident reporting duty, right to audit, sub-processors, data location
  • A data processing agreement (DPA) for suppliers that process personal data on the organization’s behalf, in line with the Data Security Regulations
  • Remote access for suppliers: MFA, a personal account for each technician, access by approval and for a limited time (just-in-time access)
  • Separating supplier access into its own network zone (segmentation, VLAN) or identity-based access without a classic VPN (ZTNA)
  • Eliminating shared accounts and logging every supplier connection (audit log)
  • Payment security: phone verification for every change to a supplier’s bank details, against email impersonation fraud (BEC)

Continuity, monitoring and compliance

  • An exit plan for every critical supplier: how to get the data out and where to move
  • A second supplier or a temporary alternative: an additional internet line with automatic failover, an additional payment processor, a manual work procedure
  • An offline copy of critical data held by a supplier, and a separate backup for cloud email and files
  • Including critical suppliers in the business continuity (BCP) and disaster recovery (DRP) plans and in drills
  • Monitoring incidents and leaks at suppliers (threat intelligence) and a response scenario for an incident at a supplier (incident response)
  • Supplier onboarding and offboarding: a check before access, revoking access and deleting data at the end
  • Periodic supplier review based on the classification level
  • Alignment with the Privacy Protection Law and Amendment 13, the supplier controls in ISO 27001 (Annex A 5.19 to 5.23) and NIST CSF 2.0 (GV.SC)

From the first conversation to an organized routine

  1. 1

    Introductory call

    Which suppliers the business has, which of them hold data and which connect to the network, and what requirements have already come from customers or a regulator.

  2. 2

    Mapping and classification (supplier tiering)

    A first supplier register and a classification of each supplier by its impact on the business: critical, significant or minor.

  3. 3

    Closing gaps

    Limiting remote access, contracts and DPAs, and a fallback plan for the critical suppliers, in order of priority.

  4. 4

    Periodic review

    Updating the register when a new supplier comes in or a supplier leaves, and rechecking the critical suppliers on a fixed schedule.

What happens when the problem starts at a supplier

You can manage the business’s IT well and still be hit through someone else. An incident at a supplier reaches you through the data it holds, through the access it has to the network, or simply because you stopped receiving its service.

  1. When a critical supplier goes down, work stops

    When the internet provider, the cloud email service or the accounting system is unavailable, there is nothing to fix on your side. What matters is what was prepared in advance: a backup line, a manual work procedure or a copy of the data. Without an alternative, the length of the outage (downtime) is decided at the supplier, not by you.

  2. A supplier’s access is access to your network

    An IT or software provider that connects remotely sometimes holds the broadest permissions on the network. If its account is breached, or the technician’s computer is infected, the attacker comes in through the same door. Supply chain attacks exploit exactly this trust, and sometimes they arrive through a software update that was compromised at the vendor.

  3. The data is at the supplier, the responsibility is yours

    When a payroll provider, a cloud provider or an advertising agency holds personal data of employees or customers, a leak on their side is your incident. The Data Security Regulations explicitly address engaging an outside party (outsourcing): the risk is assessed before the engagement, and the agreement sets what the supplier may do with the data and how it protects it. Amendment 13 expanded the supervision and enforcement powers of the Privacy Protection Authority, and an inquiry may also ask what was checked at the suppliers.

  4. What a certificate tells you about a supplier

    A SOC 2 report or an ISO 27001 certification shows that the supplier manages information security systematically. It’s worth checking the certification scope, whether the service you receive is included in it and when the last audit took place. A small supplier without certification isn’t necessarily riskier, and with such a supplier the questionnaire, the contract and the access restrictions do the work.

  5. Where the IT provider comes in

    Most of the protection against supplier risk sits in the infrastructure: how a supplier connects, which part of the network it reaches, what is logged and where a copy of the data is kept. Whoever manages the network, the permissions and the backup can actually put these restrictions in place and show them in an audit under ISO 27001 and the Israel National Cyber Directorate guidelines. And the IT company is a supplier too, so it has to work by the same rules it demands of others.

Guide: How to map critical suppliers: who brings the business to a halt if they go down

Frequently asked questions

About supplier and supply chain risk.

Didn’t find an answer? +972-3-3801180

Size doesn’t mean the service won’t go down, or that your account with them is configured correctly. A large supplier usually provides organized evidence, so checking it is quick. A large part of the work is actually on your side (shared responsibility model): who holds the admin account, whether there is MFA, whether there is a separate backup and what to do if the service is unavailable.

Not at the same level. The classification by impact sets how much work goes in: a critical supplier gets a full review, a contract and a fallback plan, and a minor supplier gets an entry in the register and a check that it has no unnecessary access. That way the effort is focused on the suppliers that can really stop the business or expose data.

A data processing agreement sets out what a supplier may do with personal data it holds for you: for what purposes, with what security measures, when it reports an incident and what happens to the data at the end of the engagement. You need one with every supplier that processes personal data on behalf of the business, for example payroll, a cloud CRM or an advertising agency that receives the customer list. The legal wording is finalized with a lawyer.

The connection itself is fine. The question is how it’s set up. A shared account that all the technicians know, with no MFA, with admin rights to the entire network and open all the time, is a door an attacker can use exactly like the technician. We move to a personal account for each technician, MFA, least privilege and access that opens as needed and is logged.

Check the register for what the supplier holds and where it connects, suspend or restrict its access to the network, change the passwords and keys it had, and check the logs for unusual activity. At the same time, check with legal counsel whether personal data was affected and whether there is a duty to report to the Privacy Protection Authority (breach notification). If the service is unavailable, activate the fallback plan.

Yes. Large customers often ask how you manage your suppliers, and ISO 27001 includes dedicated controls on the subject. A documented supplier register, classification, contracts and DPAs are what you present in a questionnaire, an audit or an inquiry by the Privacy Protection Authority.

Want to know which suppliers could stop your business?

Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.

Business hours: Sunday to Thursday, 08:00 to 17:00

Existing client? Open a support ticket

Leave your details and we’ll get back to you

Your details are used only to get back to you. Privacy policy

Call +972-3-3801180Get in touch