United States (Federal executive branch)

US Executive Order 14028

52 controls. 0 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.

52 controls 0 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.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
USEO14028-1Threat Information Sharing and Contractual Barriers Removal0
USEO14028-2Zero Trust Architecture and Federal Cybersecurity0
USEO14028-3Software Supply Chain Security and SBOM0
USEO14028-4Endpoint Detection and Response (EDR)0
USEO14028-5Cyber Incident Reporting and Standardisation0
2Sec. 2 Removing Barriers to Sharing Threat Information0
2(c)(i)Sec. 2(c)(i) Collect and preserve cybersecurity event data0
2(c)(ii)Sec. 2(c)(ii) Share incident data with the contracting agency0
2(c)(iii)Sec. 2(c)(iii) Collaborate in federal investigations and response0
2(c)(iv)Sec. 2(c)(iv) Share threat information in industry-recognized formats0
2(f)(i)Sec. 2(f)(i) Promptly report incidents involving products or services supplied0
2(f)(ii)Sec. 2(f)(ii) Also report to CISA0
2(k)Sec. 2(k) Remove duplicative agency-specific cybersecurity requirements0
3Sec. 3 Modernizing Federal Government Cybersecurity0
3(b)(i)Sec. 3(b)(i) Update agency plans to prioritize cloud adoption0
3(b)(ii)Sec. 3(b)(ii) Develop a Zero Trust Architecture implementation plan0
3(b)(iii)Sec. 3(b)(iii) Report the cloud and zero trust plans to OMB and the APNSA0
3(c)Sec. 3(c) Adopt Zero Trust Architecture in cloud migration0
3(c)(iv)Sec. 3(c)(iv) Evaluate unclassified data sensitivity and report0
3(d)Sec. 3(d) Adopt multi-factor authentication and encryption of data at rest and in transit0
3(d)(i)Sec. 3(d)(i) Report MFA and encryption progress every 60 days0
3(d)(iii)Sec. 3(d)(iii) Written rationale where MFA and encryption are not fully adopted0
4Sec. 4 Enhancing Software Supply Chain Security0
4(e)(i)Sec. 4(e)(i) Secure software development environments0
4(e)(ii)Sec. 4(e)(ii) Generate and provide conformance artifacts0
4(e)(iii)Sec. 4(e)(iii) Maintain trusted source code supply chains with automated tools0
4(e)(iv)Sec. 4(e)(iv) Check for and remediate vulnerabilities before release0
4(e)(ix)Sec. 4(e)(ix) Attest to secure software development practices0
4(e)(v)Sec. 4(e)(v) Provide tool execution artifacts and publish risk summaries0
4(e)(vi)Sec. 4(e)(vi) Maintain provenance data and controls on components, with recurring audits0
4(e)(vii)Sec. 4(e)(vii) Provide a Software Bill of Materials0
4(e)(viii)Sec. 4(e)(viii) Participate in a vulnerability disclosure program0
4(e)(x)Sec. 4(e)(x) Ensure and attest to open source integrity and provenance0
4(j)Sec. 4(j) Comply with the critical software security measures0
4(k)Sec. 4(k) Comply with the software supply chain guidance for software procured0
4(n)Sec. 4(n) Suppliers comply with and attest to the requirements (contract language)0
4(p)Sec. 4(p) Remove non-conforming software from contract vehicles0
4(q)Sec. 4(q) Bring legacy software into compliance or plan remediation0
5Sec. 5 Establishing a Cyber Safety Review Board0
6Sec. 6 Standardizing the Federal Government's Playbook for Responding to Cybersecurity Vulnerabilities and Incidents0
6(b)(ii)Sec. 6(b)(ii) Use the standard incident and vulnerability response playbook0
6(d)Sec. 6(d) Deviate from the playbook only after consultation and demonstration0
7Sec. 7 Improving Detection of Cybersecurity Vulnerabilities and Incidents on Federal Government Networks0
7(b)Sec. 7(b) Deploy an Endpoint Detection and Response initiative0
7(f)Sec. 7(f) Establish or update the CDM Memorandum of Agreement with CISA0
8Sec. 8 Improving the Federal Government's Investigative and Remediation Capabilities0
8(a)Sec. 8(a) Collect and maintain logs and provide them to CISA and the FBI0
8(b)Sec. 8(b) Protect log integrity cryptographically and retain lawfully0
8(c)Sec. 8(c) Meet the logging, retention and log management requirements with centralized SOC access0
9-11Secs. 9 to 11 National Security Systems, definitions and general provisions0
ORDERExecutive Order 14028: the instrument0
STATUSStatus: in force and unamended; EO 14144 builds on it and EO 14306 amended EO 141440

Tell me when US Executive Order 14028 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 14028, 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