<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Program Scope on OpenChain KWG</title><link>https://korea-wg.openchainproject.org/en/tags/program-scope/</link><description>Recent content in Program Scope on OpenChain KWG</description><generator>Hugo</generator><language>en</language><atom:link href="https://korea-wg.openchainproject.org/en/tags/program-scope/index.xml" rel="self" type="application/rss+xml"/><item><title>§3.1.4 Program Scope</title><link>https://korea-wg.openchainproject.org/en/guide/iso5230_guide/1-program-foundation/4-scope/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/iso5230_guide/1-program-foundation/4-scope/</guid><description>&lt;h2 id="1-clause-overview"&gt;1. Clause Overview&lt;/h2&gt;&#10;&lt;p&gt;If it is unclear whether the open source program applies to the entire organization or only to specific&#10;product lines or business units, the boundaries of compliance activities become vague and accountability&#10;becomes unclear. §3.1.4 requires a documented written statement that clearly defines which software,&#10;organizational units, and distribution channels the open source program applies to, and what is outside&#10;the scope. The scope may vary depending on the organization&amp;rsquo;s size and business model, and this clause&#10;requires that choice to be explicitly recorded.&lt;/p&gt;</description></item><item><title>§4.1.4 Program Scope</title><link>https://korea-wg.openchainproject.org/en/guide/iso18974_guide/1-program-foundation/4-scope/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/iso18974_guide/1-program-foundation/4-scope/</guid><description>&lt;div class="alert alert-warning" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;★ 18974 Exclusive Items — Documented Evidence Strength&lt;/div&gt;&#10;&lt;p&gt;§4.1.4.2·§4.1.4.3 are ISO 18974 exclusive (★) items requiring &lt;strong&gt;Documented Evidence&lt;/strong&gt;. Metrics must include actual measurement data; continuous improvement must retain review/audit meeting minutes. For a detailed explanation of the strength difference, see &lt;a href="https://korea-wg.openchainproject.org/en/guide/iso18974_guide/1-program-foundation/5-standard-practice/#evidence-strength-for-iso-18974-exclusive--items--documented-evidence"&gt;§4.1.5 Standard Practices — Documented Evidence Notice&lt;/a&gt;.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="1-clause-overview"&gt;1. Clause Overview&lt;/h2&gt;&#10;&lt;p&gt;§4.1.4 is the clause from ISO/IEC 5230 §3.1.4 (Program Scope) with 2 additional Verification Materials. While 5230 only requires a written statement that clearly defines the program&amp;rsquo;s scope, 18974 additionally requires a &lt;strong&gt;set of performance metrics the program seeks to improve upon (4.1.4.2)&lt;/strong&gt; and &lt;strong&gt;documented evidence from each review, update, or audit demonstrating continuous improvement (4.1.4.3)&lt;/strong&gt;. These two items are intended to demonstrate that the security assurance program is not static compliance, but a system with measurable goals that continuously improves.&lt;/p&gt;</description></item></channel></rss>