Access Official Technical PDF

Share Summary:LinkedInEmail

Electronics supply chain assurance is difficult when a component passes through multiple companies, facilities and countries before installation. A conventional chain-of-custody record can become hard to maintain as products move from design and fabrication through packaging, testing, distribution and integration. SHIELD, a DARPA program technology developed by SRI International, addresses one part of this challenge by placing a secure identification chip inside a microelectronic component package. The aim is to make component authenticity verifiable at points along the supply chain.

Why component provenance is hard to maintain

A complex electronic component may pass through many organizations before it reaches its final application. Each handoff creates a point where records can be incomplete, parts can be diverted, or a component’s identity can be misrepresented. The risks are not limited to obvious substitution. Threats can arise during design, manufacturing, packaging, testing and distribution, including unauthorized overproduction, process compromise, theft and malicious insertion.

It is useful to distinguish counterfeit parts from cloned parts. A counterfeit may be presented as a new, genuine original-equipment-manufacturer (OEM) component even though its condition or reliability is uncertain. Examples include used components that have been recycled and remarked, OEM test failures resold as acceptable, or parts from unlicensed overproduction. A clone is not made by the OEM but is designed to imitate an authentic component. It may be copied at another facility or reverse-engineered using stolen intellectual property, and its function may have been altered.

Both categories undermine confidence in component identity. For defense and other demanding applications, a paper trail alone may not establish that the physical part being inspected is the same part described in the records.

How SHIELD supports electronics supply chain assurance

SHIELD uses a small identification chip called a dielet, embedded in the host integrated circuit’s package. The dielet is described as 100 micrometers square and 30 micrometers thick, making it small enough to fit within a package. Its role is to provide a hardware root of trust: a physical identity tied to the component that can be checked rather than relying solely on labels or documents.

The dielet contains an Advanced Encryption Standard (AES) encryption engine and a unique 256-bit secret key. The key is programmed into nonvolatile memory during wafer probing and enrolled with a verification server. Authentication uses a challenge-response protocol: a reader communicates wirelessly with the dielet, which responds using its cryptographic identity. A successful response provides evidence that the dielet is authentic and associated with the expected component record.

From reader to verification server

In the described system, a SHIELD reader interrogates the dielet wirelessly. An Android handheld device, such as a tablet or smartphone, controls the reader and communicates with the remote SHIELD Verification Server over a secure VPN connection. The server is hosted on Amazon Web Services, with dielet keys stored using AWS Key Management Service. The whitepaper reports that a complete authentication transaction, including internet latency, takes one to two seconds.

This process is designed to make counterfeiting more difficult and costly by requiring a valid hardware identity, rather than a plausible external marking alone. Authentication does not, by itself, prove every detail of a component’s manufacturing history or operating condition. It provides a way to verify the identity of the protected component at a check point.

Where authentication fits in manufacturing and distribution

The SHIELD supply model describes dielet production and installation as part of the component flow. An IC manufacturer sends products to a SHIELD facility, where dielets are installed; the protected products are then returned or forwarded to the designated distributor or OEM. This arrangement creates an opportunity to check identity as products move between organizations.

The broader manufacturing-chain concepts in the whitepaper consider additional points at which hardware identity could support provenance. These include attaching dielets to wafers, incorporating them into reticles or dicing streets, and placing them within or on a chip package. The appropriate location depends on what needs to be tracked: a wafer, a design or mask, a packaged component, or a larger assembly. These are proposed approaches for extending assurance across manufacturing stages, not a claim that every option is part of the same installed system.

For engineers and supply chain managers, practical questions include:

  • What is being authenticated? Define whether the target is a packaged IC, a manufacturing intermediate or an assembly.
  • Where should checks occur? Identify transfer points where verifying component identity would support receiving, inspection or production controls.
  • How will identity link to records? Determine which product-specific data and process events should be associated with the hardware identifier.
  • Who can access verification data? Establish roles and procedures for readers, servers and participating organizations.

Combining hardware identity with auditable records

The whitepaper also outlines a possible bridge between hardware-backed authentication and distributed ledgers. In this architecture, scanners read component identity and event data, intermediary software passes relevant information to a blockchain network, and ledgers or smart contracts record events such as manufacture, delivery, inspection, installation and disposal. Participants could use those records for queries, notifications, compliance and traceability.

The layers serve different purposes. The hardware layer can provide identity and cryptographic authentication. A software bridge can capture and relay observations. A ledger can preserve shared records of events reported by authorized participants. A ledger cannot independently establish that an event was observed correctly; the quality of its records depends on the hardware, scanning process and data governance connecting the physical component to the digital entry.

Practical implications for industrial and defense supply chains

SHIELD illustrates how electronic component authentication can strengthen a supply chain control system without treating documentation as the only source of trust. A cryptographic identifier embedded in packaging can help organizations check that a component carries a recognized identity when it changes hands. When combined with appropriately managed records, that identity may support more traceable manufacturing and distribution workflows.

For organizations evaluating such an approach, the key is to align authentication with the actual risk and operating process. Decide which components require protection, where verification is meaningful, and how results will be handled when a check fails or records do not match. Hardware identity, secure communications and well-managed supply chain data work together; none replaces the need for sound procurement, inspection and process controls.

Access Official Technical PDF

About The Author