1 | Sec. 1 Policy (as replaced by EO 14306) | 0 |
10-11 | Secs. 10 and 11 Definitions and general provisions | 0 |
2 | Sec. 2 Operationalizing Transparency and Security in Third-Party Software Supply Chains | 0 |
2(d) | Sec. 2(d) (now 2(b)) Comply with NIST SP 800-161 and integrate supply chain risk into acquisition | 2 |
2(e) | Sec. 2(e) (now 2(c)) Manage agency use of open source software | 2 |
3 | Sec. 3 Improving the Cybersecurity of Federal Systems | 0 |
3(c)(ii)(A) | Sec. 3(c)(ii)(A) (now 3(a)(ii)(A)) Provide CISA the EDR and SOC data the concept of operations requires | 2 |
3(c)(v) | Sec. 3(c)(v) (now 3(a)(v)) Enroll EDR endpoints in CISA's Persistent Access Capability | 2 |
3(c)(vi) | Sec. 3(c)(vi) (now 3(a)(vi)) Tell CISA which systems need extra controls or non-disruption periods | 1 |
3(d) | Sec. 3(d) (now 3(b)) Provide agency configuration baselines for cloud services (FedRAMP) | 2 |
3(e) | Sec. 3(e) (now 3(c)) Continually verify the cybersecurity of Federal space systems | 2 |
3(e)(i)(A) | Sec. 3(e)(i)(A) (now 3(c)(i)(A)) Protect civil space command and control | 1 |
3(e)(i)(B) | Sec. 3(e)(i)(B) (now 3(c)(i)(B)) Detect, report and recover from anomalous space system activity | 2 |
3(e)(i)(C) | Sec. 3(e)(i)(C) (now 3(c)(i)(C)) Use secure software and hardware development for civil space systems | 2 |
4 | Sec. 4 Securing Federal Communications | 0 |
4(b)(i) | Sec. 4(b)(i) Cover internet number resources by a registry agreement and keep registry records current | 0 |
4(b)(ii) | Sec. 4(b)(ii) Publish Route Origin Authorizations for agency IP address blocks | 0 |
4(b)(iii) | Sec. 4(b)(iii) Deploy routing security as a contracted internet service provider | 2 |
4(c)(i) | Sec. 4(c)(i) Support encrypted DNS in products that act as DNS resolvers | 1 |
4(c)(ii) | Sec. 4(c)(ii) Enable encrypted DNS wherever clients and servers support it | 2 |
4(d)(i) | Sec. 4(d)(i) Enforce encrypted, authenticated transport between email clients and servers | 2 |
4(e)(i) | Sec. 4(e)(i) Enable transport encryption by default for voice, video and messaging | 2 |
4(e)(ii) | Sec. 4(e)(ii) Use end-to-end encryption by default while keeping records capability | 1 |
4(f)(ii) | Sec. 4(f)(ii) Support TLS 1.3 or a successor by 2 January 2030 | 1 |
4(g)(ii) | Sec. 4(g)(ii) Meet FedRAMP key management requirements for access tokens and keys | 1 |
4(g)(iii) | Sec. 4(g)(iii) Follow best practice for HSMs and isolation protecting cloud keys | 1 |
6 | Sec. 6 Promoting Security with and in Artificial Intelligence | 0 |
6(e) | Sec. 6(e) (now 5(b)) Manage AI software vulnerabilities and compromises in vulnerability management | 2 |
7 | Sec. 7 Aligning Policy to Practice | 0 |
7(c) | Sec. 7(c) Carry the US Cyber Trust Mark on consumer IoT products sold to Government | 2 |
8 | Sec. 8 National Security Systems and Debilitating Impact Systems | 0 |
8(d) | Sec. 8(d) Inventory major information systems and provide the inventory to the registry | 2 |
9 | Sec. 9 Sanctions for significant malicious cyber-enabled activities (EO 13694 amended) | 0 |
AMEND | Amendment by EO 14306: provisions struck and how the numbering is read | 0 |
STATUS | Status: in force as amended by EO 14306; builds on EO 14028 | 0 |