A third-party data breach occurs when malicious actors compromise a vendor, supplier, contractor, or other organization in order to gain access to sensitive information or systems at the victim’s customers, clients or business partners. Third-party data breaches are becoming increasingly common as technology makes it easier for businesses to connect and as global supply chains grow in complexity. As a result, organizations are often unable to visualize where their data goes, and proprietary or sensitive data can easily be shared with suppliers and subcontractors that the contracting organization knows little to nothing about.
This article examines why third-party data breaches are increasing; provides examples of prominent companies that were compromised by third, fourth, or Nth party vendors; and explains what steps you can take to mitigate the risk of your organization becoming a victim.
The last decade has seen an increasing number of large organizations investing heavily in information security. In fact, information security spending grew by a stunning 12.4% in 2020 alone. No system can be entirely secure, but heavy investments in cybersecurity do make it far more difficult for malicious actors to compromise well-resourced organizations. Hackers are increasingly incentivized to target smaller subcontractors to bypass robust and well-funded cybersecurity programs. Compromising a small HVAC contractor and using that organization as an unwitting Trojan Horse is far easier to accomplish than directly compromising a Fortune 500 company with a fully staffed Security Operations Center and several layers of security controls.
Small businesses have consistently lagged behind in adopting robust information security practices despite the fact that 43% of attacks target them. This enables malicious actors to compromise smaller third parties and either steal data entrusted to them, or hijack their access to sensitive systems at larger organizations. Third-party data breaches can be extremely damaging and can result in millions of dollars in fines, legal fees and penalties -- along with inordinate reputational damage.
Third-party data breaches have become far more common in recent years. As the world economy becomes more integrated, data often flows throughout supply chains with little regard for its protection or how it is managed. This has resulted in a “wild west” approach to applying information security controls, as many organizations have little to no idea where their data is throughout the extended supply chain -- much less what security measures are being taken to protect it.
In March 2022, the U.S.-based identity and access management platform Okta acknowledged that an attack against a third-party vendor they used resulted in a data breach impacting approximately 2.5% of their customer base. According to Okta, the damage was limited to permissions that third-party support engineers have on their platform. The ransomware group responsible for the attack, LAPSUS$, had the potential to access:
Lists of Users
Reset multi-factor authentication
Attacks against critical players in the supply chain ecosystem have escalated in recent years as malicious actors have increasingly pursued a strategy of leveraging one successful attack to damage companies throughout the software supply chain. Cybersecurity companies can be particularly at risk due to their privileged access to other organizations’ IT environments. For more information about the OKTA breach, we recommend reading our blog on four questions you should answer to determine if you are ready for third-party incident response.
On February 28, 2022, Toyota announced that the company was suspending operations on all 28 production lines at 14 manufacturing plants in Japan for a day due to a system failure at a supplier, Kojima Industries. Other Toyota partners, including Hino Motors and Daihatsu Motor, were also affected by the shutdown. The cause of the system failure at Kojima appeared to be a cyberattack that prevented communications with Toyota and production monitoring systems. On March 1, Toyota announced that they were resuming operations for only the first production shift starting March 2.
In December of 2021 security researchers announced the discovery of CVE-2021-44228, Apache Log4j Java-based logging library. The Log4j vulnerability allows unauthenticated remote code execution and access to servers – in effect, a complete takeover of vulnerable systems. Log4J opened up a massive risk throughout the third-party software ecosystem.
Even though a patch was released by Apache within days, many organizations are reliant on third, fourth, and Nth parties that may have neglected to quickly patch, or been unaware that they were affected. Prevalent put together a list of 8 questions to ask third parties to reduce the risks of being affected by a third-party data breach enabled by Log4J.
8 Steps to a Third-Party Incident Response Plan
When one of your critical vendors is breached, being ready with a prescriptive incident response plan is essential to preventing your company from becoming the next victim.
Remote Monitoring & Management software attacks have become a primary concern for many IT teams and Managed Services Providers. On July 2, 2021, Kaseya announced that attackers had taken advantage of a vulnerability in the company's VSA software to stage a ransomware attack against Kaseya’s customers. Dozens of IT service providers and hundreds of downstream customers were affected resulting in millions of dollars worth of damages.
Like the SolarWinds Orion breach and other recent third-party cyber security incidents, this is another example of the potential exponential impact of supply chain attacks on the extended supply chain.
Mercedes-Benz announced in June 2021 that approximately 1.6 million unique records were leaked through a third-party vendor's cloud storage platform. An eternal cybersecurity researcher reportedly found the flaw and notified Mercedes-Benz of the incident. According to Mercedes-Benz, less than 1,000 customers had sensitive information like social security numbers and drivers license information leaked.
The car manufacturer disclosed the breach on Thursday, June 24th. It appears that potential buyer and customer information was leaked from filling out information on Mercedes-Benz websites between January 1, 2014 through June 19, 2017. Any individual seeking to access these files would need to implement “special software programs and tools” to find the information leaked. The company announced that the security flaw has been remediated and plugged.
Possibly leaked data included:
Driver's license numbers
Social Security numbers
Credit card information
First and last name
Purchased vehicle information
Over 3.3 million customers were impacted in a data breach of car manufacturer Volkswagen announced in June 2021. Current and prospective customers' information was left exposed online between August 2019 and May 2021. According to Volkswagen, they were alerted that an unauthorized third party may have accessed the customer information on March 10, 2020.
Possibly exposed data included:
First and last name
Vehicle ID numbers makes, models, years, and colors
Healthcare billing and IT solutions vendor PracticeMax announced that it was the victim of a ransomware attack that occurred between April 17 and May 5, 2021. PracticeMax is a business associate of healthcare organizations Humana and Anthem. During the breach, an unauthorized actor accessed and stole more than 4,000 Humana patient files containing protected health information (PHI).
The SolarWinds supply chain breach, first reported in December of 2020, impacted over 18,000 users of its Orion network management product. The SolarWinds supply chain breach continues to wreak havoc on Orion customers around the world, as they continue to identify and mitigate its risks. The list of impacted companies includes major US government agencies and firms:
Department of Energy
Department of the Treasury
Department of Commerce
State and local governments
Department of State
Department of Homeland Security
National Institutes of Health
The Department of Defense
Private companies affected by the breach include Microsoft and FireEye. This security incident dealt a major blow to US national security that revealed major flaws in cybersecurity defenses. Recognizing the potentially damaging impact on companies’ operations, Prevalent released a free event and incident management assessment to its customers soon after the breach was first reported.
Navigating the Vendor Risk Lifecycle: Keys to Success
This complimentary guide details best practices for successfully managing risk throughout the vendor lifecycle. See what we've learned in our 15+ years of experience working with hundreds of customers.
In 2019, Capital One reported a data breach affecting over 100 million customers and involving data going back a decade. The Office of the Comptroller of the Currency cited the failure “to establish effective risk assessment processes” before moving IT infrastructure and data to the public cloud as one of the principal causes of the breach. Capital One was fined over $80,000,000 for the breach. Data compromised included:
Social Security Numbers
Bank Account Numbers
Customer Credit Scores
The 2020 GE breach shows that a security incident can harm not only customer relationships, but also employee relationships and trust in the company. General Electric’s human resources document management provider, Canon Business Process Service, suffered a breach at the beginning of 2020. Over 200,000 current and former employees' sensitive information, including benefits and personal health information (PHI), and more were exposed in the incident.
The personal information released includes:
Social Security Numbers
Bank account information
Date of birth
Direct deposit forms
Death certificates, medical child support orders, tax withholding forms, beneficiary designation forms and applications for benefits such as retirement, severance and death benefits with related forms and documents were also exposed.
In 2019, over 7 million Adobe Creative Cloud user records were exposed because an internal Elasticsearch database was left exposed online without password protection. The information included usernames and customer account information but not financial data or user passwords.
Other information exposed included:
User email addresses
Adobe member IDs
Country of origin
Adobe products used
Account creation date
Last login date
Although the breach did not include user credentials like names, passwords or financial information, the incident still posed harm to users. Hackers using spear phishing techniques can email high-value accounts, obtain passwords, and sell them on the dark web. Any breach of customer information, no matter how small, can pose enormous risks.
When Marriott acquired Starwood in 2016, the company inherited a compromised reservation system platform that resulted in lawsuits and reputational damage after the breach was announced in 2018. Malicious actors had direct access to Starwood’s networks and systems since 2014. The attackers maintained access to Starwood systems until the breach’s discovery and disclosure in 2018.
The malicious actors stole information on up to 500 million guests, including:
Encrypted credit card details
In 2020, Marriott announced a second breach, which affected over 5 million customer accounts and compromised addresses, birthdays, phone numbers, and loyalty card information. This third-party data leak was caused because two Marriott franchise owners had their corporate access to systems stolen. It is important to monitor any third parties who have access to your business infrastructure information, even if this is a partner organization like a franchisee. Franchisees frequently may not adhere to the same cybersecurity requirements as their parent company, exposing the entire organization to risk.
In 2013, major retailer Target was hacked by cyber attackers compromising the data of over 70 million consumers. During this seminal third-party breach, one of Target's HVAC contractors was the victim of a spear-phishing attack that leaked credit card numbers, security codes, phone numbers, and full names.
The hackers accessed Target’s corporate network with stolen credentials and installed malware on Target’s POS devices. The installed malware collected sensitive customer data between November and December of 2013. The Target breach provides a clear example of how even the best-funded information security programs can easily be compromised via security exposures in third-party products and services.
Many organizations fail to build their third-party contracts with vendor risk management in mind. Your organization should have clear company policies regarding when personal information, customer data, or other sensitive information can be shared with third parties. For example, you might want to consider including clear stipulations regarding when confidential information can be shared with fourth parties and beyond.
Vendors should be monitored for unauthorized access to personal data or other proprietary information. Even if the vendor isn’t acting maliciously, their IT systems could have been compromised resulting in malware spreading to your organization’s systems. Any vendor with any access to your IT assets should be monitored for the duration of access.
In addition, you should practice proactive, external third-party monitoring for all vendors that deal with your confidential information. Organizations change their information security programs over time, and what was originally reported on their vendor risk assessment questionnaire may not hold true a few months later. Additionally, a proactive monitoring approach can help you to catch potential data breaches before they happen. By monitoring the dark web, pastebin and other areas where stolen credentials are posted, you can learn if one of your vendors has been compromised.
Third-party risk management software can dramatically simplify your TPRM workflow and enable you to get easy visualization of how your data is being shared and used across your vendor network. Prevalent’s TPRM software makes it easy to build standardized vendor risk assessment questionnaires, centralize vendor data, and compare vendors based on risk.
Information security and data privacy regulations have been ramped up dramatically in the past decade. We’ve seen the introduction of GDPR, CCPA, NY Shield Act, and dozens of other compliance requirements in just the past few years. It is highly likely that regulatory scrutiny will continue to mount as new third-party breaches emerge.
Third-party risk assessment questionnaires can be enormously helpful in determining whether vendors are taking appropriate information security measures. However, in some cases, you may want to consider requiring potential vendors to become certified against an information security standard. For example, the Department of Defense recently propagated the Cybersecurity Maturity Model Certification. This regulation required contractors working with the Department of Defense to be certified against a 5-tier standard set by DOD determined by the type of information the contractor is working with.
Your organization can take a similar approach in dealing with vendor cybersecurity concerns. For many vendors, particularly those not dealing with large amounts of confidential data, a simple vendor risk assessment questionnaire might suffice. However, for vendors that need access to proprietary data and systems, you might want to consider requiring compliance against an outside standard such as SOC2 or NIST CSF.
Wondering how prepared your organization is for a third-party data breach? Get started with our 10-question risk calculator. For a custom benchmarking report on your third-party risk management program, request a free TPRM maturity assessment and consulting session. Interested in how Prevalent can help? Read more about our third-party risk management platform and vendor risk assessment services, or request a demo.