<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integrity on Commentary of Takao</title><link>https://takao.blog/en/tags/integrity/</link><description>Recent content in Integrity on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/integrity/index.xml" rel="self" type="application/rss+xml"/><item><title>Subresource Integrity: Protecting Your CDN Dependencies</title><link>https://takao.blog/en/web/subresource-integrity/</link><pubDate>Fri, 20 Dec 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/subresource-integrity/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Subresource Integrity: Protecting Your CDN Dependencies" /&gt;&lt;p&gt;Subresource Integrity (SRI) is a security feature that lets browsers verify that resources fetched from CDNs or third-party origins have not been tampered with. In an era of supply chain attacks — the British Airways Magecart breach, the Polyfill.io compromise, and numerous CDN incidents — SRI provides cryptographic assurance that the resource your page loads is exactly what you intended.&lt;/p&gt;
&lt;h2 id="how-sri-works"&gt;How SRI Works
&lt;/h2&gt;&lt;p&gt;When you add an &lt;code&gt;integrity&lt;/code&gt; attribute to a &lt;code&gt;&amp;lt;script&amp;gt;&lt;/code&gt; or &lt;code&gt;&amp;lt;link rel=&amp;quot;stylesheet&amp;quot;&amp;gt;&lt;/code&gt; tag, the browser computes the hash of the fetched resource and compares it to the attribute value. If they don&amp;rsquo;t match, the browser refuses to execute or apply the resource.&lt;/p&gt;</description></item></channel></rss>