Executive Order 14306: Sustaining Select Efforts To Strengthen the Nation's Cybersecurity and Amending Executive Order 13694 and Executive Order 14144
President: Donald J. Trump
Preserved selected federal cybersecurity initiatives while narrowing or revising parts of EOs 13694 and 14144, including software supply-chain, cryptography, cloud-token and sanctions work.
Status: In effect. Is Executive Order 14306 still in effect? Yes. Executive Order 14306 remains in effect. See Federal Register record.

What does Executive Order 14306 do?
The text directs NIST to update the SSDF, SP 800-53 and key-management guidance, and OMB and CISA to pilot machine-readable cybersecurity policy.
Reading the operative provisions of Executive Order 14306
EO 14306 preserves selected federal cybersecurity initiatives while amending portions of EO 13694 and EO 14144. The changes address areas such as software supply-chain security, cryptography, cloud access and sanctions policy. Its Federal Register text identifies which earlier provisions remain, are revised or are removed. The order is a selective amendment, not a repeal of every prior cybersecurity direction.
When one executive order amends another, agencies must read the two texts together. A provision that remains unchanged continues to operate under the original order; a modified provision follows the newer language; a deleted provision no longer supplies that specific direction. This is why the scope of each amendment matters for agency deadlines and implementation plans. The order’s list of preserved efforts also helps distinguish continuity from new policy.
Cybersecurity implementation relies on technical standards, procurement terms, incident response and agency systems. A presidential directive may set priorities, but NIST guidance, agency regulations and contract requirements often provide the operational detail. Changes to a software or cryptographic standard can affect vendors and federal systems at different times. To understand the order’s practical effect, check subsequent agency guidance and the specific revised subsection rather than describing the document as a wholesale rollback.
Before and after
Before the order
EO 14144 set a broad 2025 cybersecurity program and EO 13694 supplied sanctions authority for significant malicious cyber activity.
After the order
NIST issued SP 800-53 release 5.2.0 and advanced secure-development demonstrations; remaining agency and procurement work continues on separate schedules.
Who had to do what
| Agency / office | Action | Timing / position |
|---|---|---|
| NIST | Update the SSDF, SP 800-53 and key-management guidance | Staged deadlines |
| OMB and CISA | Pilot machine-readable cybersecurity policy | One year |
| Agencies | Continue selected post-quantum and fraud-prevention work | Ongoing |
What happened next
EO 14306 signed.
NIST finalized SP 800-53 release 5.2.0 in response to the order.
Legal and source detail
How it works legally
FISMA, procurement law, the International Emergency Economic Powers Act and agency organic statutes govern implementation. The amendments do not themselves impose sanctions on a named person.
Sources by type
If a source is unavailable, first check the cited publisher or another official repository. The cited publisher remains the authority.
Primary and official sources
Orders, laws, court records and official implementation material.
- NIST secure-development update (opens in a new tab) Official record
How we checked this
Last checked against the sources above on September 9, 2026. How we research →