United States (Federal executive branch)

US Executive Order 14144

35 controls. 3 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

35 controls 3 frameworks share controls with it United States (Federal executive branch) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
1Sec. 1 Policy (as replaced by EO 14306)0
10-11Secs. 10 and 11 Definitions and general provisions0
2Sec. 2 Operationalizing Transparency and Security in Third-Party Software Supply Chains0
2(d)Sec. 2(d) (now 2(b)) Comply with NIST SP 800-161 and integrate supply chain risk into acquisition2
2(e)Sec. 2(e) (now 2(c)) Manage agency use of open source software2
3Sec. 3 Improving the Cybersecurity of Federal Systems0
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 requires2
3(c)(v)Sec. 3(c)(v) (now 3(a)(v)) Enroll EDR endpoints in CISA's Persistent Access Capability2
3(c)(vi)Sec. 3(c)(vi) (now 3(a)(vi)) Tell CISA which systems need extra controls or non-disruption periods1
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 systems2
3(e)(i)(A)Sec. 3(e)(i)(A) (now 3(c)(i)(A)) Protect civil space command and control1
3(e)(i)(B)Sec. 3(e)(i)(B) (now 3(c)(i)(B)) Detect, report and recover from anomalous space system activity2
3(e)(i)(C)Sec. 3(e)(i)(C) (now 3(c)(i)(C)) Use secure software and hardware development for civil space systems2
4Sec. 4 Securing Federal Communications0
4(b)(i)Sec. 4(b)(i) Cover internet number resources by a registry agreement and keep registry records current0
4(b)(ii)Sec. 4(b)(ii) Publish Route Origin Authorizations for agency IP address blocks0
4(b)(iii)Sec. 4(b)(iii) Deploy routing security as a contracted internet service provider2
4(c)(i)Sec. 4(c)(i) Support encrypted DNS in products that act as DNS resolvers1
4(c)(ii)Sec. 4(c)(ii) Enable encrypted DNS wherever clients and servers support it2
4(d)(i)Sec. 4(d)(i) Enforce encrypted, authenticated transport between email clients and servers2
4(e)(i)Sec. 4(e)(i) Enable transport encryption by default for voice, video and messaging2
4(e)(ii)Sec. 4(e)(ii) Use end-to-end encryption by default while keeping records capability1
4(f)(ii)Sec. 4(f)(ii) Support TLS 1.3 or a successor by 2 January 20301
4(g)(ii)Sec. 4(g)(ii) Meet FedRAMP key management requirements for access tokens and keys1
4(g)(iii)Sec. 4(g)(iii) Follow best practice for HSMs and isolation protecting cloud keys1
6Sec. 6 Promoting Security with and in Artificial Intelligence0
6(e)Sec. 6(e) (now 5(b)) Manage AI software vulnerabilities and compromises in vulnerability management2
7Sec. 7 Aligning Policy to Practice0
7(c)Sec. 7(c) Carry the US Cyber Trust Mark on consumer IoT products sold to Government2
8Sec. 8 National Security Systems and Debilitating Impact Systems0
8(d)Sec. 8(d) Inventory major information systems and provide the inventory to the registry2
9Sec. 9 Sanctions for significant malicious cyber-enabled activities (EO 13694 amended)0
AMENDAmendment by EO 14306: provisions struck and how the numbering is read0
STATUSStatus: in force as amended by EO 14306; builds on EO 140280

Tell me when US Executive Order 14144 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for US Executive Order 14144, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition