Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Threat Intelligence

05:30 PM
Connect Directly

Who's the Weakest Link in Your Supply Chain?

Nearly 60% of organizations have suffered data breaches resulting from a third party, as suppliers pose a growing risk to enterprise security.

Do you know how many third parties your organization works with?

If not, you're not alone: Only 34% of companies have a comprehensive inventory of all third party suppliers they work with, according to a survey of 1,038 professionals across multiple industries in the US and UK, according to the recently released "Data Risk in the Third-Party Ecosystem" report conducted by The Ponemon Institute and commissioned by Opus.

Third party breaches are significant and in the US at least, they are growing. (This is the first year UK respondents were polled, so no earlier data exists for comparison in that region). In the US, 61% of businesses have had a third-party breach, up 5% from last year and 12% from 2016.

More than three-quarters of respondents say the number of third-party security incidents involving vendors is going up, researchers found. Part of the reason is greater reliance on them: in the US, the number of third party suppliers increased 25% over 2017 and sits at an average of 583.

However, companies struggle to keep an inventory of all their suppliers due to a lack of centralized control (69%) and the complexity of these relationships. Only 15% know how their information is accessed and processed by the companies they work with, and only 28% receive notifications when their information is shared with a third party, researchers report.

Many don't know what to do. Only 37% say they have sufficient resources to manage third-party relationships; 35% say their third-party risk management program is "highly effective."

When it comes to supply chain risk, many businesses are in the dark. Researchers note 22% of respondents could not determine whether they'd had a third-party breach in the year prior.

"The reason that's so scary, or scary to me, is the fact that if you can't determine if you've had a breach …  that's really bad," says Lee Kirschbaum, senior vice president and head of product, marketing, and alliances at Opus. "Companies need to know who has access to personal and sensitive information."

Businesses can be held liable for being in the dark on security breaches, he continues. Lee points to the General Data Protection Regulation (GDPR), which requires companies to have a good understanding of who is in their supply chain and has access to sensitive data.

From a practical standpoint, Lee says it's "not surprising that people don't have an inventory … it's just very risky." Many policies allow employees to download apps and use online services without IT's approval, driving opportunities to share sensitive data outside the organization.

But keeping meticulous track of the third parties you work with doesn't guarantee security. Almost 60% of companies with an inventory don't know if their safeguards are strong enough to prevent a breach and less than 50% evaluate the security practices of their vendors. Sixty percent don't have the resources to verify vendors' security posture; the same amount don't require third parties to complete questionnaires or conduct security assessments.

It's Not All Bad News   

Companies that report no third-party security breaches also report stronger focus on third-party management. Of those who hadn't suffered third-party breaches, 60% say they allocate resources toward managing vendors. Only 15% of breached companies say they have the same level of focus.

In the US, businesses are starting to take responsibility.

"Over the past few years, we've seen in the US more ownership in terms of people being accountable for third-party risk," says Lee, adding that supply chain security "starts with ownership and accountability. As we drive toward more ownership, it enables a person or a group to be accountable for putting in the appropriate controls so that can occur."

He advises companies to conduct an inventory of all third parties with whom they share information, and know who can access confidential data. Create a formal process for reviewing and managing vendors' privacy and security practices. Know how they handle new and emerging threats; for example, unsecured IoT devices. When data is shared with external vendors, make sure you know about it. Get your board of directors involved in the process: companies that didn’t report a vendor breach were 28% more likely to include senior execs.

"Supply chains are an extremely complex multi-stakeholder environment," says Ophir Gaathon, CEO and co-founder of Dust Identity. "Currently there are wide gaps in what technology can cover that leave unaddressed vulnerabilities."

Diamonds and Dust

Startup Dust Identity focuses on ensuring the integrity of hardware components, an issue of growing importance to manufacturers in the critical infrastructure space as the IoT continues to grow. Companies need to know hardware components were sourced through the proper channels, says Gaathon, and it's challenging to learn where objects come from and who accessed them.

"Until now, the industry has depended on technologies such as RFID, holograms or barcodes, that were not really designed for security applications," he explains. The IoT is driving an "explosion" of connected parts and, as a result, growing the attack surface.

Today's supply chains are increasingly global and involve more people, says Gaathon, and manufacturing is leaner with smaller batches and shorter runs. The two trends make verifying vendors and parts more complex. Dust Identity aims to ease part identification by placing a layer of nano-engineered diamond crystals onto products. A scanning technology lets them read the angle of those diamonds and produce a unique identity for a specific part; this identity can be used to link the part to data, ledgers, processes, and other components, he explains.

"We started with the hardware, where we focus on delivering high-security authentication with end-to-end tracking that traces down to the component level for the commercial IT, defense and government sectors," says Gaathon.

Dust was first funded by DARPA, he continues, and the startup recently raised $2.3 million in seed funding. In the long term, it hopes to influence how security is deployed in supply chains across industries.

Related Content:


Black Hat Europe returns to London Dec 3-6 2018  with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
11/28/2018 | 8:04:20 AM
Thanks for your great post. It's really important for me. I look forward to your new post
User Rank: Apprentice
11/28/2018 | 8:03:05 AM
Thanks for sharing. It's very important for me
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.