Malicious attacks on software supply chains have increased 742% since 2019. Do you have a comprehensive way to keep your applications and products safe?
We’re seeing more large-scale breaches happening through vulnerabilities in the third-party software that big organizations use. An average data breach in the US today costs $9.44 million. But in looking at the SolarWinds breach, which happened through a vulnerability in third-party technology, the costs could be much higher: More than 18,000 organizations were put at risk, with a cost of over $40 million—and an additional $26 million lawsuit settlement.
It’s more important than ever to have ways to ensure that the products you’re producing for your customers stay safe from code to cloud. One way to do that is by having a comprehensive security program to address software supply chain risk. In the same way that a manufacturer would want every step of their product’s supply chain to remain secure, so should engineers want every step of their software’s supply chain to remain secure.
Scaling your approach to security will ultimately be worth the effort, but will take action and buy-in to get there. If you’re implementing a software supply chain security program, be aware of the following challenges you may face, along with some questions to ask as you evaluate new tools and technologies to help you build that program.
COMMON SOFTWARE SUPPLY CHAIN SECURITY CHALLENGES
Challenges to your software supply chain security program can arise before you’ve even begun drafting a plan. Here are three common challenges you may face as you begin your efforts.
Challenge 1: You Don’t Own It
One of the biggest reasons why software supply chain security is needed is because you don’t really know where your raw materials are coming from. Software today isn’t written from scratch and is built with components that have already been created by third parties. The challenge is that you do not control how the third-party technologies you consume are created, so you inherit whatever’s in the code you use—from mistakes to deliberately embedded ransomware.
Focus your efforts on what you can control. Start by taking an inventory of your third-party components so that you can assess their risk and create standards for using third-party code to reduce risk in the future.
Challenge 2: You’re Outside Your Area Of Influence
If you’re in security, the software supply chain is definitely an area of concern, but not necessarily an area in which you can influence. Much of the changes that need to take place will require leadership from the software engineering team. Until they see the value of having a more comprehensive approach to security, you may find yourself sidelined.
In order to get movement on software supply chain security initiatives, you’ll need to become that influencer and convince engineers of the benefits of it and practical ways to implement it. Level up your internal marketing, security champion, and other drum-beating initiatives to get folks moving in the desired direction. Change is never easy, but in this case, it’s a necessity.
Challenge 3: You’re Already Overwhelmed
How can you lead the charge on a software supply chain security initiative when you’re already overwhelmed with all the other security needs in your organization—especially considering that there are roughly 100 software engineers for every one security engineer?
In order to free up time and energy for the effort, focus on initiatives and methods that can free up time and energy. Ramp up your automation, which can free your team up for more, higher-impact work such as championing a software supply chain security program. Don’t forget to incorporate collaboration and delegation to effectively scale your efforts as well.
4 QUESTIONS TO EVALUATE SOFTWARE SUPPLY CHAIN SECURITY TOOLS
You’ve got the buy-in, the people, the resources, and the budget to roll out a software supply chain security program. Here are a few questions to ask as you begin to evaluate the tools you need.
Question 1: Does This Tool Work With My Product Technology Stack?
Product development teams leverage a wide variety of technologies today, and software supply chain security tools do not support all with an equal level of maturity. You’ll need to test and prove that whatever tool you’re evaluating does what you need it to with the level of maturity required.
Question 2: How Are Results Disseminated To Software Engineers? DevOps? IT?
Collecting data is meaningless if you do not have the ability to act on it. Many software supply chain risks require an action to be carried out not by the security team, but by the engineering, DevOps, or IT teams. Therefore, it is paramount that the tool or platform supports your ability to reach this audience.
Question 3: How Does It Increase The Visibility Into Our Software Supply Chain?
There are a ton of moving parts within the software supply chain, including source code repositories, build servers, infrastructure as code, and container registries. Understanding the totality of your supply chain requires the automated discovery and aggregation of these moving parts, and is foundational for you to subsequently reduce risk.
Question 4: Does The Tool Provide You With Meaningful Business Context?
You’ll need to make decision after decision about identified risks within your supply chain. Unfortunately, very few reported risks lack meaningful context about the asset, its environment, and the vulnerability itself. Many SCA tools, for example, will raise an alert when a vulnerable dependency is found in your code—but is that code even deployed? Context is key to understanding risk, so look for tools that provide the information you need to make those informed decisions.
PROTECTING CUSTOMERS WITH BETTER SECURITY
Implementing a software supply chain security program will take effort, from gaining buy-in across the organization to inventorying assets to taking steps to remediate and lower risk across each step of your development process. But if you can prevent a SolarWinds-like breach for your customers, it will be worth it.
Eric Sheridan is the Chief Innovation Officer at Tromzo.