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.

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.

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.

The checklist

Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.

  1. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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].

Spotted an error? Tell us and we will check it and correct the checklist where needed.

  • OMB
  • M-26-14
  • CISA
  • Logging Reference Architecture
  • event logging
  • security operations center
  • FISMA