<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.nobuo-scitt-hardware-iot-cloud-use-cases" target="https://datatracker.ietf.org/doc/html/draft-nobuo-scitt-hardware-iot-cloud-use-cases-00">
   <front>
      <title>Applying SCITT to Hardware, IoT Device, and Cloud Compute Resource Supply Chains</title>
      <author initials="N." surname="Aoki" fullname="Nobuo Aoki">
         <organization>The Graduate University for Advanced Studies (SOKENDAI)</organization>
      </author>
      <date month="July" day="6" year="2026" />
      <abstract>
	 <t>   This document describes how SCITT can be applied to supply chains
   that include hardware components, IoT devices, firmware, cloud
   compute resources, confidential-computing environments, accelerators,
   and related operational evidence.  It gives use cases and scope
   guidance.  It also explains how SCITT can work with RATS, COSE, TCG
   technologies, SBOM, HBOM, CBOM, and cloud attestation systems without
   replacing those technologies.

   This document is informational.  It does not define hardware
   assurance rules, cloud assurance rules, device identity systems,
   manufacturing requirements, or payload formats.  Its purpose is to
   show where SCITT statements and receipts can provide transparency for
   heterogeneous supply-chain evidence, and where other standards or
   domain profiles should remain responsible.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-nobuo-scitt-hardware-iot-cloud-use-cases-00" />
   
</reference>
