What a supplier incident is
Every business relies on a chain of suppliers: accounting software, a CRM system in the cloud, the email service, the accounting firm, the payroll company, the website hosting provider, the technician who maintains the camera system and the IT company. Many of them have access to the organization’s systems or information, and some have very broad access.
A supplier incident is a fault or a breach at one of these parties that affects you. The organization itself was not breached, and yet its information is exposed, its systems are down or someone is impersonating it. The field that deals with this is called third-party risk management. When the damage passes through software or a service the supplier provides, it is called a supply chain attack.
Four ways it reaches you
- Through the supplier’s access: a breached supplier account, or a remote access tool installed for support, lets an attacker into your network with permissions that look legitimate.
- Through the information the supplier holds: a breach of the system of a supplier that processes information for you, such as payroll, accounting or customer management, exposes your information and your customers’ information.
- Through the product or the update: software or an update compromised at the vendor reaches you through the usual channel, and so it looks trustworthy.
- Through dependency: an outage of a cloud service, a communications provider or a critical system at the supplier stops you too, even when there is no breach at all.
There is also an indirect route. A supplier’s breached mailbox is used to send an invoice that looks real, with new bank account details. This is fraud in the name of a familiar party (business email compromise, BEC), and it succeeds because the message comes from an address you know and correspond with.
What increases the risk
- No supplier list: it is not clear who the suppliers are, which systems and information they have access to, and who in the organization is responsible for the relationship with each one.
- Permanent, broad access: a remote connection that is open all the time, a single administrator account shared by all the supplier’s technicians, and no multi-factor authentication (MFA).
- Suppliers who finished and stayed: accounts and connections of a former supplier that nobody closed. Just as when an employee leaves (offboarding), ending work with a supplier needs a procedure.
- Dependence on a single supplier: a critical system with no alternative and no way to export the data from it, in other words a single point of failure.
- Agreements without security clauses: security measures are not defined, there is no duty to report an incident, and there is no information about the sub-processors.
- Changing payment details without verification: updating a bank account based on an email alone.
The supplier with the broadest access is usually the IT company. It holds administrator passwords, remote management tools and access to every server and computer. That is why the IT company’s level in information security, the way it manages its own permissions and protects its tools, is a central part of the organization’s risk.
Early warning signs
- An official notice from the supplier about an incident, or a media report about a breach at the supplier.
- Sign-ins from supplier accounts at unusual hours, from unexpected locations, or to systems they are not supposed to touch.
- A request to change bank account details, especially when it comes with time pressure.
- Phishing messages that use details only a specific supplier knows, such as order numbers or the names of contacts.
- Sudden faults in services that depend on the supplier, or unusual system behavior after an update.
Some of the signs come from outside, so there needs to be someone to pass them on to. An accounting employee who received a strange request from a supplier should know that this is exactly the kind of thing that gets reported.
The impact on the organization
An outage at a critical supplier stops work just like a fault on your side, and sometimes for longer, because the decision to restore service is not in your hands. A leak at a supplier that processes personal information for you is your problem with your customers and with the regulator.
Under the Privacy Protection Law, the organization that decides why and how the information is used (the data controller) remains responsible for it even when the processing is done at a supplier. The data security regulations require reviewing the risks before contracting with an outside party that will receive access to personal information, and setting out its security obligations in the agreement. Since Amendment 13, the Privacy Protection Authority has broader enforcement powers, and the question of whether the organization chose the supplier and supervised it properly is part of what is examined.
There is also damage that is hard to measure. Customers who were notified that their information was exposed do not always distinguish between the organization and its supplier. As far as they are concerned, they gave the information to you.
How to reduce the risk
- Mapping suppliers (vendor inventory): a list of all suppliers, what information and access each one has, and what happens to the business if it is unavailable. Based on this, suppliers are ranked by risk level.
- Checking before contracting (vendor assessment): a security questionnaire for the significant suppliers, and a request for evidence such as ISO 27001 certification or an independent audit report. These are not a substitute for judgment, but they show the supplier has an organized process.
- Minimal, controlled access: a personal account for each person at the supplier, multi-factor authentication, access only to the systems required, and a remote connection that is opened as needed and for a limited time (just-in-time access) and does not stay open.
- Network segmentation (VLANs): a supplier who maintains one system should not see the whole network.
- Monitoring and logging: recording the actions taken from supplier accounts, and alerts on unusual activity.
- Verification through a separate channel (out-of-band verification): every change in payment details is verified by a call to a number you already know, not to the number that appears in the email.
- Closing at the end of the engagement: canceling accounts, changing passwords the supplier knew, and written confirmation that the information was returned or deleted.
- Alternatives and an exit plan: for the critical suppliers, a scenario in the disaster recovery plan (DRP) and the ability to export the information and move to an alternative if needed.
Recognized frameworks such as ISO 27001 and NIST CSF include dedicated controls for managing suppliers and the supply chain, and it is worth using them as a checklist even in a small business.
What goes in the agreement with the supplier (DPA)
When a supplier processes personal information for you, the agreement should include an annex that defines the processing and the security obligations. In international terms, it is called a data processing agreement (DPA). What it should contain:
- Which information the supplier receives, for what purpose, and in which systems it processes it.
- The security measures the supplier commits to, including permissions, encryption and backup.
- A confidentiality obligation for the supplier’s employees who are exposed to the information.
- A duty to notify you without delay of a security incident involving your information, and to cooperate in the investigation.
- Sub-processors: who they are, and whether your approval is required before new ones are added.
- Where the information is stored, including whether it is transferred outside Israel.
- The right to receive periodic reports on compliance with the commitments, or to carry out an audit.
- What happens to the information at the end of the engagement: return or deletion, and confirmation of it.
The legal wording is a matter for a lawyer. The decision of what to require from each supplier, according to its risk level, is the organization’s decision, and it is best made together with someone who understands the technical side and the regulation.
When it happens: working with the response team
When a supplier reports an incident, or when there is a suspicion that its access was exploited, a cyber incident response team works in an order similar to any other incident, with a few steps specific to suppliers:
- Assessing the exposure: which systems and information the supplier has access to, and which of them may be affected.
- Restricting access: temporarily suspending the supplier’s accounts and connections, and changing passwords and keys the supplier knew.
- Checking activity: going through the system logs to see what was done recently from the supplier’s accounts, and whether there are signs of an attacker inside the network.
- Requesting information from the supplier: what happened, when, which of your information is involved and what the supplier is doing, according to what was set in the agreement.
- Continuing work: moving to an alternative or to a manual work procedure if the service is unavailable, according to the business continuity plan (BCP).
- Reporting: checking whether a report to the Privacy Protection Authority is required and informing customers, in coordination with the supplier and a legal adviser.
- Lessons: updating the requirements from the supplier, its permissions and the agreement, or deciding to replace it.
Summary
- There is a supplier list, with each one’s access and information and its risk level.
- Every supplier with access has a personal account, multi-factor authentication and limited access.
- Suppliers’ remote connections are opened as needed and are logged.
- A change in payment details is verified by phone to a known number.
- There is an agreement with security clauses (DPA) with suppliers that process personal information.
- Critical suppliers have a scenario in the recovery plan and a defined alternative.