What “Restricted Source” Means for a Defense or UAS Program
Program teams hear "restricted source" constantly and are rarely given a plain explanation of what it actually requires. Here's what the term means, why the restrictions exist, and what it takes to actually develop a compliant alternative.
The short answer
A restricted source is a component, subcomponent, or supplier a program is prohibited or discouraged from using because of its country of origin, ownership, or ties to specific entities identified as a security concern under federal law or program policy — commonly entities covered under Section 889 of the National Defense Authorization Act. Meeting the requirement means finding, qualifying, and documenting a replacement source that genuinely avoids the restriction, not just one that looks different on paper.
These rules are about named entities and origins, not vague nationality concerns.
Restricted-source requirements are usually specific, not general — they name particular companies, ownership structures, or countries of origin identified through federal law or program-level policy as carrying supply-chain security risk. Section 889 of the National Defense Authorization Act, for example, names specific telecommunications and video-surveillance manufacturers (Huawei, ZTE, Hytera, Hikvision, Dahua, and their subsidiaries) rather than restricting an entire country's industrial output wholesale. That specificity matters for sourcing work: it means the compliance question isn't "was this made in Country X," it's "does this part or its subcomponents trace back to one of the specifically named restricted entities."
Replacing a restricted part is a technical project, not a paperwork exercise.
The trap worth naming directly
The most common failure mode isn't dishonesty — it's stopping the investigation one level too early. A final assembler outside a restricted country can still source a restricted subcomponent from exactly the entity the program is trying to avoid. Real restricted-source development checks the replacement at the same depth as the original problem, not just at the finished-good level.
Questions programs actually ask about this.
What does "restricted source" mean in a defense or UAS program?
It refers to a component, subcomponent, or supplier that a program is prohibited or discouraged from using, typically because of its country of origin, ownership, or ties to specific named entities restricted under federal law or program policy — for example, entities covered under Section 889 of the National Defense Authorization Act. A restricted-source requirement means the program needs to source that part from somewhere else.
Why do these restrictions exist?
They exist to reduce supply-chain risk tied to specific countries, entities, or ownership structures that federal law or program policy has identified as a security concern — commonly around telecommunications equipment, surveillance technology, and component sourcing from named restricted entities. The restrictions are usually defined at the entity or country level, not simply by the finished product's country of assembly.
What does developing a compliant alternate source actually involve?
It starts with identifying candidate manufacturers outside the restricted origin, then doing the technical and provenance work to confirm the replacement part actually meets the original specification and doesn't simply move the restricted content one tier upstream. That means BOM-level investigation of the alternate source, not just confirming its headline country of assembly.
Tell us what needs to be re-sourced.
This is one part of Kestrel's broader supplier qualification and provenance investigation work, described on the Capabilities and Government & Defense pages.