Resource Integrity - Revision history

Tom: /* Context */

2025-09-06T19:05:52Z

‎Context

Tom: /* Context */

2022-05-03T05:10:18Z

‎Context

Tom: /* Context */

2022-05-03T05:09:48Z

‎Context

Tom: /* Subresource Integrity */

2022-05-03T04:36:24Z

‎Subresource Integrity

Tom: /* Subresource Integrity */

2022-05-03T04:32:02Z

‎Subresource Integrity

Tom: /* Sub Resource Integrity */

2022-05-03T04:31:03Z

‎Sub Resource Integrity

Tom: /* Solutions */

2022-05-03T04:11:18Z

‎Solutions

Tom: /* Solutions */

2022-05-03T04:10:55Z

‎Solutions

Tom: /* Context */

2022-05-03T04:10:12Z

‎Context

Tom: Created page with "==Full Title or Meme== The ability of the receiver to determine that a received resource has not be tampered with before it is used. ==Context== * Where a digital device is d..."

2022-05-03T01:07:33Z

Created page with "==Full Title or Meme== The ability of the receiver to determine that a received resource has not be tampered with before it is used. ==Context== * Where a digital device is d..."

New page

==Full Title or Meme==
The ability of the receiver to determine that a received resource has not be tampered with before it is used.

==Context==
* Where a digital device is dependent on the received resource being an exact duplicate of that produced by a trusted party, some sort of authentication code is suppled. Cryptography is used to assure that no attacker could alter the contents without the receiver detecting the alteration.
* This is also known a tamper evident protection.

==References==

[[Category: Glossary]]

@@ Line 3: / Line 3: @@
 ==Context==
-* Where a digital device is dependent on the received resource being an exact duplicate of that produced by a trusted party, some sort of authentication code is suppled. Cryptography is used to assure that no attacker could alter the contents without the receiver detecting the alteration.
+* Where a digital device is dependent on the received resource being an exact duplicate of that produced by a trusted party, some sort of  [[Authentication Code]] is supplied. Cryptography is used to assure that no attacker could alter the contents without the receiver detecting the alteration.
 * This is also known as tamper evident protection.

@@ Line 4: / Line 4: @@
 ==Context==
 * Where a digital device is dependent on the received resource being an exact duplicate of that produced by a trusted party, some sort of authentication code is suppled. Cryptography is used to assure that no attacker could alter the contents without the receiver detecting the alteration.
-* This is also known as a tamper evident protection.
+* This is also known as tamper evident protection.
 ==Problems==

@@ Line 4: / Line 4: @@
 ==Context==
 * Where a digital device is dependent on the received resource being an exact duplicate of that produced by a trusted party, some sort of authentication code is suppled. Cryptography is used to assure that no attacker could alter the contents without the receiver detecting the alteration.
-* This is also known a tamper evident protection.
+* This is also known as a tamper evident protection.
 ==Problems==
 ==Solutions==

@@ Line 11: / Line 11: @@
 ===Subresource Integrity===
-* [https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity SRI for the browser] is a security feature that enables browsers to verify that resources they fetch (for example, from a CDN) are delivered without unexpected manipulation. It works by allowing you to provide a cryptographic hash that a fetched resource must match.
+* [https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity SRI for the browser] is a security feature that enables browsers to verify that resources they fetch (for example, from a CDN) are delivered without unexpected manipulation. It works by allowing you to provide a cryptographic hash that a fetched resource must match. Using Content Delivery Networks (CDNs) to host files such as scripts and stylesheets that are shared among multiple sites can improve site performance and conserve bandwidth. However, using CDNs also comes with a risk, in that if an attacker gains control of a CDN, the attacker can inject arbitrary malicious content into files on the CDN (or replace the files completely) and thus can also potentially attack all sites that fetch files from that CDN.
 ==References==
 [[Category: Glossary]]

@@ Line 11: / Line 11: @@
 ===Subresource Integrity===
-* [https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity SRI for the browser] is
+* [https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity SRI for the browser] is a security feature that enables browsers to verify that resources they fetch (for example, from a CDN) are delivered without unexpected manipulation. It works by allowing you to provide a cryptographic hash that a fetched resource must match.
 ==References==
 [[Category: Glossary]]

@@ Line 8: / Line 8: @@
 ==Solutions==
-===Soce Signing===
+===Code Signing===
 ===Sub Resource Integrity===