<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dave Bechberger</title>
    <description>The latest articles on DEV Community by Dave Bechberger (@bechbd).</description>
    <link>https://dev.to/bechbd</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1415348%2Fcf7609b3-b739-40c4-899a-d57adc26f35a.png</url>
      <title>DEV Community: Dave Bechberger</title>
      <link>https://dev.to/bechbd</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bechbd"/>
    <language>en</language>
    <item>
      <title>Analyzing Software Supply Chain Security with Graph Analytics</title>
      <dc:creator>Dave Bechberger</dc:creator>
      <pubDate>Tue, 09 Apr 2024 20:37:15 +0000</pubDate>
      <link>https://dev.to/bechbd/analyzing-software-supply-chain-security-with-graph-analytics-551h</link>
      <guid>https://dev.to/bechbd/analyzing-software-supply-chain-security-with-graph-analytics-551h</guid>
      <description>&lt;p&gt;If you look at XZ utils or Log4j, it has become clear that serious software vulnerabilities are not isolated incidents. &lt;br&gt;
While the origin of the issues differ, anyone who has had to track down the impact of these problems knows that finding the impact and remediating them is a time-consuming process.  Software Bill of Materials (SBOM) help with specific applications but understanding and risking the overall impact is difficult.  &lt;/p&gt;

&lt;p&gt;I have recently integrated SBOM ingestion into Nodestream to help with this problem, and allow you to gain more complete visibility into software components and dependencies.&lt;/p&gt;

&lt;p&gt;If you're interested in more details, please check out the recent blog post on &lt;a href="https://lnkd.in/dSzFpj8D"&gt;Software Vulnerability Analysis using SBOMs, Amazon Neptune, and Nodestream&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Flvlw8yda9mha0oxnituj.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Flvlw8yda9mha0oxnituj.jpeg" alt="Image description" width="565" height="425"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>database</category>
      <category>security</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
