# Checklist: the FISMA annual cycle for an agency CIO and CISO

Fourteen steps for a federal agency’s CIO, CISO and privacy officer through the FISMA year: the program 44 U.S.C. 3554 requires, the quarterly and annual CIO metrics for fiscal years 2026 and 2027, the agency head letter, and the one-hour and seven-day clocks for major incidents in OMB M-25-04.

Checklist · Government · Regulation & Compliance. Published November 14, 2026. Last reviewed November 14, 2026.

## Who this is for

Chief Information Officers, Chief Information Security Officers and Senior Agency Officials for Privacy at federal agencies covered by the Federal Information Security Modernization Act. Section 3554 of title 44 sets what the agency head, the CIO and the agency-wide security program must do [1]. OMB Memorandum M-25-04 of January 15, 2025 sets reporting, agency head letter and major incident requirements, with a deadline table written for fiscal year 2025 [2]. The fiscal year 2026 and 2027 CIO FISMA Metrics, version 1.1 of September 1, 2026, set the CyberScope deadlines from October 2026 to October 2027 [3].

## Status as checked

As checked on November 14, 2026, OMB’s memoranda page lists no FISMA guidance memo for fiscal year 2026 or 2027 [5], so the steps rely on M-25-04 for the agency head letter, the inspector general cycle and incident reporting. CISA’s FISMA page lists the fiscal year 2026 CIO and privacy metrics alongside the earlier years’ documents [4]. The order follows the year: program foundations, the metrics calendar, the annual package, then incidents, which can arrive at any time. Where a step is our suggestion, it says so. The owner shown is the role that usually holds the work unless the statute or M-25-04 names it.

## The checklist

1. **Confirm the senior agency information security officer’s designation matches the statute, and that the CIO holds the delegated authority in writing.** (Agency head’s office with the CIO) Section 3554(a)(3) has the agency head delegate compliance authority to the CIO, including designating a senior agency information security officer whose primary duty is information security, who has the required qualifications, and who heads an office with the mission and resources to do the job [1]. Holding the delegation in writing is our suggestion.
2. **Rebuild the system inventory by FIPS 199 impact level, split between agency-operated and contractor-operated systems, and reconcile it with CDM data.** (CISO with the CDM program lead) The CIO metrics count operational unclassified systems by impact level and component (CIO-FY26-0001 and 0002) and use that count as the denominator for other metrics [3]. M-25-04 says agencies must still report their own asset counts through CyberScope where CDM cannot capture them [2].
3. **Plan testing of the management, operational and technical controls of every inventoried system at least once a year, using automated tools.** (CISO) Section 3554(b)(5) requires periodic testing with a frequency based on risk but no less than annually, covering every system in the inventory and including automated tools [1].
4. **Put the CyberScope dates in the calendar: January 29, April 30, July 30 and October 29, 2027 for fiscal year 2027, with time to review CISA’s pre-populated values.** (CIO’s FISMA reporting lead) The metrics document sets those submission deadlines and CISA pre-population dates four weeks before each; the fiscal year 2026 annual submission was due October 30, 2026. Non-CFO Act agencies report only the fourth quarter and annual periods; agencies must correct pre-populated data before the deadline and ask OMB’s Office of the Federal CIO for any extension before it passes [3].
5. **Assign an owner for each metric area tied to recent directives and orders: logging maturity, end-of-support devices, KEV remediation, AI security and supply chain risk.** (CISO) The fiscal year 2026 and 2027 metrics measure logging against the maturity model in OMB M-26-14, count end-of-life and end-of-support assets for BOD 26-02, ask for the CDM-reported mean time to remediate known exploited vulnerabilities, add pilot AI security metrics tied to the AI Use Case Inventory, and update supply chain questions under Executive Order 14306 [3].
6. **Agree with the privacy office which answers overlap, and collect the privacy documents that go to CyberScope separately.** (CIO with the Senior Agency Official for Privacy) M-25-04 asks the SAOP and CIO to coordinate where CIO and SAOP metrics cross over, and requires the SAOP to submit the privacy program plan, breach response plan, privacy continuous monitoring strategy and other listed items as separate documents [2].
7. **Have the CIO report to the agency head each year on how effective the security program is, including progress on remedial actions.** (CIO) Section 3554(a)(5) requires this annual report; section 3554(b)(6) requires a process for planning, carrying out and documenting remedial action for deficiencies [1].
8. **Draft the agency head letter early, with the incident and breach counts reconciled against the CISA Incident Reporting System.** (CIO and CISO, with the SAOP) M-25-04 requires a signed letter from the agency head to the OMB Director and the DHS Secretary, uploaded to CyberScope, assessing the adequacy and effectiveness of security policies and practices (including the CIO metrics), giving the number of incidents and breaches reported through the CISA system, and describing each major incident [2]. Drafting early and reconciling the counts is our suggestion.
9. **Send the annual FISMA report to the congressional committees and GAO directly, unclassified with any classified annex.** (CIO with legislative affairs) Section 3554(c)(1) lists the recipients and contents, including each major incident and the total number of incidents, and requires an unclassified report [1]. M-25-04 says OMB will not review, clear or provide a template for these reports [2].
10. **Agree the evidence schedule for the inspector general’s annual evaluation, starting with the core metrics.** (CISO with the Office of Inspector General) M-25-04 has IG metrics reported every year, with core metrics evaluated annually and the rest on a two-year cycle, and notes that OMB moved the IG due date from October to July, starting in fiscal year 2022, to align IG assessments with development of the President’s Budget [2]. Section 3554(b)(5)(B) allows the agency’s own testing to include testing relied on in that evaluation [1].
11. **Report incidents to CISA under the Federal Incident Notification Guidelines, including events still unexplained after 72 hours.** (Security operations center) Section 3554(b)(7)(C)(ii) requires notifying and consulting the federal information security incident center [1]. M-25-04 requires reporting under CISA’s guidelines, including events under investigation for 72 hours without a determination of root cause or nature [2].
12. **Write down who decides whether an incident is major, and what criteria they apply.** (CIO and CISO, with mission owners and the SAOP) M-25-04 defines a major incident as one likely to cause demonstrable harm to national security, foreign relations, the economy, public confidence, civil liberties, or public health and safety, and requires a major incident determination for unauthorized modification, deletion, exfiltration or access to the personal information of 100,000 or more people; the analysis includes the CIO, CISO, mission or system owners and, for a breach, the SAOP [2]. Recording who decides is our suggestion.
13. **Prepare templates and contact lists for the major incident clock: one hour to CISA and OMB, seven days to Congress and the inspector general, and 30 days for a breach supplement.** (CISO with the CIO’s front office) M-25-04 requires reporting to CISA and OMB’s Office of the Federal CIO within 1 hour of determining a major incident; notice to the appropriate committees and the OIG within seven days of a reasonable basis to conclude one occurred; updates as more is learned; and a further report within 30 days of discovering a breach that is a major incident [2]. Section 3554(b)(7)(C)(iii)(III) sets the seven-day requirement in statute [1].
14. **Put the security program’s time periods and resources into the agency performance plan, based on the risk assessments.** (CIO with the Performance Improvement Officer and CFO) Section 3554(d) requires the performance plan under 31 U.S.C. 1115 to describe the time periods and the budget, staffing and training needed to run the security program, based on the agency’s risk assessments [1].

## Sources

1. U.S. Government Publishing Office, GovInfo. 44 U.S.C. 3554, Federal agency responsibilities (United States Code, 2023 edition). <https://www.govinfo.gov/content/pkg/USCODE-2023-title44/html/USCODE-2023-title44-chap35-subchapII-sec3554.htm> Checked November 14, 2026.
2. Office of Management and Budget. M-25-04, Fiscal Year 2025 Guidance on Federal Information Security and Privacy Management Requirements (January 15, 2025). <https://www.whitehouse.gov/wp-content/uploads/2025/01/M-25-04-Fiscal-Year-2025-Guidance-on-Federal-Information-Security-and-Privacy-Management-Requirements.pdf> Checked November 14, 2026.
3. OMB, CISA and the CISO Council FISMA Metrics Subcommittee. FY 2026 and 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.
4. Cybersecurity and Infrastructure Security Agency. Federal Information Security Modernization Act. <https://www.cisa.gov/topics/cyber-threats-and-advisories/federal-information-security-modernization-act> Checked November 14, 2026.
5. Office of Management and Budget, The White House. Memoranda. <https://www.whitehouse.gov/omb/information-resources/guidance/memoranda/> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-fisma-annual-cycle-cio-ciso>
Publisher: Moraph Insights
