; (C) a process to certify developers of emergency management software; and (D) requiring developers to provide the Administrator with a copy of and rights of use for ongoing testing of each version of incident management and warning tool software before the software is first used by a State, Tribal, or local government. (d) Review and update of memoranda of understanding (1) In general The Administrator shall review the memoranda of understanding between the Agency and State, Tribal, and local governments with respect to the public alert and warning system to ensure that all agreements ensure compliance with the requirements developed by the Administrator under subsection (b)(1). (e) Future memoranda The Administrator shall ensure that any new memorandum of understanding entered into between the Agency and a State, Tribal, or local government on or after the date of enactment of this Act with respect to the public alert and warning system ensures that the agreement requires compliance with the requirements developed by the Administrator under subsection (b)(1). (f) Missile alert and warning authorities (1) In general (A) Authority On and after the date that is 120 days after the date of enactment of this Act, the authority to originate an alert warning the public of a missile launch directed against a State using the public alert and warning system shall reside primarily with the Federal Government. (B) Delegation of authority The Secretary may delegate the authority described in subparagraph (A) to a State, Tribal, or local entity if, not later than 180 days after the date of enactment of this Act, the Secretary submits a report to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives that— (i) it is not feasible for the Federal Government to alert the public of a missile threat against a State