{"id":90008,"date":"2019-10-16T09:00:54","date_gmt":"2019-10-16T16:00:54","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/\/?p=90008"},"modified":"2023-05-15T23:02:40","modified_gmt":"2023-05-16T06:02:40","slug":"guarding-against-supply-chain-attacks-part-1-big-picture","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2019\/10\/16\/guarding-against-supply-chain-attacks-part-1-big-picture\/","title":{"rendered":"Guarding against supply chain attacks\u2014Part 1: The big picture"},"content":{"rendered":"
Every day, somewhere in the world, governments, businesses, educational organizations, and individuals are hacked. Precious data is stolen or held for ransom, and the wheels of \u201cbusiness-as-usual\u201d grind to a halt. These criminal acts are expected to cost more than $2 trillion in 2019,<\/a> a four-fold increase in just four years. The seeds that bloom into these business disasters are often planted in both hardware and software systems created in various steps of your supply chain, propagated by bad actors and out-of-date business practices.<\/p>\n These compromises in the safety and integrity of your supply chain can threaten the success of your business, no matter the size of your operation. But typically, the longer your supply chain, the higher the risk for attack, because of all the supply sources in play.<\/p>\n In this blog series, \u201cGuarding against supply chain attacks,\u201d we examine various components of the supply chain, the vulnerabilities they present, and how to protect yourself from them.<\/p>\n Supply chain attacks are not new. The National Institute of Standards and Technology (NIST) has been focused on driving awareness in this space since 2008. And this problem is not going away. In 2017 and 2018, according to Symantec, supply chain attacks rose 78 percent<\/a>. Mitigating this type of third-party risk has become a major board issue as executives now understand that partner and supplier relationships pose fundamental challenges to businesses of all sizes and verticals.<\/p>\n Moreover, for compliance reasons, third-party risk also continues to be a focus. In New York State<\/a>, Nebraska<\/a>, and elsewhere in the U.S., third-party risk has emerged as a significant compliance issue.<\/p>\n Throughout the supply chain, hackers look for weaknesses that they can exploit. Hardware, software, people, processes, vendors\u2014all of it is fair game. At its core, attackers are looking to break trust mechanisms, including the trust that businesses naturally have for their suppliers. Hackers hide their bad intentions behind the shield of trust a supplier has built with their customers over time and look for the weakest, most vulnerable place to gain entry, so they can do their worst.<\/p>\n According to NIST, cyber supply chain risks<\/a> include:<\/p>\n Cyber Supply Chain Risk Management (C-SCRM) identifies what the risks are and where they come from, assesses past damage and ongoing and future risk, and mitigates these risks across the entire lifetime of every system.<\/p>\n This process examines:<\/p>\n The NIST approach to C-SCRM considers how foundational practices and risk are managed across the whole organization.<\/p>\n The following are examples of sources of recent supply chain attacks:<\/p>\n Hardware component attacks<\/strong>\u2014When you think about it, OEMs are among the most logical places in a supply chain which an adversary will likely try to insert vulnerabilities. Moreover, these vulnerabilities can be inserted into the end product via physical access as a physical component is being transported or delivered, during pre-production access in a factory or manufacturing facility, via a technical insertion point, or other means.<\/p>\n Software component attacks<\/strong>\u2014Again in 2016, Chinese hackers purportedly attacked TeamViewer software<\/a>, which was a potential virtual invitation to view and access information on the computers of millions of people all over the world who use this program.<\/p>\n People perpetrated attacks<\/strong>\u2014People are a common connector between the various steps and entities in any supply chain and are subject to the influence of corrupting forces. Nation-states or other \u201ccause-related\u201d organizations prey on people susceptible to bribery and blackmail. In 2016, the Indian tech giant, Wipro, had three employees arrested in a suspected security breach of customer records for the U.K. company TalkTalk.<\/p>\n Business processes<\/strong>\u2014Business practices (including services), both upstream and downstream, are also examples of vulnerable sources of infiltration. For example, Monster.com experienced an exposed database<\/a> when one of its customers did not adequately protect a web server storing resumes, which contain emails and physical addresses, along with other personal information, including immigration records. This and other issues can be avoided if typical business practices such as risk profiling and assessment services are in place and are regularly reviewed to make sure they comply with changing security and privacy requirements. This includes policies for \u201cbring your own\u201d IoT devices, which are another fast-growing vulnerability.<\/p>\n Here\u2019s some practical advice to take into consideration:<\/p>\n Watch out for copycat attacks<\/strong>\u2014If a data heist worked with one corporate victim, it\u2019s likely to work with another. This means once a new weapon is introduced into the supply chain, it is likely to be re-used\u2014in some cases, for years.<\/p>\n To prove the point, here are some of the many examples of cybercrimes that reuse code stolen from legal hackers and deployed by criminals.<\/p>\n Crafting a successful cyberattack from scratch is not a simple undertaking. It requires technical know-how, resources to create or acquire new working exploits, and the technique to then deliver the exploit, to ensure that it operates as intended, and then to successfully remove information or data from a target.<\/p>\n It\u2019s much easier to take a successful exploit and simply recycle it\u2014saving development and testing costs, as well as the costs that come from targeting known soft targets (e.g., avoiding known defenses that may detect it). We advise you to stay in the know about past attacks, as any one of them may come your way. Just ask yourself: Would your company survive a similar attack? If the answer is no\u2014or even maybe\u2014then fix your vulnerabilities or at the very least make sure you have mitigation in place.<\/p>\n Know your supply chain<\/strong>\u2014Like many information and operational technology businesses, you probably depend on a global system of suppliers. But do you know where the various technology components of your business come from? Who makes the hardware you use\u2014and where do the parts to make that hardware come from? Your software? Have you examined how your business practices and those of your suppliers keep you safe from bad actors with a financial interest in undermining the most basic components of your business? Take some time to look at these questions and see how you\u2019d score yourself and your suppliers.<\/p>\n Hopefully, the above information will encourage (if not convince) you to take a big picture look at who and what your supply chain consists of and make sure that you have defenses in place that will protect you from all the known attacks that play out in cyberspace each day.<\/p>\n In the remainder of the \u201cGuarding against supply chain attacks\u201d series, we\u2019ll drill down into supply chain components to help make you aware of potential vulnerabilities and supply advice to help you protect your company from attack.<\/p>\n Stay tuned for these upcoming posts:<\/p>\n In the meantime, bookmark the Security blog<\/a> to keep up with our expert coverage on security matters. Also, follow us at @MSFTSecurity<\/a> for the latest news and updates on cybersecurity.<\/p>\nDefining the problem<\/h3>\n
\n
\n
Examples of past supply chain attacks<\/h3>\n
Big picture practical advice<\/h3>\n
\n
Looking ahead<\/h3>\n
\n