Download the 2020 State of the Software Supply Chain Report

Developers Are the Frontline of Software Supply Chain Attacks

Since December 17, 2020, when federal agencies and enterprises alike learned of the malicious software attack on SolarWinds’ Orion platform, some have been asking, “How do I avoid becoming the next SolarWinds?”

Exemplary development teams already lead the way, focusing on how software supply chain hygiene, governance, and security can minimize the risk from a similar style of attack that we saw at SolarWinds. Our 2020 State of the Software Supply Chain Report highlights software development trends for open source and third party components and what exemplary teams are doing to minimize the risk from a software supply chain attack similar to what we saw at SolarWinds.

FIGURE 1C Next Gen SSC Attacks 2020@4x

Understand that software supply chain attacks are on the rise.

SolarWinds isn’t the first company to experience a software supply chain attack focused on the build process. In our sixth annual State of the Software Supply Chain Report, we've documented a 430% increase in software supply chain related attacks. For instance, in May 2020, Octopus Scanner was discovered by GitHub as having IDEs injecting malicious code as part of the build process. Similarly, Gitpaste-12 leveraged trustworthy sites like GitHub and Pastebin to host itself and maliciously infect users.

FIGURE 1C Next Gen SSC Attacks 2020@4x

Understand that software supply chain attacks are on the rise.

SolarWinds isn’t the first company to experience a software supply chain attack focused on the build process. In our sixth annual State of the Software Supply Chain Report, we've documented a 430% increase in software supply chain related attacks. For instance, in May 2020, Octopus Scanner was discovered by GitHub as having IDEs injecting malicious code as part of the build process. Similarly, Gitpaste-12 leveraged trustworthy sites like GitHub and Pastebin to host itself and maliciously infect users.

Map your software supply chain to track the source of OSS packages and containers.

The average Java development organization relies on over 3,500 open source projects, including 14,000 unique component releases. The average JavaScript developer downloads 90,000 npm packages packages annually. Documenting where these projects are sourced is key to understanding who can nefariously access and alter elements of the build process.

FIGURE 5A Organizational Visibility of Supply Chain@4x

Map your software supply chain to track the source of OSS packages and containers.

The average Java development organization relies on over 3,500 open source projects, including 14,000 unique component releases. The average JavaScript developer downloads 90,000 npm packages packages annually. Documenting where these projects are sourced is key to understanding who can nefariously access and alter elements of the build process.

FIGURE 5A Organizational Visibility of Supply Chain@4x
FIGURE 3B Exemplary Dev Teams Perfomance Metrics@4x

Know that software supply chain attacks are preventable.

The State of the Software Supply Chain Report has shown how high performing software development teams have improved security outcomes. In addition to mapping their software supply chains, these teams maintain automated checks on the quality of software components and packages moving through them, and update the components to the latest releases on a regular basis. As a result, these teams update their code more often and generally stay more secure.

FIGURE 3B Exemplary Dev Teams Perfomance Metrics@4x

Know that software supply chain attacks are preventable.

The State of the Software Supply Chain Report has shown how high performing software development teams have improved security outcomes. In addition to mapping their software supply chains, these teams maintain automated checks on the quality of software components and packages moving through them, and update the components to the latest releases on a regular basis. As a result, these teams update their code more often and generally stay more secure.

Enhance Nexus Lifecycle With the Advanced Development Pack

Dev Lifecycle

 

The Advanced Development Pack allows developers to engage in proactive dependency management practices without losing the momentum of agile software development. The Advanced Development Pack makes developers’ lives easier by allowing them to:

  • Choose the best packages guided by Exemplar ratings for OSS projects
  • Avoid suspicious packages by blocking malicious OSS releases from entering production environments
  • Know what will break through simple OSS upgrades including insight into the level of effort required
  • Fix dependencies faster including single-click upgrades and guidance on when to upgrade a dependency

Save time by knowing what components to avoid from the start of a project, whether it doesn’t fit policy or is associated with abnormal commit behavior.

Dev Lifecycle

 

The Advanced Development Pack allows developers to engage in proactive dependency management practices without losing the momentum of agile software development. The Advanced Development Pack makes developers’ lives easier by allowing them to:

  • Choose the best packages guided by Exemplar ratings for OSS projects
  • Avoid suspicious packages by blocking malicious OSS releases from entering production environments
  • Know what will break through simple OSS upgrades including insight into the level of effort required
  • Fix dependencies faster including single-click upgrades and guidance on when to upgrade a dependency

Save time by knowing what components to avoid from the start of a project, whether it doesn’t fit policy or is associated with abnormal commit behavior.