Be A Freedom Fighter · Bill Library

HR 10972 — NEW HORIZON Act

Freedom score: -1 (scale −10 to +10)

Sponsor: Rep. Cloud, Michael [R-TX-27] · Latest action: Referred to the House Committee on Armed Services. (2026-11-10)

Full text on GovInfo (introduced version) · Congress.gov · ← Bill Library index

Findings — 7 highlighted provisions

Each item below is one provision documented in the findings file. The same provision is highlighted in the full text underneath, with its section citation and criterion. Everything else on this page is plain, unreviewed bill text.

  1. Sec. 1 — Short title defines NEW HORIZON acronym See in text ↓
  2. Sec. 2(a) — Nonoperative findings about military use of orbital computing See in text ↓
  3. Sec. 2(b)(1)-(3) — Within one year of enactment, Defense Secretary through Defense Innovation Unit must conduct Hybrid Space Architecture pilot testing commercial orbital data centers and cloud for intelligence, space awareness, command-and-control, data transport and limited operational use See in text ↓
  4. Sec. 2(b)(4)-(7) — Encourage competition including nontraditional contractors; require zero-trust cybersecurity, encryption, continuous monitoring, access controls, supply-chain safeguards, redundancy, protected links and workload isolation for sensitive/classified data; interoperability and consultation with Space Force, NRO, NGA and other agencies See in text ↓
  5. Sec. 2(b)(8) — Congressional briefing by December 31, 2028 on performance, acquisition, cybersecurity, resilience and risks See in text ↓
  6. Sec. 2(c) — Pilot ends five years after enactment See in text ↓
  7. Sec. 2(d) — Orbital data center defined as distinct space-based persistent/shared computing, storage, networking and data functions, not merely ancillary spacecraft functions. No fixed appropriation See in text ↓

Full text (introduced version)

19 of 19 text blocks highlighted. Source: GovInfo, fetched cached.

[Congressional Bills 119th Congress] [From the U.S. Government Publishing Office] [H.R. 10972 Introduced in House (IH)] <DOC> 119th CONGRESS 2d Session H. R. 10972 To require the Secretary of Defense to carry out an operational pilot program under the Hybrid Space Architecture initiative to evaluate the use of commercially available orbital data center services and space- based cloud computing capabilities relevant to national security space and joint mission requirements, and for other purposes. _______________________________________________________________________ IN THE HOUSE OF REPRESENTATIVES November 10, 2026 Mr. Cloud introduced the following bill; which was referred to the Committee on Armed Services _______________________________________________________________________ A BILL To require the Secretary of Defense to carry out an operational pilot program under the Hybrid Space Architecture initiative to evaluate the use of commercially available orbital data center services and space- based cloud computing capabilities relevant to national security space and joint mission requirements, and for other purposes. Be it enacted by the Senate and House of Representatives of the United States of America in Congress assembled,

SECTION 1. SHORT TITLE.

Sec. 1 — Short title defines NEW HORIZON acronym

This Act may be cited as the ``Nodes, Enterprise Workloads, and Hybrid Operations, Resilience, Integration, Zero-Trust, Orbital Networks Act'' or ``NEW HORIZON Act''.

SEC. 2. OPERATIONAL PILOT PROGRAM ON ORBITAL DATA CENTER SERVICES.

Sec. 2(a) — Nonoperative findings about military use of orbital computing

(a) Findings.--Congress makes the following findings:

Sec. 2(a) — Nonoperative findings about military use of orbital computing

(1) Modern national security space missions generate increasing volumes of data from space-based sensors, platforms, and constellations, placing growing demands on terrestrial data transport, processing, and analysis infrastructure.

Sec. 2(a) — Nonoperative findings about military use of orbital computing

(2) Reliance on ground-based data processing can introduce latency, bandwidth constraints, and vulnerabilities that may degrade the timeliness, resilience, and effectiveness of military and intelligence operations in contested environments.

Sec. 2(a) — Nonoperative findings about military use of orbital computing

(3) Commercial industry is developing orbital data center and space-based cloud computing capabilities that enable in- space data processing, storage, and analytics, which may reduce latency, enhance resilience, and improve mission outcomes.

Sec. 2(a) — Nonoperative findings about military use of orbital computing

(4) The Department of Defense has identified the need for hybrid architectures that integrate space, terrestrial, and commercial capabilities to support joint and national security missions.

Sec. 2(a) — Nonoperative findings about military use of orbital computing

(5) An operational pilot program is necessary to evaluate the military utility, operational integration, and transition potential of orbital data center services through real-world mission use cases before any broader adoption or sustained acquisition.

Sec. 2(a) — Nonoperative findings about military use of orbital computing

(6) Maintaining a competitive and resilient domestic industrial base for orbital infrastructure, including satellite platforms, communications systems, and in-space computing capabilities, is important to accelerating innovation and supporting operational resilience.

Sec. 2(b)(1)-(3) — Within one year of enactment, Defense Secretary through Defense Innovation Unit must conduct Hybrid Space Architecture pilot testing commercial orbital data centers and cloud for intelligence, space awareness, command-and-control, data transport and limited operational use

Sec. 2(b)(4)-(7) — Encourage competition including nontraditional contractors; require zero-trust cybersecurity, encryption, continuous monitoring, access controls, supply-chain safeguards, redundancy, protected links and workload isolation for sensitive/classified data; interoperability and consultation with Space Force, NRO, NGA and other agencies

Sec. 2(b)(8) — Congressional briefing by December 31, 2028 on performance, acquisition, cybersecurity, resilience and risks

(b) Pilot Program.--

Sec. 2(b)(1)-(3) — Within one year of enactment, Defense Secretary through Defense Innovation Unit must conduct Hybrid Space Architecture pilot testing commercial orbital data centers and cloud for intelligence, space awareness, command-and-control, data transport and limited operational use

(1) In general.--Not later than one year after the date of the enactment of this Act, the Secretary of Defense, acting through the Director of the Defense Innovation Unit, shall carry out an operational pilot program under the Hybrid Space Architecture initiative to evaluate the use of commercially available orbital data center services and space-based cloud computing capabilities relevant to national security space and joint mission requirements.

Sec. 2(b)(1)-(3) — Within one year of enactment, Defense Secretary through Defense Innovation Unit must conduct Hybrid Space Architecture pilot testing commercial orbital data centers and cloud for intelligence, space awareness, command-and-control, data transport and limited operational use

(2) Purposes.--The purposes of the pilot program shall be-- (A) to assess the military utility of orbital data center and space-based cloud computing services; (B) to evaluate the operational integration of such services into existing and planned Department of Defense space and joint architectures; (C) to examine the resilience, latency, security, and mission assurance benefits of in-space data processing; (D) to inform the potential transition of such services into sustained programs of record or operational use; (E) to evaluate concepts of operations for the protection and defense of orbital data center assets against kinetic, nonkinetic, and cyber threats; (F) to assess the asset protection strategies and vulnerabilities of orbital data center infrastructure; and (G) to evaluate the integration and operational performance of interoperable, commercially provided orbital infrastructure components sourced from multiple vendors across the hybrid space architecture ecosystem.

Sec. 2(b)(1)-(3) — Within one year of enactment, Defense Secretary through Defense Innovation Unit must conduct Hybrid Space Architecture pilot testing commercial orbital data centers and cloud for intelligence, space awareness, command-and-control, data transport and limited operational use

(3) Scope.--In carrying out the pilot program, the Secretary may-- (A) employ commercially available orbital data center services in support of real-world mission scenarios, including intelligence, space domain awareness, command and control, data transport, and other national security applications; (B) conduct testing, demonstration, and limited operational employment necessary to assess technical performance and operational viability; and (C) support integration activities required to evaluate interoperability with the Department of Defense's space, ground, and network systems.

Sec. 2(b)(4)-(7) — Encourage competition including nontraditional contractors; require zero-trust cybersecurity, encryption, continuous monitoring, access controls, supply-chain safeguards, redundancy, protected links and workload isolation for sensitive/classified data; interoperability and consultation with Space Force, NRO, NGA and other agencies

(4) Acquisition authority.--The Secretary shall encourage competitive participation from a diverse set of nontraditional defense contractors and commercial space providers.

Sec. 2(b)(4)-(7) — Encourage competition including nontraditional contractors; require zero-trust cybersecurity, encryption, continuous monitoring, access controls, supply-chain safeguards, redundancy, protected links and workload isolation for sensitive/classified data; interoperability and consultation with Space Force, NRO, NGA and other agencies

(5) Security and resilience measures for sensitive and classified information.--In carrying out the pilot program, the Secretary shall ensure that any orbital data center services used to process, store, or transmit sensitive or classified information have in place-- (A) cybersecurity protections, including zero-trust architecture, encryption, identity and access management, continuous monitoring, and protections against insider threats; (B) risk-management measures-- (i) to address supply chain vulnerabilities and foreign ownership, control, or influence; and (ii) that achieve compliance with applicable Department of Defense cybersecurity and authorization requirements; (C) resilience and mission assurance capabilities, including redundancy, failover, operation in degraded or contested environments, and rapid reconstitution or replacement capabilities; (D) protections against cyber, electronic warfare, counterspace, and other nonkinetic threats; (E) secure telemetry, tracking, and command links and associated command-and-control systems, including authenticated command uplinks, encrypted telemetry and data links, anti-spoofing and anti-jamming protections, resilient cryptographic key management, protected timing and navigation inputs, and secure software and firmware update mechanisms; (F) protections for associated ground systems, mission operations centers, terrestrial network connections, software supply chains, and user access interfaces, including segmentation, continuous monitoring, access controls, encryption, and resilience against cyber intrusion, disruption, and unauthorized access; and (G) protections to ensure workload isolation, tenant separation, and data sovereignty for sensitive or classified information processed, stored, or transmitted through orbital data center services, including safeguards against unauthorized cross-tenant, cross-domain, or provider access.

Sec. 2(b)(4)-(7) — Encourage competition including nontraditional contractors; require zero-trust cybersecurity, encryption, continuous monitoring, access controls, supply-chain safeguards, redundancy, protected links and workload isolation for sensitive/classified data; interoperability and consultation with Space Force, NRO, NGA and other agencies

(6) Integration and interoperability.--The Secretary shall ensure that any orbital data center services evaluated under the pilot program are interoperable with existing Department of Defense command, control, communications, and intelligence systems.

Sec. 2(b)(4)-(7) — Encourage competition including nontraditional contractors; require zero-trust cybersecurity, encryption, continuous monitoring, access controls, supply-chain safeguards, redundancy, protected links and workload isolation for sensitive/classified data; interoperability and consultation with Space Force, NRO, NGA and other agencies

(7) Consultation.--In carrying out the pilot program, the Secretary, acting through the Director of the Defense Innovation Unit, shall consult with-- (A) the Assistant Secretary of Defense for Space Policy; (B) service acquisition executives (as defined in section 101 of title 10, United States Code); (C) the Space Force and other military departments with potential operational interest or transition pathways; (D) the National Reconnaissance Office; (E) the National Geospatial-Intelligence Agency; and (F) such other individuals and organizations as the Secretary considers appropriate.

Sec. 2(b)(8) — Congressional briefing by December 31, 2028 on performance, acquisition, cybersecurity, resilience and risks

(8) Briefing.--Not later than December 31, 2028, the Secretary shall provide the congressional defense committees (as defined in section 101 of title 10, United States Code) with a briefing on-- (A) execution of the pilot program; (B) operational use cases evaluated; (C) lessons learned from operational employment; (D) recommendations regarding future acquisition or operational use of orbital data center services; (E) cybersecurity risks, insider threat vulnerabilities, and mitigation measures; (F) resilience against counterspace threats and contested space environments; (G) commercial provider risks, including supply chain and foreign ownership concerns; and (H) recommendations for security, resilience, and acquisition requirements for any future program of record.

Sec. 2(c) — Pilot ends five years after enactment

(c) Termination.--The authority to carry out the pilot program under this section shall terminate on the date that is five years after the date of the enactment of this Act.

Sec. 2(d) — Orbital data center defined as distinct space-based persistent/shared computing, storage, networking and data functions, not merely ancillary spacecraft functions. No fixed appropriation

(d) Orbital Data Center Defined.--In this section, the term ``orbital data center'' means a space-based computing, data storage, or networking capability, including one or more spacecraft, hosted payloads, or distributed orbital architectures, designed primarily to provide persistent, scalable, or shared in-orbit processing, analysis, storage, fusion, routing, or dissemination of data as a distinct operational capability, rather than as a function ancillary to the primary mission of a spacecraft, prior to transmission to terrestrial or other external infrastructure, including to reduce latency, mitigate bandwidth constraints, improve operational resilience, or support time- sensitive missions. <all>

Findings source: bill-scores-v2-batch19-findings-2026-11-14.md. Highlights come only from that file; no finding, score, or provision was invented for this page.

What you can do

Contact your U.S. Representative and Senators about this bill.

Find your Representative Contact your Senators

Spot an error on this page? Report it.