# Federal agency zero trust, logging and asset visibility duties: deadlines compared

**In short:** OMB M-22-09 set zero trust goals for the end of fiscal year 2024 and is still cited: in OMB M-26-18 (August 31, 2026) as existing OMB policy, in BOD 26-02 and in the FY 2026 and FY 2027 CIO FISMA metrics. OMB M-26-14 (May 22, 2026) rescinded M-21-31 and requires an Agency Logging Plan within 90 days of the release of CISA's Logging Reference Architecture (publish date August 20, 2026, per CISA), then logging maturity Level 1, 2 and 3 within 120, 180 and 320 days of that release. BOD 23-01 requires asset discovery every 7 days and vulnerability enumeration every 14 days; BOD 26-04 sets remediation timelines from 3 days to 60 days or fix on system upgrade; BOD 26-02 requires end-of-support edge devices to be decommissioned within 12 and 18 months of its issuance on February 5, 2026.

Government · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. <https://creativecommons.org/licenses/by/4.0/>. Attribution: "Moraph Insights", <https://insights.moraph.com/compare/federal-zero-trust-and-logging-duties>.

## The table

Each cell ends with the number of its source in "Sources". Cells were checked on November 14, 2026 unless the cell gives another date. Data: <https://insights.moraph.com/compare/federal-zero-trust-and-logging-duties.csv> (CSV), <https://insights.moraph.com/compare/federal-zero-trust-and-logging-duties.json> (JSON).

| Instrument | Duty | Deadline as stated | Source |
|---|---|---|---|
| OMB M-22-09 (zero trust strategy) [1] | Meet specific zero trust standards and objectives, organized by CISA's five pillars: identity, devices, networks, applications and workloads, and data [1] | By 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, 2022 [1] | M-22-09 [1] |
| M-22-09 as cited in OMB M-26-18 (August 31, 2026) [8] | To manage digital identity, agencies should follow applicable law and existing OMB policy, including M-19-17, M-21-04 and M-22-09 [8] | No deadline stated for this point [8] | M-26-18, footnote 5 [8] |
| M-22-09 as cited in BOD 26-02 [6] | When 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 transit [6] | No deadline stated for this point [6] | BOD 26-02, Background [6] |
| M-22-09 as cited in the FY 2026 and FY 2027 CIO FISMA metrics [7] | The system interconnections metrics (network micro-segmentation, API traffic, interconnection security) reflect requirements under BOD 26-02, M-22-09 and related directives [7] | CIO metrics are reported through CyberScope: FY26 Q4 and annual by October 30, 2026; FY27 Q1 by January 29, 2027; then quarterly to October 29, 2027 [7] | CIO FISMA Metrics v1.1, reporting instructions and system interconnections section [7] |
| OMB M-26-14 (logging) [2] | Rescinds 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 technology [2] | Rescission of M-21-31 effective immediately (memo dated May 22, 2026) [2] | M-26-14, Prioritization [2] |
| CISA Logging Reference Architecture (publish date August 20, 2026) [3] | CISA, 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 Model [2] | CISA to publish within 90 days of the memo's date [2] | M-26-14, Reference Architecture and Appendix A [2] |
| M-26-14 Agency Logging Plan [2] | Submit an Agency Logging Plan to OMB and CISA that provides for meeting the memo's minimum requirements [2] | Within 90 days of the release of the reference architecture [2] | M-26-14, Agency Logging Plan and Agency Actions [2] |
| M-26-14 logging maturity model [2] | Reach 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 level [2] | Level 1 within 120 days, Level 2 (Intermediate) within 180 days and Level 3 (Advanced) within 320 days of the release of the reference architecture [2] | M-26-14, Agency Actions and Appendix C [2] |
| M-26-14 updates to the reference architecture [2] | When CISA notifies agencies of an updated reference architecture: update the Agency Logging Plan and regain the required maturity levels [2] | Plan within 30 calendar days; Intermediate within 60 calendar days; Advanced within 120 calendar days of CISA's notice [2] | M-26-14, Agency Actions (ongoing) [2] |
| M-26-14 minimum logging baseline [2] | Logs 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 changes [2] | Appendix 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 requirements [2] | M-26-14, Appendix B [2] |
| M-26-14 log access [2] | After 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 law [2] | Within the timeframes CISA or the FBI request, to the greatest extent practicable [2] | M-26-14, Log Access Requirements [2] |
| CISA BOD 23-01 (asset visibility) [4] | Automated 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 possible [4] | By April 3, 2023 [4] | BOD 23-01, Required Actions [4] |
| CISA BOD 23-01 (CDM reporting and on-demand scans) [4] | Feed enumeration results into the CDM Agency Dashboard; run on-demand asset discovery and vulnerability enumeration when CISA asks [4] | By 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 days [4] | BOD 23-01, Required Actions [4] |
| CISA BOD 26-04, Phase I (issued June 10, 2026) [5] | Update 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 quarter [5] | Effective immediately [5] | BOD 26-04, Required Actions, Phase I [5] |
| CISA BOD 26-04, Phase III remediation [5] | Remediate 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 first [5] | Phase 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 automatable [5] | BOD 26-04, Phase III and Appendix A, Table 1 [5] |
| CISA BOD 26-04, Phase III asset tagging [5] | Continuously 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 days [5] | Within 180 days of issuance [5] | BOD 26-04, Phase III [5] |
| CISA BOD 26-02 (issued February 5, 2026), inventory [6] | Update supported edge devices running end-of-support software; inventory devices on CISA's end-of-support edge device list and report it to CISA [6] | Updates immediately; inventory within 3 months of issuance [6] | BOD 26-02, Required Actions [6] |
| CISA BOD 26-02, decommissioning [6] | Decommission 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 CISA [6] | Within 12 months and within 18 months of issuance [6] | BOD 26-02, Required Actions [6] |
| CISA BOD 26-02, continuous discovery [6] | Set 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 date [6] | Within 24 months of issuance [6] | BOD 26-02, Required Actions [6] |

## 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

1. Office of Management and Budget. M-22-09, Moving the U.S. Government Toward Zero Trust Cybersecurity Principles (January 26, 2022). <https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf> Checked November 14, 2026.
2. 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. <https://www.whitehouse.gov/wp-content/uploads/2026/05/M-26-14-Ensuring-Effective-and-Efficient-Agency-Logging-and-Network-Visibility-to-Defend-Against-Evolving-Cyber-Threats.pdf> Checked November 14, 2026.
3. Cybersecurity and Infrastructure Security Agency. Logging Reference Architecture (resource page). <https://www.cisa.gov/resources-tools/resources/logging-reference-architecture> Checked November 14, 2026.
4. Cybersecurity and Infrastructure Security Agency. BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks. <https://www.cisa.gov/news-events/directives/bod-23-01-improving-asset-visibility-and-vulnerability-detection-federal-networks> Checked November 14, 2026.
5. Cybersecurity and Infrastructure Security Agency. BOD 26-04: Prioritizing Security Updates Based on Risk, including Table 1: Remediation Timelines. <https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk> Checked November 14, 2026.
6. Cybersecurity and Infrastructure Security Agency. BOD 26-02: Mitigating Risk From End-of-Support Edge Devices. <https://www.cisa.gov/news-events/directives/bod-26-02-mitigating-risk-end-support-edge-devices> Checked November 14, 2026.
7. Cybersecurity and Infrastructure Security Agency and Office of Management and Budget. FY 2026 & FY 2027 CIO FISMA Metrics, Version 1.1 (September 1, 2026). <https://www.cisa.gov/sites/default/files/2026-09/fy26-fy27-fisma-cio-metrics-508.pdf> Checked November 14, 2026.
8. 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). <https://www.whitehouse.gov/wp-content/uploads/2026/08/M-26-18-Scaling-Use-of-Login.gov-to-Deliver-a-Universal-Sign-on-for-Public-Services.pdf> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/compare/federal-zero-trust-and-logging-duties>
Publisher: Moraph Insights
