{"id":4315,"date":"2025-10-23T09:48:06","date_gmt":"2025-10-23T09:48:06","guid":{"rendered":"https:\/\/hkm-consulting.de\/?page_id=4315"},"modified":"2025-10-23T13:19:02","modified_gmt":"2025-10-23T13:19:02","slug":"extended_bill_of_materials","status":"publish","type":"page","link":"https:\/\/hkm-consulting.de\/en\/extended_bill_of_materials\/","title":{"rendered":"Extended Bill of Materials (XBOM – Transparency across the Supply Chain)"},"content":{"rendered":"

[vc_row][vc_column][vc_column_text css=””]<\/p>\n

Transparency across the Supply Chain – Extended Bill of Materials (HBOM & SBOM)<\/h3>\n

The term XBOM<\/strong> (\u201cExtended Bill of Materials\u201d) describes an advanced approach for the systematic recording and documentation of all software<\/strong> and hardware<\/strong> components used within a product or system.<\/p>\n

It combines the established concepts of the Software Bill of Materials (SBOM)<\/strong> and the Hardware Bill of Materials (HBOM)<\/strong>, addressing the increasing regulatory and cybersecurity requirements within the European Union.<\/p>\n

XBOM serves as a key instrument for ensuring transparency across both digital and physical components.
With the growing relevance of the NIS-2 Directive<\/strong>, the Cyber Resilience Act (CRA)<\/strong>, and the Supply Chain Act<\/strong>, traceable documentation of all components is becoming a mandatory element \u2014 not only for manufacturers, but also for system integrators, operators, and service providers.<\/p>\n

 <\/p>\n

Requirements for Companies<\/strong><\/h3>\n

Organizations face the challenge of fully documenting the origin, security, and maintainability of all deployed components.
Introducing an XBOM structure supports compliance with regulatory obligations while enabling early identification of risks within the supply chain.<\/p>\n

Key Requirements:<\/strong><\/p>\n

    \n
  • \n

    Component Transparency:<\/strong>
    All hardware and software components must be identifiable \u2014 including version, origin, manufacturer, and security status.<\/p>\n<\/li>\n

  • \n

    Security Evidence:<\/strong>
    Each component requires documented evidence of security testing, certification, or known vulnerabilities.<\/p>\n<\/li>\n

  • \n

    Lifecycle Management:<\/strong>
    The XBOM must be continuously maintained and updated to reflect product changes throughout its lifecycle.<\/p>\n<\/li>\n

  • \n

    Supply Chain Responsibility:<\/strong>
    Organizations must ensure that suppliers also provide transparent documentation and report any modifications.<\/p>\n<\/li>\n

  • \n

    Data Format and Traceability:<\/strong>
    The use of internationally recognized formats such as SPDX (ISO\/IEC 5962:2021)<\/strong> or CycloneDX (ECMA-424)<\/strong> is recommended.<\/p>\n<\/li>\n<\/ul>\n

     <\/p>\n

    Necessary Steps for Implementation<\/h3>\n

    Implementing an XBOM structure requires strategic planning, clear responsibilities, and integration into existing management systems (e.g., Quality Management, Information Security Management, and IT Service Management). A practical implementation roadmap includes the following steps:<\/p>\n

      \n
    1. \n

      Inventory and Assessment<\/strong>
      Identify existing software and hardware inventories (e.g., CMDB, asset management, license management).<\/p>\n<\/li>\n

    2. \n

      Data Structuring<\/strong>
      Map components to products, systems, or services, and identify versions, dependencies, and origins.<\/p>\n<\/li>\n

    3. \n

      Format Definition<\/strong>
      Select the appropriate exchange formats (SPDX, CycloneDX) and define the required data depth and field sets.<\/p>\n<\/li>\n

    4. \n

      Process Integration<\/strong>
      Embed XBOM creation into development, procurement, and change\/release management processes.<\/p>\n<\/li>\n

    5. \n

      Automation and Maintenance<\/strong>
      Utilize tools or collectors to automatically record components and version data.
      Within the HKM Framework<\/strong>, dedicated connectors<\/strong> and collectors<\/strong> are available for this purpose.<\/p>\n<\/li>\n

    6. \n

      Verification and Compliance Evidence<\/strong>
      Conduct regular reviews of XBOM data for accuracy, completeness, and compliance with regulatory requirements.<\/p>\n<\/li>\n<\/ol>\n

       <\/p>\n

      Which Companies Must Implement the Requirements and when?<\/strong><\/h3>\n

      The implementation of XBOM increasingly affects all organizations developing, integrating, or operating digital products.
      The following sectors are directly impacted:<\/p>\n

        \n
      • \n

        Manufacturers<\/strong> of hardware, software, or combined digital products,<\/p>\n<\/li>\n

      • \n

        Service providers and operators<\/strong> of critical infrastructure under NIS-2<\/strong>,<\/p>\n<\/li>\n

      • \n

        System integrators and suppliers<\/strong> providing components for security-relevant environments,<\/p>\n<\/li>\n

      • \n

        Companies subject to reporting obligations<\/strong> under the Cyber Resilience Act (CRA)<\/strong> or the Supply Chain Act<\/strong>.<\/p>\n<\/li>\n<\/ul>\n

         <\/p>\n

        Timeline and Strategic Preparation
        \n<\/strong>The regulatory requirements arising from NIS-2<\/strong> and the Cyber Resilience Act (CRA)<\/strong> will take effect in stages, with NIS-2 applicable from October 2025<\/strong> and the main CRA obligations by December 2027<\/strong>.
        Organizations are therefore strongly advised to begin establishing an XBOM framework during 2024<\/strong>.<\/p>\n

        This early preparation enables the development of the necessary technical and organizational foundations \u2014 minimizing the risk of delays, penalties, or compliance deviations.<\/p>\n

        A review of existing management systems<\/strong> such as Quality Management (QMS)<\/strong>, Information Security Management (ISMS)<\/strong>, IT Service Management (ITSM)<\/strong>, and Data Protection Management (DSMS)<\/strong> is essential before<\/strong> integrating XBOM into the regulatory environments of CRA and NIS-2.
        This ensures that XBOM is seamlessly embedded within existing governance structures and operated as part of a coherent, standards-based management framework<\/strong>.<\/p>\n

         <\/p>\n

        Benefits of an XBOM St<\/strong>ructure \u2013 Combining SBOM and HBOM<\/strong><\/h3>\n
          \n
        • \n

          Transparency and Traceability<\/strong> across the entire supply chain<\/p>\n<\/li>\n

        • \n

          Risk Reduction<\/strong> through early identification of vulnerabilities and dependencies<\/p>\n<\/li>\n

        • \n

          Accelerated Audit and Compliance Readiness<\/strong> (CRA, NIS-2, ISO standards)<\/p>\n<\/li>\n

        • \n

          Efficient Lifecycle Management<\/strong> for product updates and changes<\/p>\n<\/li>\n

        • \n

          Enhanced Trust<\/strong> among customers and regulators through verifiable security documentation<\/p>\n<\/li>\n<\/ul>\n

          XBOM is not a theoretical construct \u2014 it forms a practical foundation for digital resilience<\/strong>.
          By combining SBOM (Software)<\/strong> and HBOM (Hardware)<\/strong>, organizations achieve comprehensive transparency<\/strong> from development to deployment.
          Those who act early establish trust, accountability, and a tangible competitive advantage.<\/p>\n

          [\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"

          [vc_row][vc_column][vc_column_text css=””] Transparency across the Supply Chain – Extended Bill of Materials (HBOM & SBOM) The term XBOM (\u201cExtended Bill of Materials\u201d) describes an advanced approach for the systematic recording and documentation of all software and hardware components used within a product or system. It combines the established concepts of the Software Bill of Materials…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-4315","page","type-page","status-publish","hentry","description-off"],"_links":{"self":[{"href":"https:\/\/hkm-consulting.de\/en\/wp-json\/wp\/v2\/pages\/4315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hkm-consulting.de\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/hkm-consulting.de\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/hkm-consulting.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hkm-consulting.de\/en\/wp-json\/wp\/v2\/comments?post=4315"}],"version-history":[{"count":6,"href":"https:\/\/hkm-consulting.de\/en\/wp-json\/wp\/v2\/pages\/4315\/revisions"}],"predecessor-version":[{"id":4355,"href":"https:\/\/hkm-consulting.de\/en\/wp-json\/wp\/v2\/pages\/4315\/revisions\/4355"}],"wp:attachment":[{"href":"https:\/\/hkm-consulting.de\/en\/wp-json\/wp\/v2\/media?parent=4315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}