SupplyChainSecurityCon hosted by CNCF + CDF 2021

The software bill of materials (SBOM) has quickly become a critical foundation for software supply chain security. Gaining the ability to see and process the full picture of all software components included in your applications is the first step in preventing vulnerabilities and malware from reaching production systems.

The recent United States Executive Order on Improving the Nation's Cybersecurity details the need for software producers to supply SBOMs, as well as maintaining controls on the provenance of software components and tools. The U.S. NTIA has subsequently released minimum elements for a compliant SBOM. This highlights the important role of an SBOM for open source projects, whether they are incorporated in software applications or used as part of the development toolchain.

Multiple Linux Foundation and CNCF projects including SPDX, In-Toto, and SigStore are providing critical frameworks and specifications designed to advance the security of the software supply chain.

This session will explore best practices for generating SBOMs for both open source projects and software producers, we will share insights and lessons learned from creating SBOMs for CNCF projects using Syft, an open source SBOM generator, and predict ways that we see the role of the SBOM in securing software supply chains evolving over time.

Several recent high-profile security incidents were due to compromised software supply chains. Software Supply Chain is a collective term used to describe the stages of software lifecycle from source to deployment through CI/CD pipelines, and all the static and dynamic analyses in between. In the world of microservices and cloud computing, trust in your company’s supply chain is critical, as most of the tooling and dependencies are from open source and vendor projects. When the code hits production, it’s essential to have enough observability to detect and investigate the problem and get to the root cause and mitigation as quickly as possible. With software supply chain attacks, not only is the newly deployed code under suspicion, but also all the tooling used to produce it becomes a potential attack vector, so an efficient and effective way to verify the integrity of the supply chain is paramount. This talk will discuss what information needs to be collected to allow DevOps to inspect and verify the integrity of the supply chain, the challenges of having the right level of detail to reduce mean-time-to-detection and mean-time-to-understanding, some of the existing solutions and open problems in this space.

As you're no doubt aware, SolarWinds was hit in December 2020 with a sophisticated supply chain attack perpetrated by nation state actors. In the months since, they've been working to create an entirely new build system based on a number of CNCF and CDF projects. In this talk, you'll learn about what they're building, why it's necessary, and what it's like to be on the inside when the unthinkable happens.

Open source is everywhere and software is eating the world. However, we now face serious challenges within the security of our software and its supply chain from code commit to production. For this talk, Luke Hinds will outline the current immediate threats and what can be done by us as a community to address the risks we face by harnessing Open Source tooling and open transparent development models.

Code signing is the security foundation of the software supply chains we rely on every day. But if you let yourself think about it for too long -- like we have -- it starts to seem weird that we’re so sure a random download won’t steal our credentials or ransom our data just because someone, somewhere happened to choose a very special point on an elliptic curve.

In this talk, we will explore what a digital signature really means -- and what it doesn’t. We’ll look at the implications of policy choices around key handling, what gets signed, and when we call a signature "valid". And we’ll dive so deeply into the very idea of identity that you may begin to question the nature of your reality.

In this talk, Steven will provide a comprehensive introduction to DevSecOps. He'll help attendees get past the buzzwords and demystify the various kinds of software security scanning that teams can incorporate into their software delivery processes to shift-left security. Equally important - you'll then learn how to apply these principles at scale using the Jenkins Templating Engine to develop tool-agnostic pipelines that can be shared across teams.

The new technologies such as cloud, containers, virtual & cloud native network functions result in tremendous advances in the telecommunications industry.
With the help of these new technologies, the 5G networks that are currently being rolled out all around the world are developed rapidly in heavily disaggregated manner, allowing communications service providers to introduce new services to their users much faster than before.

However, the new technologies and resulting disaggregation is not without their challenges and the security of the software supply chain is one of them.
The components that are part of the 5G networks originate from multiple sources, including but not limited to vendors and open source communities with many integration points and deployed into different environments such as public and private clouds, increasing the risk of breaking the chain of trust.

This session will give a short overview of the next generation telecommunications networks, highlight the challenges, and talk about the opportunities to tackle them in a collaborative manner.

The Python Package Index (PyPI) is one of the oldest software repositories for a language ecosystem and the canonical place to publish Python code. It serves more than 2 billion requests a day, and is almost entirely supported by volunteers and the non-profit Python Software Foundation.

In this talk, we'll review some recent supply-chain attack and how they relate to PyPI specifically. In addition, we'll take a look at some in-progess projects to make PyPI more resilient, secure and sustainable.

SLSA – Supply-chain Levels for Software Artifacts – introduces a comprehensive methodology to prevent tampering with the software supply chain.  To illustrate the impact of SLSA, we follow a few gremlins as they try to introduce malicious code into a container image used by thousands of projects.  At each step of the supply chain we show how SLSA controls raise the cost of attack, preventing the gremlins from causing any harm.

In this talk, we’ll explore the complementary roles that TUF, in-toto, and SigStore play in creating a transparent hack-proof software supply chain that thwarts man-in-the-middle attacks anywhere between developers and end-users. The talk will build off the basics of using in-toto and TUF together to deliver hack-proof updates, especially how it was done for the first time in the industry at Datadog, and then going the extra mile with SigStore. We’ll see how SigStore’s transparent and auditable model holds publishers accountable in this system. Finally, we’ll see a real example of the whole stack in action for the first time with Datadog’s integration, and show just how easy it is to adopt yourself!

With the explosion of interest in SBOMs, it's likely that you've just heard of a few projects for the first time -- even if those projects aren't new, they may be new to you, and you might be asking yourself, "how is X different from Y?" You might also be wondering which projects you should select in order to satisfy the requirements of the Executive Order!
As when starting out on any journey, before entering unfamiliar territory, it is important to understand the lay of the land, pack the right supplies, and get to know your traveling companions.
In this talk, a few maps of the open source supply chain landscape will be shared. Attendees will gain a sense of both the breadth and depth of the challenges ahead, and learn to identify a few essential types of tools for their journey.

If you've analyzed or responded to software vulnerabilities like BadAlloc, KRACK, or the PROTOS SNMP test suite from 2002, then you've encountered the intersection of vulnerabilities and supply chains. Without supply chain knowledge, multi-party coordinated vulnerability disclosure efforts are largely limited to manual investigation, one-offs, and guesswork. Follow-on activities like vulnerability management and risk assessment are also hindered. To what extent are vulnerabilities in upstream dependencies inherited? What happens when build tools have or create vulnerabilities? How might we effectively perform coordinated disclosure and share supply chain knowledge at scale? What part will SBOM (software bill of materials) play?

If you build software on Kubernetes and want to learn more about how to do it in a secure way, then this talk is for you! In this talk, Christie Wilson and Priya Wadhwa will provide a hands on overview to creating a secure zero-trust supply chain on Kubernetes. We'll show you how to use tools like Tekton, Tekton Chains and sigstore together to protect your pipelines and generate provenance for your builds. We'll also cover how the audience can integrate these tools with other projects like In-Toto and SPIRE to securely build, sign and verify software components today.

With the growing frequency of supply chain attacks and complexity of technology environments securing the software supply chain has never been more important, especially in highly regulated environments like banking. The road to a secure supply is long and challenging but getting started is easy. There are a series of practices that you can implement today to get you started on your supply chain security journey that will help you: better understand the technologies currently in your environments, establish provenance of source code, and help you audit and respond quickly in the event of supply chain vulnerabilities.