<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>John Speed Meyers on</title><link>https://deploy-preview-3187--ornate-narwhal-088216.netlify.app/contributors/john-speed-meyers/</link><description>Recent content in John Speed Meyers on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Tue, 06 Oct 2020 08:50:45 +0000</lastBuildDate><atom:link href="https://deploy-preview-3187--ornate-narwhal-088216.netlify.app/contributors/john-speed-meyers/index.xml" rel="self" type="application/rss+xml"/><item><title>Selecting a Base Container Image</title><link>https://deploy-preview-3187--ornate-narwhal-088216.netlify.app/software-security/selecting-a-base-image/</link><pubDate>Thu, 04 Aug 2022 15:21:01 +0200</pubDate><guid>https://deploy-preview-3187--ornate-narwhal-088216.netlify.app/software-security/selecting-a-base-image/</guid><description>Software teams building and deploying container-based software applications often use a &amp;ldquo;base image,&amp;rdquo; an initial set of software packages often associated with a Linux distribution. Software developers, security professionals, and infrastructure teams seeking to make an informed decision about what base image to use must consider a number of criteria when selecting a base image appropriate for their needs. Base images like those provided by Chainguard are designed to meet these security criteria while maintaining compatibility.</description></item><item><title>What is software supply chain security</title><link>https://deploy-preview-3187--ornate-narwhal-088216.netlify.app/software-security/what-is-software-supply-chain-security/</link><pubDate>Thu, 04 Aug 2022 15:21:01 +0200</pubDate><guid>https://deploy-preview-3187--ornate-narwhal-088216.netlify.app/software-security/what-is-software-supply-chain-security/</guid><description>An earlier version of this material was published in the first chapter of the Linux Foundation Sigstore course.
Software producers have a supply chain just like manufacturing businesses have a supply chain. And just like manufacturers require physical inputs and then perform a manufacturing process to build a finished product, so do software producers, whether the producer is a company or individual. In other words, a software producer uses components, developed by third parties and themselves, and technologies to write, build, and distribute software.</description></item><item><title>What Makes a Good SBOM?</title><link>https://deploy-preview-3187--ornate-narwhal-088216.netlify.app/open-source/sbom/what-makes-a-good-sbom/</link><pubDate>Thu, 04 Aug 2022 15:21:01 +0200</pubDate><guid>https://deploy-preview-3187--ornate-narwhal-088216.netlify.app/open-source/sbom/what-makes-a-good-sbom/</guid><description>A software bill of materials, or an SBOM (pronounced s-bomb), is a formal record of the components contained in a piece of software. It is analogous to an ingredients list for a recipe. And it has become recognized as one of the key building blocks of software supply chain security. Proponents rightfully point out that organizations can&amp;rsquo;t secure their software if they don&amp;rsquo;t know what&amp;rsquo;s inside their software.
As awareness and adoption of SBOM has grown, there has been a gradual acknowledgement that not all SBOMs are created equal, some are more or less useful, depending on the goals of the SBOM user and the contents of the SBOM.</description></item></channel></rss>