# Checklist: meeting OMB M-26-14 logging deadlines after CISA’s reference architecture

Thirteen steps for a federal agency’s CIO, CISO and security operations center, from the Agency Logging Plan due 90 days after CISA released the Logging Reference Architecture on August 20, 2026 to Advanced maturity at 320 days.

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

## Who this is for

OMB Memorandum M-26-14, dated May 22, 2026, applies to agencies as defined in 44 U.S.C. 3502 and rescinds M-21-31 effective immediately. It does not apply to national security systems or to the Defense Department and Intelligence Community systems described in 44 U.S.C. 3553(e) [1]. It asks agencies to organize logging around two objectives, continuous event monitoring (CEM) and threat hunting, investigation, response and forensics (THIRF) [1]. What the memorandum asks for is set out in our [explainer](https://insights.moraph.com/omb-m-26-14-federal-logging-requirements-explained).

## The clock and our dates

The memorandum’s deadlines run from the release of CISA’s Logging Reference Architecture (LRA), not from the memorandum’s date: 90 days for the first Agency Logging Plan, then 120, 180 and 320 days for maturity Levels 1, 2 and 3 [1]. CISA published the LRA on August 20, 2026 [2]. Neither source gives calendar dates for these deadlines, so the steps state them as periods from the LRA’s release. Each step cites the part of the memorandum it rests on; where a step is our suggestion, it says so. The owner under each step is a typical role; the memorandum assigns duties to agencies, not to named roles. This page is not legal advice.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Set the scope: every information system the agency owns or that third parties operate for it, including IoT devices and operational technology.** (CISO) The Prioritization section applies the CEM and THIRF objectives to all information systems owned or operated by the agency or by third parties on its behalf, including IoT and OT that are part of or make up such a system. Footnote 2 excludes national security systems and the Defense and Intelligence Community systems in 44 U.S.C. 3553(e) [1].
2. **Replace references to M-21-31 in policies, procedures and contracts.** (CISO with acquisition) M-26-14 rescinds M-21-31 effective immediately [1]. Reviewing contracts that cite the event logging tiers of M-21-31, which M-26-14 rescinded, is our suggestion, since M-26-14 applies to systems third parties operate for the agency [1].
3. **Obtain the LRA and arrange to receive CISA’s notices of updates.** (Security operations center lead) The memorandum requires agencies to adhere to the LRA by its timelines, and CISA will notify agencies within five business days of any published update [1]. CISA’s LRA page lists logging@cisa.dhs.gov for questions [2].
4. **Complete the first Agency Logging Plan within 90 days of the LRA’s release and submit it to OMB and CISA.** (CISO with the CIO) The Agency Logging Plan section requires submission to OMB and CISA within 90 days of the LRA’s publication, and the Agency Actions table requires the first version within 90 days of its release [1]. CISA released the LRA on August 20, 2026 [2].
5. **Make the plan describe the operational steps for CEM and THIRF, the minimum baseline and any extra collection the agency’s threats and mission call for.** (Security architecture) The memorandum says the plan documents the actions to reach the minimum baseline and any additional collection, considering threat environment, risk profile and mission, and should be updated periodically [1]. CISA’s LRA page says the plan records decisions on baseline and above-baseline logging, source coverage, dataflow, normalization, retention, integrity protections, access controls, validation and improvement priorities [2].
6. **Measure inventory coverage with Continuous Diagnostics and Mitigation, hardware and software asset data.** (IT asset management) Appendix B, item 4 says agencies should use CDM, HWAM and SWAM data to determine whether log coverage reaches all IT, including IoT and OT. Appendix C’s Inventory Visibility element starts at 70% of a system’s assets in a centralized inventory at Level 1 and rises to 90%, updated daily, at Level 3 [1].
7. **Collect, at minimum, logs for the eleven activities in Appendix B.** (Security operations center engineering) Appendix B, item 5 lists them: the identity used, source and destination network information, object and data events, privilege changes, infrastructure changes, alerts from security tools, known indicators of compromise, anomalous activity, the data affected in an incident, the attack vector, and automated alerts for all of these [1].
8. **Keep logs searchable for 6 months and retrievable for a year after creation, without shortening any records schedule.** (Security operations center lead with the agency records officer) Appendix B, item 1 sets the retention minimum, defines searchable and retrievable, and says it does not relieve agencies of other requirements such as records schedules [1].
9. **Make logs available to the top-level security operations center and time-stamp them from a traceable source.** (Security operations center engineering) Appendix B, item 2 allows decentralized storage only if logs are readily available to the top-level agency SOC. Item 3 requires consistently accurate timestamps, with network time synchronized through NTP or an equivalent to a traceable source the agency designates [1].
10. **Reach Level 1 on every element within 120 days of the LRA’s release, Level 2 within 180 days and Level 3 within 320 days.** (CISO) The Agency Actions table sets these minimums across all elements of the maturity model; it calls Level 1 “Basic,” while Appendix C calls it “Initial” [1]. Progress is reported as the percentage of systems at each level, and overall maturity is the lowest level reached on any element [1].
11. **Plan the log management controls each level requires, up to encryption in transit and at rest and regular hashing at Level 3.** (Security operations center engineering) Appendix C’s Log Management element moves from logs stored (Level 1) to encrypted at rest (Level 2) to encrypted in transit and at rest and regularly hashed for veracity (Level 3). Its Data Retention element at Level 3 is searchable for 3 months and retrievable for 12 [1].
12. **Agree in advance how the agency will hand logs to CISA and the FBI in a compromise.** (Incident response lead with general counsel) The Log Access Requirements section requires agencies to provide logs to CISA and the FBI on request in a known or suspected compromise, in a format and by means agreed with them, within the requested time as far as practicable, and describes how legal access restrictions are handled [1]. Agreeing the format before an incident is our suggestion.
13. **After each LRA update notice, update the plan within 30 days and reach Intermediate within 60 days and Advanced within 120 days.** (CISO) These are the Ongoing Actions in the Agency Actions table [1]. Appendix A says the LRA will be re-evaluated at least once a year [1].

## Corrections

- November 15, 2026: Added that M-26-14 rescinded M-21-31, where the checklist suggests reviewing contracts that cite M-21-31’s event logging tiers, and named M-26-14 as the memorandum that applies to systems third parties operate.

## Sources

1. 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). <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 15, 2026.
2. Cybersecurity and Infrastructure Security Agency. Logging Reference Architecture (published August 20, 2026; checked November 14, 2026). <https://www.cisa.gov/resources-tools/resources/logging-reference-architecture> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-omb-m-26-14-agency-logging-plan-and-maturity>
Publisher: Moraph Insights
