(1) A mission owner who has elected to evaluate, pilot, or field a covered capability shall furnish (A) an authorized landing zone at the applicable impact level; and (B) a timely authorization decision under subsection (f).
(2) PREFERENCE. The mission owner shall use a mission-owner or military-department landing zone when one exists at the required impact level. A Department-wide or Service-wide enterprise platform shall be leveraged as a fallback when the mission owner lacks a suitable environment, not as a substitute for mission-owner responsibility.
(3) Not later than 180 days after the date of the enactment of this Act, the Secretary, acting through the Chief Information Officer and in coordination with the Under Secretary of War for Research and Engineering, the Chief Digital and Artificial Intelligence Officer, the Defense
Innovation Unit, and the military department chief information officers, shall designate (A) fallback landing zones at Impact Levels 2, 4, and 5; and (B) an accredited experimentation landing zone at Impact Level 6 and an accredited experimentation path for special-access capabilities, for use when a mission owner has no suitable environment.
(4) Each authorized landing zone shall inherit identity, logging, scanning, container hardening, and continuous monitoring; accept machine-readable artifacts; support the subsection (g) overlay; be capable, where the mission requires, of hosting quantum-safe and homomorphic-encryption workloads without forcing plaintext exposure as a condition of authorization; and shall not charge a vendor authorization fee for the security boundary.
(5) A mission owner may not decline evaluation on the ground that only a central enterprise service can host or authorize the capability, or on the ground that the capability is neuromorphic, quantum-based, or uses homomorphic encryption.
(f) Authorization to Experiment; Time Limits.
(1) Upon receipt of a complete onboarding package, the responsible authorizing official shall issue an ATE or an authorization to use under the host-system ATO, or a written denial, not later than (A) 30 calendar days for Impact Level 2; (B) 45 calendar days for Impact Level 4; and (C) 60 calendar days for Impact Level 5. For an experimentation landing zone designated under subsection (e)(3)(B), the period shall be 90 calendar days.
(2) The authorizing official may extend a deadline in paragraph (1) once, for not more than 15 calendar days, upon written notice to the mission owner and the Chief Information Officer stating the specific control gap still open.
(3) An ATE shall run not less than 180 days, may be renewed, shall convert to continuous authorization upon published criteria, and shall be revoked immediately if continuous-monitoring thresholds are breached.
(4) If no decision is issued when the period in paragraph (1), plus any extension under paragraph (2), has expired (A) the Chief Information Officer shall, within 10 calendar days, assign another authorizing official to decide the package and shall notify the mission owner
and the congressional defense committees of the missed deadline, the residual open items, and the official assigned; (B) the assigned authorizing official shall issue an ATE, an authorization to use under the host-system ATO, or a written denial not later than 15 calendar days after assignment; and (C) silence, and the expiration of a deadline, shall not constitute an authorization. Risk acceptance remains the decision of an authorizing official.
(5) Not later than 60 days after enactment, the Chief Information Officer shall publish the complete-onboarding-package checklist, including a short annex for neuromorphic, quantum-based, and homomorphic-encryption workloads. After publication, a package that contains each listed item is complete. Additional artifacts may be requested in parallel
and shall not reset the clock in paragraph (1).