Skip to main content

Requirements Checklist Integrated Mapping

Purpose of this document

This document complies with ISO/IEC 5230 (license compliance) and ISO/IEC 18974 (security assurance). It is a compass for the entire project that integrates self-certification checklist items from both standards into one mapping table.

Every agent's CLAUDE.md refers to this document and produces output that meets certain standard requirements. Find out which module creates it.

How to read this document

  1. Comparison table of two standards → First understand the purpose and scope of each standard
  2. Integrated mapping → Check the proving materials, output, and agent in charge in the item block for each G1~G4 group.
  3. Tag → Quickly understand the nature of each item with [Common] [5230] [18974] [Supply Chain] [Regulation]
  4. Summary statistics → Check the overall status in numbers at the bottom of the document

Compare two standards

ItemISO/IEC 5230ISO/IEC 18974
Official nameOpenChain License ComplianceOpenChain Security Assurance
Latest version2.1 (2023)1.0 (2023)
PurposeEstablishment of an open source license compliance systemEstablishment of an open source security vulnerability assurance system
FocusFulfill license obligations, manage BOM, create noticesIdentifying, tracking and responding to known CVEs, SBOM based security
Key RequirementsPolicy, Organization, Process, BOM, Compliance Deliverables, Contribution Policy, Declaration of CompliancePolicy, Organization, SBOM, CVE Scan, vulnerability Tracking/Scoring/Response, Declaration of Compliance
Authentication MethodOpenChain Website self-declarationOpenChain Website self-declaration
Validity Period18 months18 months
Related regulations/standardsSPDX, REUSE, EU CRA (licensing aspect)EO 14028, NTIA SBOM, EU CRA, NVD/CVSS
ComplementarityShare common base (policy, organization, SBOM), add license-specific requirementsShare common base, add security-specific requirements

Key Insights: The two standards share common ground in the areas of policy, organization, education, and SBOM. Building one automatically fulfills half of the other.


Remarks Column notation rules

Tagsmeaning
[Common]Required by both standards
[5230]ISO/IEC 5230 only
[18974]ISO/IEC 18974 only (security specialized)
[Supply Chain]Software supply chain security related
[Regulation]International regulatory linkage items (EO 14028, EU CRA, NTIA SBOM)

Integrated mapping

G1: Program-based


G1.1 — Establishing and documenting open source policies [Common]

ISO/IEC 5230 §3.1.1 · ISO/IEC 18974 §4.1.1

Systematic compliance cannot be established without policy; The basis for all activities

Proof IDContentoutput file
5230 §3.1.1.1 · 18974 §4.1.1.1Documented open source policyoutput/policy/oss-policy.md
5230 §3.1.1.2 · 18974 §4.1.1.2Policy dissemination procedureoutput/training/curriculum.md
  • Agent in Charge: 03-policy-generator

G1.2 — Establish a review process for security assurance policies [18974]

ISO/IEC 18974 §4.1.1

18974 further requires a regular review process to ensure policies and methods of communication are always up to date.

Proof IDContentoutput file
18974 §4.1.1.1Documented security assurance policy (including review process)output/policy/oss-policy.md
18974 §4.1.2.5Periodic review and evidence of changeoutput/conformance/gap-analysis.md
  • Agent in Charge: 03-policy-generator

G1.3 — Designation of open source contact persons and organizations [Common]

ISO/IEC 5230 §3.1.2 · ISO/IEC 18974 §4.1.2

Without a clear sense of responsibility, a decision-making vacuum arises.

Proof IDContentoutput file
5230 §3.1.2.1 · 18974 §4.1.2.1List of Roles and Responsibilitiesoutput/organization/raci-matrix.md
5230 §3.1.2.2 · 18974 §4.1.2.2Competency technical documentation for each roleoutput/organization/role-definition.md
18974 §4.1.2.3Participant list and rolesoutput/organization/role-definition.md
5230 §3.1.2.3 · 18974 §4.1.2.4Competency Assessment Evidenceoutput/training/completion-tracker.md
18974 §4.1.2.5Periodic review and evidence of process changes ⚠️output/conformance/gap-analysis.md
18974 §4.1.2.6Internal best practice alignment verification ⚠️output/conformance/gap-analysis.md

⚠️ §4.1.2.5 · §4.1.2.6 Processing upon initial certification: At first certification, there is no review history, so it is processed as partially satisfied (🔶). Record “review cycle plan” and “designation of person in charge” in gap-analysis.md and meet with actual history upon renewal after 18 months.

  • Agent in Charge: 02-organization-designer

G1.4 — Establishing a training program [Common]

ISO/IEC 5230 §3.1.2 · ISO/IEC 18974 §4.1.2 (education and training aspects)

Securing and continuously maintaining staff capacity; All standards require proof of training completion

Proof IDContentoutput file
5230 §3.1.2.1 · 18974 §4.1.2.1List of Roles and Responsibilitiesoutput/organization/raci-matrix.md
5230 §3.1.2.3 · 18974 §4.1.2.4Competency Assessment Evidenceoutput/training/completion-tracker.md
  • Agent in Charge: 06-training-manager

G1.5 — Program scope definition [Common]

ISO/IEC 5230 §3.1.4 · ISO/IEC 18974 §4.1.4

Efficient resource allocation possible by clarifying target software/products

Proof IDContentoutput file
5230 §3.1.4.1 · 18974 §4.1.4.1Program Scope and Limitations Documentoutput/policy/oss-policy.md
18974 §4.1.4.2Performance Metricsoutput/policy/oss-policy.md
18974 §4.1.4.3Evidence of continuous improvement ⚠️output/conformance/gap-analysis.md

⚠️ §4.1.4.3 Processing upon initial certification: There is no history of improvement upon first certification. The initial gap analysis execution itself is recorded in gap-analysis.md as a one-time audit history, and when renewed after 18 months, the history is satisfied at least twice.

  • Agent in Charge: 03-policy-generator

G1.6 — Establish procedures for review of license obligations [5230]

ISO/IEC 5230 §3.1.5

Prevent license violations before distribution; Copyleft Source code disclosure obligation, etc.

Proof IDContentoutput file
5230 §3.1.5.1Procedures for reviewing and recording obligations, restrictions, and rights for each identified licenseoutput/process/usage-approval.md
  • Agent in charge: 04-process-designer

G1.7 — Program Participant Recognition Record [Common]

ISO/IEC 5230 §3.1.3 · ISO/IEC 18974 §4.1.3

Individually document whether each person in each role understands the policies, goals, and ways to contribute; Key supporting information during audits

Proof IDContentoutput file
5230 §3.1.3.1 · 18974 §4.1.3.1Evidence assessing participant perceptions of program goals, ways to contribute, and impact of non-complianceoutput/training/completion-tracker.md
  • Agent in charge: 06-training-manager

G2: Define and support relevant tasks


G2.1 — Establishing Roles and Responsibilities (RACI) [Common]

ISO/IEC 5230 §3.2.2 · ISO/IEC 18974 §4.2.2

Clarification of open source activity subject, approval, and review system; Prevent work gaps

Proof IDContentoutput file
5230 §3.2.2.1 · 18974 §4.2.2.1Role Owner/Group/Job Name Documentoutput/organization/raci-matrix.md
5230 §3.2.2.2 · 18974 §4.2.2.2Ensure role placement and budget adequacyoutput/organization/raci-matrix.md
5230 §3.2.2.3How to Approach License Compliance Legal Adviceoutput/organization/role-definition.md
5230 §3.2.2.4 · 18974 §4.2.2.4Internal Responsibility Assignment Processoutput/organization/raci-matrix.md
5230 §3.2.2.5License Non-Compliance Case Review and Correction Procedureoutput/process/usage-approval.md, output/process/distribution-checklist.md
18974 §4.2.2.3Specify available expertise to address vulnerabilitiesoutput/organization/role-definition.md
  • Agent in charge: 02-organization-designer

G2.2 — Operation of channels for receiving external inquiries [Common]

ISO/IEC 5230 §3.2.1 · ISO/IEC 18974 §4.2.1

Official channel obligations to request fulfillment of license obligations and report security vulnerabilities

Proof IDContentoutput file
5230 §3.2.1.1 · 18974 §4.2.1.1Public channel for third parties to make inquiriesoutput/organization/role-definition.md
5230 §3.2.1.2 · 18974 §4.2.1.2Internal response procedures for third party inquiriesoutput/process/inquiry-response.md, output/process/vulnerability-response.md
  • Agent in charge: 02-organization-designer

G2.3 — Operating awareness-raising programs [Common]

ISO/IEC 5230 §3.1.3 · ISO/IEC 18974 §4.1.3

Effectiveness of compliance is ensured when all members know and follow the policy.

Proof IDContentoutput file
5230 §3.1.3.1 · 18974 §4.1.3.1Evidence of participant perception assessment (including goals, contributions and impact of non-compliance)output/training/resources.md, output/training/completion-tracker.md
  • Agent in charge: 06-training-manager

G3-L: License compliance (ISO/IEC 5230 focused)


G3L.1 — License Identification and Classification [5230]

ISO/IEC 5230 §3.3.1 · §3.3.2

Identify license status for each SBOM-based component; Copyleft risk identification

Proof IDContentoutput file
5230 §3.3.1.1SBOM Identification, tracking, review, approval, and storage proceduresoutput/process/usage-approval.md
5230 §3.3.1.2Component Records (Proof of Procedural Compliance)output/sbom/[project].cdx.json
5230 §3.3.2.1Licensing Use Case Processing Procedureoutput/sbom/license-report.md, output/sbom/copyleft-risk.md
  • Agent in Charge: 05-sbom-analyst

G3L.2 — Fulfillment of License Obligations [5230]

ISO/IEC 5230 §3.3.2

Fulfillment of copyleft license obligations such as GPL, LGPL, AGPL, etc.; Manage permitted license list

Proof IDContentoutput file
5230 §3.3.2.1License use case handling procedure for each open source componentoutput/process/distribution-checklist.md, output/policy/license-allowlist.md
  • Agent in Charge: 04-process-designer

G3L.3 — Generate compliance artifacts [5230]

ISO/IEC 5230 §3.4.1

Obligation to provide files proving the fulfillment of legal obligations, such as notices and source codes, when distributing

Proof IDContentoutput file
5230 §3.4.1.1Compliance deliverable preparation and distribution proceduresoutput/sbom/license-report.md
5230 §3.4.1.2Compliance deliverable storage procedures and performance recordsoutput/sbom/license-report.md
  • Agent in Charge: 05-sbom-analyst

G3L.4 — Establishing an open source contribution policy [5230]

ISO/IEC 5230 §3.5.1

Prevents IP leakage and license contamination risks when contributing upstream

Proof IDContentoutput file
5230 §3.5.1.1Open source contribution policyoutput/policy/oss-policy.md
5230 §3.5.1.3Contribution Policy Recognition Procedureoutput/training/curriculum.md
  • Agent in Charge: 03-policy-generator

G3L.5 — Process for Verifying Satisfaction of License Obligations [5230]

ISO/IEC 5230 §3.4.1

Verification that all license obligations (source code disclosure, inclusion of notices, etc.) have actually been fulfilled prior to distribution; Acts as a deployment approval gateway

Proof IDContentoutput file
5230 §3.4.1.1Compliance deliverable preparation and distribution proceduresoutput/process/distribution-checklist.md
5230 §3.4.1.2Compliance deliverable storage procedures and performance recordsoutput/process/distribution-checklist.md
  • Agent in Charge: 04-process-designer

G3L.6 — Open source contribution process operation [5230]

ISO/IEC 5230 §3.5.1

Specific procedures for implementing the policy (G3L.4); Contribution review, approval, and submission workflow; Policy alone cannot control actual contributions

Proof IDContentoutput file
5230 §3.5.1.2Open source contribution management processoutput/policy/oss-policy.md, output/process/contribution-process.md (conditional)
  • Agent in charge: 03-policy-generator, 04-process-designer (conditional)

G3-S: Security assurance (based on ISO/IEC 18974)


G3S.1 — Identification of known vulnerabilities (CVE scan) [18974]

ISO/IEC 18974 §4.3.2 · §4.1.5

Risk of security incidents and legal liability if CVE vulnerabilities are not identified; EO 14028 Requirements

Proof IDContentoutput file
18974 §4.1.5.1Standard vulnerability response procedures, including vulnerability detection methodsoutput/process/vulnerability-response.md
18974 §4.3.2.1vulnerability detection and resolution proceduresoutput/vulnerability/cve-report.md
18974 §4.3.2.2Record of vulnerabilities and actions takenoutput/vulnerability/cve-report.md
  • Agent in Charge: 05-vulnerability-analyst

G3S.2 — vulnerability Tracking and Health Management [18974]

ISO/IEC 18974 §4.3.2 · §4.1.5

Continuous tracking of identified vulnerabilities until response is completed; Prevention of omission and neglect

Proof IDContentoutput file
18974 §4.1.5.1Standard response procedures, including how to follow up on vulnerabilitiesoutput/process/vulnerability-response.md
18974 §4.3.2.1vulnerability detection and resolution proceduresoutput/vulnerability/cve-report.md
18974 §4.3.2.2Record of vulnerabilities and actions takenoutput/vulnerability/cve-report.md
  • Agent in Charge: 05-vulnerability-analyst

G3S.3 — CVE Risk Score Assessment (CVSS) [18974]

ISO/IEC 18974 §4.3.2

CVSS score-based prioritization; Efficient resource allocation

Proof IDContentoutput file
18974 §4.3.2.1vulnerability handling procedures, including risk/impact score assignmentoutput/vulnerability/cve-report.md
18974 §4.3.2.2Record identified vulnerabilities and risk scoresoutput/vulnerability/cve-report.md
  • Agent in Charge: 05-vulnerability-analyst

G3S.4 — vulnerability response and patching procedures [18974]

ISO/IEC 18974 §4.3.2 · §4.1.5

Rapid patch, upgrade, and mitigation action system for discovered vulnerabilities

Proof IDContentoutput file
18974 §4.1.5.1Standard response procedures, including appropriate action methods for each risk leveloutput/vulnerability/remediation-plan.md
18974 §4.3.2.1vulnerability remediation proceduresoutput/vulnerability/remediation-plan.md
18974 §4.3.2.2Records of actions takenoutput/vulnerability/remediation-plan.md
  • Agent in Charge: 05-vulnerability-analyst

G3S.5 — Security Artifact Deployment Process [18974,supply chain]

ISO/IEC 18974 §4.3.1

SBOM·Formal procedures for delivering security outputs such as CVE reports to supply chain partners and customers; Response to EO 14028·EU CRA disclosure obligation

Proof IDContentoutput file
18974 §4.3.1.1SBOM Continuous recording procedures throughout the supplied software life cycleoutput/sbom/sbom-sharing-template.md
18974 §4.3.1.2Component Records (Proof of Procedural Compliance)output/sbom/[project].cdx.json
  • Agent in Charge: 05-sbom-management

G3S.6 — Process for ensuring security obligations are met [18974]

ISO/IEC 18974 §4.3.2

Procedures to verify that response, patch, and mitigation measures for identified and tracked vulnerabilities have actually been completed; Confirmation of actual implementation rather than formal declaration

Proof IDContentoutput file
18974 §4.3.2.1Procedures including verification of completion of vulnerability resolutionoutput/vulnerability/remediation-plan.md
18974 §4.3.2.2Action Completion Recordoutput/vulnerability/remediation-plan.md
  • Agent in charge: 05-vulnerability-analyst

G3-B: SBOM and supply chain (common)


G3B.1 — create SBOM (CycloneDX/SPDX)[Common,supply chain]

ISO/IEC 5230 §3.3.1 · ISO/IEC 18974 §4.3.1

Starting point for ensuring component transparency; Inputs for both license and security analysis

Proof IDContentoutput file
5230 §3.3.1.1 · 18974 §4.3.1.1SBOM Identification, tracking, review, approval, and storage proceduresoutput/sbom/sbom-commands.sh
5230 §3.3.1.2 · 18974 §4.3.1.2Component Records (Proof of Procedural Compliance)output/sbom/[project].cdx.json
  • Agent in Charge: 05-sbom-guide

G3B.2 — SBOM Management and Maintenance [Common,supply chain]

ISO/IEC 5230 §3.3.1 · ISO/IEC 18974 §4.3.1

Maintain SBOM up-to-date when released/updated; Configuration management integration

Proof IDContentoutput file
5230 §3.3.1.1 · 18974 §4.3.1.1SBOM Life Cycle Management Procedureoutput/sbom/sbom-management-plan.md
5230 §3.3.1.2 · 18974 §4.3.1.2Latest component historyoutput/sbom/[project].cdx.json
  • Agent in charge: 05-sbom-management

G3B.3 — SBOM Share (Supply Chain Partner)[Supply chain,regulation]

ISO/IEC 18974 §4.3.1

Transparency down the supply chain; NTIA·Response to EU CRA supply chain disclosure obligation

Proof IDContentoutput file
18974 §4.3.1.1Life cycle recording procedures, including sharing SBOM with supply chain partnersoutput/sbom/sbom-sharing-template.md
18974 §4.3.1.2Component Historyoutput/sbom/[project].cdx.json
  • Agent in charge: 05-sbom-management

G3B.4 — Continuous monitoring of supply chain vulnerabilities [Supply Chain]

ISO/IEC 18974 §4.3.2

Immediately identify affected supply chain components when a new CVE is disclosed

Proof IDContentoutput file
18974 §4.3.2.1Response procedures including new vulnerability analysis methods after releaseoutput/sbom/sbom-management-plan.md
18974 §4.3.2.2vulnerability and Action Logoutput/sbom/sbom-management-plan.md
  • Agent in Charge: 05-sbom-management

G4: Declaring and maintaining compliance


G4.1 — ISO/IEC 5230 self-certification declaration [5230]

ISO/IEC 5230 §3.6.1

Official declaration of license compliance capability; Secure supply chain partner trust

Proof IDContentoutput file
5230 §3.6.1.1Confirmation that the program in §3.1.4 meets all requirements of this specificationoutput/conformance/declaration-draft.md
  • Agent in charge: 07-conformance-preparer

G4.2 — ISO/IEC 18974 self-certification declaration [18974]

ISO/IEC 18974 §4.4.1

Official declaration of security assurance capability; Proof of EO 14028 and EU CRA response

Proof IDContentoutput file
18974 §4.4.1.1Confirmation that the program in §4.1.4 meets all requirements of this specificationoutput/conformance/declaration-draft.md
  • Agent in charge: 07-conformance-preparer

G4.3 — Management of certification validity period (18 months) [Common]

ISO/IEC 5230 §3.6.2 · ISO/IEC 18974 §4.4.2

Both standards require redeclaration every 18 months; Avoid automatic expiration

Proof IDContentoutput file
5230 §3.6.2.1 · 18974 §4.4.2.1Documentation confirming that all requirements have been met within 18 months of obtaining conformityoutput/conformance/submission-guide.md
  • Agent in charge: 07-conformance-preparer

G4.4 — Regular gap analysis and policy updates [Common]

ISO/IEC 5230 §3.6.2 · ISO/IEC 18974 §4.4.2

Implementation of the system according to changes in the technological and regulatory environment; Required before renewal declaration

Proof IDContentoutput file
5230 §3.6.2.1 · 18974 §4.4.2.1Document confirming re-satisfaction of requirements after renewaloutput/conformance/gap-analysis.md
  • Agent in Charge: 07-conformance-preparer

G4.5 — Verify that distributed software has no known vulnerabilities [18974]

ISO/IEC 18974 §4.4.1 · §4.3.2

Verify and declare before distribution that there are no known vulnerabilities in externally distributed software; Practical prerequisites for declaration of certification

Proof IDContentoutput file
18974 §4.4.1.1Confirmation that deployment software requirements are fully metoutput/conformance/declaration-draft.md
18974 §4.3.2.2Record of vulnerability action completionoutput/vulnerability/cve-report.md
  • Agent in charge: 07-conformance-preparer

Summary Statistics

Categorynumber of items
ISO/IEC 5230 mapping entries20
ISO/IEC 18974 mapping entries23
Number of items common to both standards11
Number of supply chain related items ([Supply Chain] tag)5
Number of regulatory linkage items ([Regulation] tag)1
Total number of items31

Note: Common entries (11) are counted in both 5230 (20) and 18974 (23). Preparing both standards simultaneously saves approximately 35% by working on common items only once.


next steps

Self-study mode (about 1 hour)

Once you have this mapping document figured out, start creating the actual output. If the output/ folder is empty, start with the steps below.

  1. Organizational Designcd agents/02-organization-designer && claude
  2. Create Policycd agents/03-policy-generator && claude
  3. Process Designcd agents/04-process-designer && claude
  4. SBOM creationcd agents/05-sbom-guide && claude
  5. License Analysiscd agents/05-sbom-analyst && claude
  6. vulnerability Analysiscd agents/05-vulnerability-analyst && claude
  7. SBOM Management Plancd agents/05-sbom-management && claude
  8. Education Systemcd agents/06-training-manager && claude
  9. Certification Declarationcd agents/07-conformance-preparer && claude

This document contains the ISO/IEC 5230 Full and ISO/IEC 18974 Full requirements. This is the mapping standard document within the project. This file is referenced in each agent's CLAUDE.md.