<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Supply Chain Security on Nalar</title>
    <link>https://nalar.dev/tags/supply-chain-security/</link>
    <description>Recent content in Supply Chain Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/supply-chain-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Subresource Integrity Pins External Assets to Expected Bytes</title>
      <link>https://nalar.dev/subresource-integrity-pins-external-assets-to-expected-bytes/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/subresource-integrity-pins-external-assets-to-expected-bytes/</guid>
      <description>&lt;h1 id=&#34;subresource-integrity-pins-external-assets-to-expected-bytes&#34;&gt;Subresource Integrity Pins External Assets to Expected Bytes&lt;/h1&gt;&#xA;&lt;p&gt;A web page can keep all of its application code under careful review and still execute JavaScript delivered from infrastructure outside its control. Analytics libraries, UI frameworks, payment components, and other dependencies are often fetched from a content delivery network. If that remote response changes, the browser normally has no basis for deciding whether the new bytes are an approved release or an unexpected substitution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Subresource Integrity Pins Browser Dependencies to Expected Bytes</title>
      <link>https://nalar.dev/subresource-integrity-pins-browser-dependencies-to-expected-bytes/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/subresource-integrity-pins-browser-dependencies-to-expected-bytes/</guid>
      <description>&lt;h1 id=&#34;subresource-integrity-pins-browser-dependencies-to-expected-bytes&#34;&gt;Subresource Integrity Pins Browser Dependencies to Expected Bytes&lt;/h1&gt;&#xA;&lt;p&gt;A production page can contain no application-side injection flaw and still execute hostile JavaScript if a trusted external asset changes underneath it. The script URL may be correct, TLS may be valid, and the browser may have reached the intended host. None of those facts establish that the returned file is the exact artifact the site operator approved.&lt;/p&gt;&#xA;&lt;p&gt;Subresource Integrity, commonly shortened to SRI, adds that missing assertion for selected browser-loaded scripts and stylesheets. An &lt;code&gt;integrity&lt;/code&gt; attribute carries one or more cryptographic digest values. After fetching the resource, the browser computes the digest of the representation used for the integrity check and refuses to apply or execute it when no supported digest matches.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
