Federal agency zero trust, logging and asset visibility duties: deadlines compared
| Instrument | Duty | Deadline as stated | Source |
|---|---|---|---|
| OMB M-22-09 (zero trust strategy)1 | DutyMeet specific zero trust standards and objectives, organized by CISA's five pillars: identity, devices, networks, applications and workloads, and data1 | Deadline as statedBy the end of fiscal year 2024; an FY22 to FY24 implementation plan and an FY24 budget estimate within 60 days of the memo's date, January 26, 20221 | SourceM-22-091 |
| M-22-09 as cited in OMB M-26-18 (August 31, 2026)8 | DutyTo manage digital identity, agencies should follow applicable law and existing OMB policy, including M-19-17, M-21-04 and M-22-098 | Deadline as statedNo deadline stated for this point8 | SourceM-26-18, footnote 58 |
| M-22-09 as cited in BOD 26-026 | DutyWhen planning technical refreshes of edge devices, agencies should keep M-22-09's requirements in mind: multifactor authentication, asset management and identification, isolation of critical workloads and strong access policy, and encryption of data in transit6 | Deadline as statedNo deadline stated for this point6 | SourceBOD 26-02, Background6 |
| M-22-09 as cited in the FY 2026 and FY 2027 CIO FISMA metrics7 | DutyThe system interconnections metrics (network micro-segmentation, API traffic, interconnection security) reflect requirements under BOD 26-02, M-22-09 and related directives7 | Deadline as statedCIO metrics are reported through CyberScope: FY26 Q4 and annual by October 30, 2026; FY27 Q1 by January 29, 2027; then quarterly to October 29, 20277 | SourceCIO FISMA Metrics v1.1, reporting instructions and system interconnections section7 |
| OMB M-26-14 (logging)2 | DutyRescinds M-21-31. Agencies must prioritize continuous event monitoring and threat hunting, investigation, response and forensics for all systems they or third parties run on their behalf, including IoT and operational technology2 | Deadline as statedRescission of M-21-31 effective immediately (memo dated May 22, 2026)2 | SourceM-26-14, Prioritization2 |
| CISA Logging Reference Architecture (publish date August 20, 2026)3 | DutyCISA, with OMB and the CISO Council, develops a logging reference architecture; agencies must adhere to it on the memo's timelines. It will align with CISA's Zero Trust Maturity Model2 | Deadline as statedCISA to publish within 90 days of the memo's date2 | SourceM-26-14, Reference Architecture and Appendix A2 |
| M-26-14 Agency Logging Plan2 | DutySubmit an Agency Logging Plan to OMB and CISA that provides for meeting the memo's minimum requirements2 | Deadline as statedWithin 90 days of the release of the reference architecture2 | SourceM-26-14, Agency Logging Plan and Agency Actions2 |
| M-26-14 logging maturity model2 | DutyReach minimum maturity levels across all elements (inventory visibility, collection coverage, collection operations, data retention, log management); progress is reported as the share of systems at each level2 | Deadline as statedLevel 1 within 120 days, Level 2 (Intermediate) within 180 days and Level 3 (Advanced) within 320 days of the release of the reference architecture2 | SourceM-26-14, Agency Actions and Appendix C2 |
| M-26-14 updates to the reference architecture2 | DutyWhen CISA notifies agencies of an updated reference architecture: update the Agency Logging Plan and regain the required maturity levels2 | Deadline as statedPlan within 30 calendar days; Intermediate within 60 calendar days; Advanced within 120 calendar days of CISA's notice2 | SourceM-26-14, Agency Actions (ongoing)2 |
| M-26-14 minimum logging baseline2 | DutyLogs searchable for at least 6 months and retrievable for a year after creation; readily available to the top-level agency security operations center; accurate, synchronized timestamps; collection that supports listed activities such as identifying identities used, network addresses and privilege changes2 | Deadline as statedAppendix B states no separate date; the first Agency Logging Plan, due within 90 days of the release of the reference architecture, must provide for meeting the minimum requirements2 | SourceM-26-14, Appendix B2 |
| M-26-14 log access2 | DutyAfter a known or suspected compromise of federal networks, provide logs and other relevant data to CISA and the FBI on request, to the extent consistent with law2 | Deadline as statedWithin the timeframes CISA or the FBI request, to the greatest extent practicable2 | SourceM-26-14, Log Access Requirements2 |
| CISA BOD 23-01 (asset visibility)4 | DutyAutomated asset discovery every 7 days covering at least the entire IPv4 space the agency uses; start vulnerability enumeration across all discovered assets every 14 days, using privileged credentials on managed endpoints and network devices to the maximum extent possible4 | Deadline as statedBy April 3, 20234 | SourceBOD 23-01, Required Actions4 |
| CISA BOD 23-01 (CDM reporting and on-demand scans)4 | DutyFeed enumeration results into the CDM Agency Dashboard; run on-demand asset discovery and vulnerability enumeration when CISA asks4 | Deadline as statedBy April 3, 2023: start automated ingestion within 72 hours of discovery completion; be able to start on-demand discovery and enumeration within 72 hours of a CISA request and give CISA the available results within 7 days4 | SourceBOD 23-01, Required Actions4 |
| CISA BOD 26-04, Phase I (issued June 10, 2026)5 | DutyUpdate vulnerability management policies; monitor the Known Exploited Vulnerabilities (KEV) catalog; automate KEV status reporting through the CDM Dashboard (or report manually on a bi-weekly basis); attest publicly exposed IP addresses and domains once a quarter5 | Deadline as statedEffective immediately5 | SourceBOD 26-04, Required Actions, Phase I5 |
| CISA BOD 26-04, Phase III remediation5 | DutyRemediate each vulnerability by the Table 1 timeline set by public exposure, KEV status, whether exploitation can be automated, and technical impact; the clock starts when CISA adds it to the KEV catalog or the agency finds it under BOD 23-01, whichever is first5 | Deadline as statedPhase III within 180 days of issuance. Table 1 timelines run from 3 days with forensic triage to 60 days, or fix on system upgrade for assets not publicly exposed, not in the KEV and not automatable5 | SourceBOD 26-04, Phase III and Appendix A, Table 15 |
| CISA BOD 26-04, Phase III asset tagging5 | DutyContinuously identify and tag all agency-owned assets reachable from outside the agency network with a routable IP address (organization, environment, exposure, asset type); agencies without automated CDM reporting report every seven days5 | Deadline as statedWithin 180 days of issuance5 | SourceBOD 26-04, Phase III5 |
| CISA BOD 26-02 (issued February 5, 2026), inventory6 | DutyUpdate supported edge devices running end-of-support software; inventory devices on CISA's end-of-support edge device list and report it to CISA6 | Deadline as statedUpdates immediately; inventory within 3 months of issuance6 | SourceBOD 26-02, Required Actions6 |
| CISA BOD 26-02, decommissioning6 | DutyDecommission listed devices with an end-of-support date on or before the 12-month mark, then all identified end-of-support edge devices, replacing them with vendor-supported devices and reporting to CISA6 | Deadline as statedWithin 12 months and within 18 months of issuance6 | SourceBOD 26-02, Required Actions6 |
| CISA BOD 26-02, continuous discovery6 | DutySet up continuous discovery of all edge devices, keep an inventory of those at or within 12 months of end of support, and decommission them by their end-of-support date6 | Deadline as statedWithin 24 months of issuance6 | SourceBOD 26-02, Required Actions6 |
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Method
We opened each instrument in its official copy: the OMB memoranda PDFs on whitehouse.gov (text extracted with pypdf), CISA's directive pages and BOD 26-04's Table 1 image, CISA's Logging Reference Architecture page and the FY 2026 and FY 2027 CIO FISMA metrics PDF. Deadlines are copied as each source states them; where a deadline counts from an event (a memo, a release, an issuance), we give the event's date as the source states it and do not compute calendar dates. Each cell was checked on 2026-11-14. The directives apply to Federal Civilian Executive Branch agencies; M-26-14 does not apply to national security systems or to certain Defense and Intelligence Community systems. This table explains the instruments; it is not legal advice.
Notes
- M-26-14's action table calls Level 1 'Basic'; its Appendix C maturity model calls Level 1 'Initial'.
- BOD 26-04 supersedes and revokes BOD 19-02 and BOD 22-01.
- M-22-09 is not on OMB's current memoranda page, which, checked on 2026-11-14, lists memoranda from M-25-10 onward, and no rescission of it was found among the memoranda listed there; OMB M-26-18 (August 31, 2026) refers to it as existing OMB policy.
Sources
- Office of Management and Budget. M-22-09, Moving the U.S. Government Toward Zero Trust Cybersecurity Principles (January 26, 2022). Checked .
- Office of Management and Budget. M-26-14, Ensuring Effective and Efficient Agency Logging and Network Visibility to Defend Against Evolving Cyber Threats (May 22, 2026), including Appendices B and C. Checked .
- Cybersecurity and Infrastructure Security Agency. Logging Reference Architecture (resource page). Checked .
- Cybersecurity and Infrastructure Security Agency. BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks. Checked .
- Cybersecurity and Infrastructure Security Agency. BOD 26-04: Prioritizing Security Updates Based on Risk, including Table 1: Remediation Timelines. Checked .
- Cybersecurity and Infrastructure Security Agency. BOD 26-02: Mitigating Risk From End-of-Support Edge Devices. Checked .
- Cybersecurity and Infrastructure Security Agency and Office of Management and Budget. FY 2026 & FY 2027 CIO FISMA Metrics, Version 1.1 (September 1, 2026). Checked .
- Office of Management and Budget. M-26-18, Scaling Use of Login.gov to Deliver a Universal Sign-on for Public Services (August 31, 2026). Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the table where needed.