← Back to research report

Document · 2022-12-02

M-23-03 FY23 FISMA Guidance

Complete document.

About this text

This text has been formatted for reading on screen. Page links open the original PDF. Older scans may contain errors in words, tables, or reading order.

Document sections
Jump to a PDF page · 17 included

EXECUTIVE OFFICE OF THE PRESIDENT OFFICE OF MANAGEMENT AND BUDGET WASHINGTON, D.C. 20503 THE DIRECTOR

De cember 2, 2022 M- 23-03 ME

MORANDUM FOR THE HEADS OF EXECUTIVE DEPARTMENTS AND AGENCIES FRO

M: Shalanda D. Young SU BJECT: Fiscal Year 2023 Guidance on Federal Information Security and Privacy Management Requirements Pur pose Thi s memorandum provides agencies with Fiscal Year (FY) 2023 reporting guidance and deadlines in accordance with the Federal Information Security Modernization Act of 2014 (FISMA).1 It rescinds the following memoranda:

• M- 22-05, Fiscal Year 2021-2022 Guidance on Federal Information Security and Privacy Management Requirements

• M-02-09, Reporting Instructions for the Government Information Security Reform Act and Updated Guidance on Security Plans of Action and Milestones Thi s memorandum does not apply to national security systems,2 although agencies are encouraged to leverage this guidance to inform agency national security system management processes.

Int roduction The United States Government has made substantial progress in implementing the bold changes and significant investments the President outlined in Executive Order 14028, Improving the Nation’s Cybersecurity (EO 14028), incr easing deployment of critical security tools throughout the Federal enterprise and rethinking fundamental approaches to cybersecurity. However, sophisticated adversaries continue to challenge digital defenses in an attempt to undermine the Federal IT systems and services the American public relies upon. To combat this challenge, agencies are implementing cybersecurity practices called for in EO 14028 and moving away from a reliance on traditional security practices focused on perimeter-based defenses. In addition,

1 44 U.S.C.

§§ 3551 et seq.

2 As defined in 44 U.S.C.

§ 3552.

2

agencies will continue to reduce the technical debt of legacy systems and focus on modernizing information technology.

EO 14028 put forward a call to action to modernize and transform Federal systems to meet or exceed leading cybersecurity practices. The EO focused on setting and establishing clear security requirements (applying multifactor authentication, encrypting data at rest and in transit, improving endpoint detection and response); enhancing the integrity and transparency of the software supply chain; and creating a Cyber Safety Review Board to evaluate and learn from cyber incidents. Building upon this EO, the Office of Management and Budget (OMB) released the Federal Zero Trust Strategy (OMB Memorandum M-22-09, Moving the U.S. Government Toward Zero Trust Cybersecurity Principles), laying out specific goals for agencies to achieve through Fiscal Year 2024.

A s required by M-22-09, agencies submitted detailed zero trust implementation plans to OMB in the spring of 2022. Since that time, a cross-Government team of cybersecurity experts from OMB, the Office of the National Cyber Director (ONCD), and the Cybersecurity and Infrastructure Security Agency (CISA) have continuously engaged with agencies to refine these plans and support their efforts to meet ambitious, yet achievable, goals. This is a significant shift in agency cybersecurity practices and operations, and both agencies and the Executive Office of the President are demonstrating a commitment to making this shift and achieving a new and more resilient foundational state.

In July 2022, OMB and ONCD released OMB Memorandum M-22-16, Administration Cybersecurity Priorities for the FY 2024 Budget, defining three key cyberse curity priorities for agencies to address within the FY 2024 Budget. One of these three pillars is “Improving the Defense and Resilience of Government Networks,” a core focus of FISMA.

T o ensure agencies are continuing to drive forward implementation of EO 14028 and subsequent Administration actions, this memorandum is designed to modernize FISMA data collection in five key ways:

Measuring zero trust implementation: Agencies are required to take discrete, time-bound steps by FY 2024 to meet the goals of EO 14028 and M-22-09. OMB has worked with agency chief information officers (CIOs) and chief information security officers (CISOs), as well as CISA, to ensure that agency metrics align with critical security outcomes. OMB will continue to align performance management under FISMA with benchmarks for the implementation of zero trust architecture and the NIST Cybersecurity Framework (CSF). The Federal Government no longer considers any Federal system or network to be “trusted” unless that confidence is justified by clear data; this means internal traffic and data must be considered at risk. Historically, FISMA metrics have not focused enough on defense measures beyond the perimeter. Because modern cyber threat campaigns have continued to find success in breaching perimeters, it is essential to evaluate cybersecurity measures throughout the entire ecosystem. With this guidance, OMB continues to refine and update metrics to assess agencies’ protection from threat actors. Adequate protection derives not simply from the maintenance of outer defenses, but also from restricting the attack surface available to threat actors, and the rapid detection and neutralization of malicious activity.

3

Clear, ac tionable, and outcome-focused data: M-22-05 initiated significant changes in the Government’s approach to FISMA oversight and CIO and Inspector General (IG) metrics collection. This memorandum builds upon those advancements and will ultimately provide the Executive Office of the President, Congress, and the public with a clear view of agencies’ security achievements and challenges. To ensure agencies can continue to focus on outcomes over manual reporting, the FY 2023 CIO metrics will fully automate certain reporting. Even where full automation is not yet achievable, this memorandum requires CISA to provide performance and incident data to OMB in an automated manner and machine-readable format.

Collecting and reviewing data consumes time that could be spent on security outcomes. OMB intends for agencies to collect only data that provides critical insight into their security stance.

T his guidance (and associated CIO and IG metrics) will provide clarity on agency maturity in high-impact capability areas and inform risk-based decisions and agency investments—all while reducing the burden on individual agencies.

Ensuring input from across the Federal enterprise: T his guidance also establishes a CISO Council FISMA Metrics Subcommittee tasked with advising OMB on refining and improving FISMA guidance and metrics. Areas of review for FY 2023 will include:

• Identifying appropriate means and intervals for testing critical systems.

• Clarifying the components and boundaries of FISMA systems so that agencies may identify and assess those systems, including High Value Assets, more consistently.

• Prioritizing automation of specific metrics for FY 2024 and beyond, as well as working with agencies to prepare for the necessary processes to ensure accurate data.

• Incorporating Continuous Diagnostic and Mitigation (CDM) Data into FISMA reporting.

• Recommending additional methodologies to capture information regarding agency risk- based decisions and mitigations, as well as agency exceptions to OMB policies and guidance, and to CISA Emergency Directives and Binding Operational Directives (BOD).

Improving security-privacy coordination: While independent and separate disciplines, security and privacy also have a close relationship.3 Coordination across these disciplines is essential to managing security and privacy risks and to complying with applicable requirements,4 including those outlined in this memorandum. For example, when a breach5 occurs, such coordination is critical, and this memorandum underscores the guidance provided on roles regarding tracking and documenting the breach in OMB Memorandum M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information.

Improving incident response: This memorandum builds on Administration efforts to ensure CISA works closely with Federal agencies in building a cohesive, coordinated incident response infrastructure. EO 14028 laid out a series of actions to modernize the Federal Government’s investigative and remediation capabilities. If incidents are not properly reported—or updates are

3 OMB Circular A-130, Managing Information as a Strategic Resource, § 4(h) (July 28, 2016).

4 Id.

5 As defined in OMB Memorandum M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information, § III(C) (Jan. 3, 2017). This definition applies to “breach” throughout this memorandum.

4

improperly logged—the detection, investigation, and remediation of sophisticated cyber threats may suffer.

Section I: Increasing Coordination with and Visibility of Continuous Diagnostics and Mitigation Capabilities

CISA’s Continuous Diagnostics and Mitigation (CDM) Program: Overview

The CDM Program allows Federal agencies to monitor vulnerabilities and threats to their systems in near real-time. This increased situational awareness helps agencies prioritize actions to mitigate or accept cybersecurity risks. The CDM Program works with agencies to deploy commercial off-the-shelf tools that provide enterprise-wide visibility of assets, users, and activities. This enables agencies to more effectively monitor, defend, and respond to cyber incidents.

The CISA CDM Program Management Office (PMO) categorizes participating agencies into groups for the purposes of bundling task orders and enabling closer oversight of agencies’ CDM implementation. All Chief Financial Officer (CFO) Act 6 agencies, with the exception of the Department of Defense (DOD), participate in CDM, along with dozens of non-CFO Act agencies. While the CDM PMO, working with the General Services Administration (GSA), manages related contracts on behalf of the agencies, agencies are responsible for the state of their cybersecurity posture and must work closely with CISA to accomplish CDM program goals within their own enterprises. By January 2023, CISA will begin providing OMB monthly data on implementation progress by all Federal agencies.

CDM Implementation and Agency Responsibilities and Expectations

Automated Reporting: By the end of FY 202 3, agencies are required to report at least 80 percent of Government-furnished equipment (GFE) through the CDM program. Agencies will make progress toward that outcome by meeting the requirements of BOD 23-01, Im proving Asset Visibility and Vulnerability Detection on Federal Networks. CISA will provide OMB with performance data, including information on scanning cadence, rigor, and completeness of vulnerability enumeration starting in the third quarter of FY 2023, as part of the FY 2023 metrics. Starting in the first quarter of FY 2023, agencies must provide data on assets in an automated manner to the maximum extent feasible. CISA and the CISO Council FISMA Metrics Subcommittee will work with OMB to identify future metrics for automation in FY 2024 and beyond. Fully automated identification of certain assets through CDM may not be feasible.

Agencies must continue to report such assets through CyberScope.

T o assist agencies in better understanding and identifying “instances of critical software,” CISA will make available to agencies a list of software categories that meet the definition of critical software no later than January 15, 2023. CISA will include examples of software products in each category so that FISMA reporting on this metric remains consistent.

6 The CFO Act agencies are defined in 31 U.S.C.

§ 901(b).

5

Acquiring Capabilities: Although agencies may acquire continuous monitoring tools through means other than current or future CDM acquisition vehicles (CDM Dynamic and Evolving Federal Enterprise Network Defense [DEFEND], GSA IT Schedule 70 CDM Tools Special Item Number, etc.), agencies must provide sufficient justification before pursuing acquisition tools not aligned with the CDM program.7 A justification memorandum must be sent from the agency CISO to the CDM PMO, the relevant OMB Resource Management Office (RMO), and the OMB Office of the Federal Chief Information Officer (OFCIO) for concurrence. OMB may reevaluate agency justification memoranda.

Agencies must meet all of the CDM Federal Dashboard reporting requirements. Further, when agencies exchange data with the Federal Dashboard, they are responsible for responding to risks identified through the CDM program and the agency dashboard. Agencies are encouraged to provide the CDM PMO with feedback on existing tools and input on additional tools that may prove valuable for current or future CDM acquisition vehicles.

Resource Allocations: When the CDM PMO procures cybersecurity tools on behalf of an agency to fulfill specific CDM requirements, the PMO will cover the license and maintenance costs of the base year and the maintenance cost for the first option year. Otherwise, CFO Act agencies are responsible for the operations and maintenance costs (e.g., licensing costs) of their CDM-related tools and capabilities. Agencies are required to submit separate, CDM-specific line items in their annual budget documents (see OMB Circular A- 11), including their c ongressional justification documents, as applicable. In addition, each agency should work with its OMB RMO to prepare a spending plan that details the resources (including estimated staff time) dedicated to CDM. Each agency shall, in coordination with its RMO, build CDM requirements into budget plans in future years. For non-CFO Act agencies that are unable to pay for CDM, the CDM PMO will cover all costs.

8

Section II: Internet of Things

The Internet of Things Cybersecurity Improvement Act of 2020

9 (IoT Act) required the National

Institute of Standards and Technology (NIST) to publish guidelines and standards10 for: (1) the appropriate use by Federal agencies of Internet of Things (IoT) devices; and (2) addressing and sharing information about the security vulnerabilities of those devices.11 Those standards and guidelines apply to any Federal entity that qualifies as an “agency” within the meaning given in

44 U.S.C.

§ 3502(1).

The IoT Act specifies particular implementation measures for CFO Act agencies, other than the Department of Defense. Before any of those agencies may enter into a contract for IT or IT services, the agency CIO must review and approve the contract, as required by 40 U.S.C.

7 A justification should be provided from the agency CISO to the CDM PMO, the relevant OMB Resource Management Officer, and the OMB Office of the Federal Chief Information Officer for each contract period of performance to ensure existing tools keep pace with CDM contract vehicle tools.

8 Non-CFO Act agencies must provide written justification to both OMB and CISA for approval. 9Pub. L. No. 116-207 ( 2020) , codified at 15 U.S.C. §§ 278g-3a to -3d.

10 SP 800-213 and SP 800-213A.

11 15 U.S.C.

§§ 278g-3b(a)(1), 278g-3c(a).

6

§ 11319(C)(i)(I). Under the IoT Act, if the CIO conducts such a review of a contract for an IoT device, and determines during that review that using the device would prevent the agency from complying with NIST’s IoT standards and guidelines, then the agency is prohibited from using the device, procuring or obtaining the device, or renewing a contract to procure or obtain the device.

12

That prohibition may be waived, but only if the agency CIO first determines that at least one of the following conditions is met:

1) The waiver is necessary in the interest of national security; 2) Procuring, obtaining, or using the IoT device is necessary for research purposes; or 3) The device is secured using alternative and effective methods appropriate to its function. 13

The CIO shall memorialize and justify any such determination in a signed memorandum for the agency head. Upon receiving that memorandum, the agency head may issue a waiver of the prohibition on use or acquisition of the device in question. The waiver must include the following, at a minimum:

1) Date of issuance; 2) The device(s) and any associated solutions or platforms covered; 3) A description of the purposes for which or the circumstances in which the device may be acquired or used. 4) The effective period of the waiver, which may not exceed 2 years; 5) A copy of the memorandum setting out the CIO’s determination; and 6) The signature of the agency head or their designee.

A copy of any waiver signed by the agency head must be provided to the agency CIO. CIOs must make these waivers available to OMB OFCIO upon request, and ensure that such waivers are documented in relevant system security plans and shared with acquisition officials for documentation in relevant contract files. OMB has determined no additional policies or clarifications are required at this time for agencies to implement this waiver process.

S ection III: Requirements for FISMA Reporting to OMB and DHS

CIO, IG, and Senior Agency Official for Privacy (SAOP) metrics together provide insight into an agency’s information security and privacy performance. To meet FISMA requirements, agencies report the status of their information security and privacy programs to OMB, and IGs conduct annual independent assessments of those programs. OMB and CISA collaborate with interagency partners to develop the CIO FISMA metrics, and with IG partners to develop the IG FISMA metrics to facilitate these processes. OMB also develops SAOP metrics for Federal privacy programs.

12 15 U.S.C.

§ 278g-3e(a).

13 Id.

§ 278g-3e(b)(1).

7

For consistency of reporting across the agency, the SAOP and CIO should coordinate on responses to the annual CIO and SAOP metrics, where there may be crossover.

Table I: Annual and Quarterly FISMA Reporting Deadlines (FY 2023)

Activities Deadlines Responsible Parties

• Annual CIO and SAOP Metrics

• Annual Report

• Agency Head Letter

• October 31, 2023 (FY 2023) All agencies

• Annual IG Metrics • July 31, 2023 (FY 2023, Core metrics + Supplemental Metrics Group 1)

• July 31, 2024 (FY 2024, Core metrics + Supplemental Metrics Group 2)14 All agencies

• Quarterly CIO Metrics • January 17, 2023 (Q1 FY 2023)

• April 14, 2023 (Q2 FY 2023)

• July 14, 2023 (Q3 FY 2023)

• CFO Act agencies must report on all metrics

• Non-CFO Act agencies must report on all EO- related metrics 15

Section IV: CIO Reporting

OMB and CISA use CIO metrics reporting to track implementation of NIST standards, as well as other cybersecurity-related initiatives, including those in support of EO 14028.

All agencies must update their CIO metrics quarterly. Reflecting the Administration’s shift in focus from compliance to risk management, as well as the guidance and requirements outlined in OMB Memorandum M-19- 03, Strengthening the Cybersecurity of Federal Agencies by Enhancing the High Value Asset Program, Binding Operational Directive 18-02, Securing High Value Assets, and High Value Asset Program Supplemental Guidance 3.0, th e CIO m etrics are not limited to assessments and capabilities within NIST security baselines, and agency responses should reflect actual implementation levels.

O MB will identify agency programs that require additional support using CIO metrics and will utilize targeted agency engagement sessions to improve outcomes of agency information security programs and cybersecurity-mission programs.

14 In FY23, metrics will be Core Metrics plus supplemental metrics and will be evaluated on a 2-year cycle based on a calendar agreed to by Council of the Inspectors General on Integrity and Efficiency ( CIGIE), the CISO Council, OMB, and CISA. 15 Note that only EO metrics will be captured quarterly. Other metrics will be reported semi- annually.

8

Section V: IG Reporting

OMB, CISA, the Council of the Inspectors General on Integrity and Efficiency (CIGIE), agency CISOs, and other stakeholders coordinate in the development of a set of metrics for use by IGs in their evaluation of the effectiveness of agency information security programs and practices.

These metrics are referred to as “IG metrics.” All agencies will report on IG metrics annually, through an assessment conducted by the agency IG or an independent assessor. OMB is encouraging agencies to continue their shift to a continuous assessment process for their independent assessment. To help facilitate this, OMB and CIGIE are transitioning the IG metrics process to a multi-year cycle, as described below.

OMB selected a core group of metrics, representing a combination of Administration priorities and other highly valuable controls, that must be evaluated annually. The remainder of the standards and controls will continue to be evaluated in metrics on a 2-year cycle based on a calendar agreed to by CIGIE, the CISO Council, OMB, and CISA. These changes do not in any way limit the scope of IG authority to evaluate information systems on an as-needed or ad-hoc basis.

Historically, the findings of an IG assessment were released alongside annual reporting in October, but the agency assessed may not receive funding to remediate any problems identified until two or more years after the date of the report. To help remedy this situation, OMB shifted the due date of the IG metrics from October to July to better align the release of IG assessments with the development of the President’s Budget. Use of this reporting timeline began in FY 2022, starting with the core metrics.

Reflecting OMB’s shift in emphasis away from compliance in favor of risk management, IGs are encouraged to evaluate the IG metrics based on the risk tolerance and threat model of their agency, and to focus on the practical security impact of weak control implementations, rather than strictly evaluating from a view of compliance or the mere presence or absence of controls.

OMB will continue to work with CIGIE in evaluating the current process for overall improvements. A focus for FY23 will be to evaluate current methods for determining effectiveness of cybersecurity program management across the Federal Government.

Section VI: SAOP Reporting

As handling privacy issues becomes ever more important to agencies’ ability to deliver on their missions, agencies must take appropriate measures to manage privacy risks and comply with privacy requirements.

Agencies are required to submit their SAOP metrics annually. In addition to those metrics, SAOPs must submit each of the following items as separate documents through CyberScope:

• The agency’s privacy program plan; 16

16 OMB Circular A-130, Appendix I § 4(c)(2), 4(e)(1).

9

• A description of any changes made to the agency’s privacy program during the reporting period, including changes in leadership, staffing, structure, and organization;

• The agency’s breach response plan;17

• The agency’s privacy continuous monitoring strategy;18

• The Uniform Resource Locator (URL) for the agency’s privacy program page,19 as well as the URL for any other sub-agency-, component-, and/or program-specific privacy program pages; and

• The agency’s written policy to ensure that any new collection or use of Social Security numbers (SSNs) is necessary, along with a description of any steps the agency took during the reporting period to explore alternatives to the use of SSNs as a personal identifier.

20

As described in OMB Circular A- 108, Federal Agency Responsibilities for Review, Reporting, and Publication under the Privacy Act, OMB uses these reports from agencies to develop its annual FISMA report to Congress.21

Section VII: Agency Head Letter for Annual Reporting Requirement to OMB

FISMA requires agency heads to be responsible for ensuring their respective agencies maintain protections commensurate with the risk and magnitude of the harm resulting from the unauthorized access, use, disclosure, disruption, modification, or destruction of: (1) information collected or maintained by or on behalf of an agency; or (2) information systems used or operated by an agency or by a contractor of an agency or other organization on behalf of an agency.

Agency heads must maintain awareness of their agency’s information security programs and direct CIOs and CISOs to implement appropriate security measures and, where necessary, take remedial actions to address known vulnerabilities and threats.

Agency heads also are ultimately responsible for ensuring the protection of privacy interests and the responsible management of personally identifiable information within the agency. Executive Order 13719 requires each agency head to designate or re-d esignate an SAOP who has agency- wide responsibility and accountability for the agency’s privacy program.22

Where there is crossover between their respective areas of responsibility, CIOs, CISOs, and SAOPs must coordinate on the contents of the agency head letter—e.g., in reporting on breaches and major incidents that are breaches, in accordance with the roles for tracking and documenting breaches outlined in OMB Memorandum M-17-12.

23

17 OMB Memorandum M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information

(Jan. 3, 2017).

18 OMB Circular A-130, Appendix I § 4(d)(9), 4(e)(2).

19 OMB Memorandum M-17-06, Policies for Federal Agency Public Websites and Digital Services (Nov.

8, 2016).

20 OMB Circular A-130, Appendix I § 5(f)(1)(f).

21 OMB Circular A-108 § 13 (Dec.

2016).

22 OMB Memorandum M-16-24, Role and Designation of Senior Agency Officials for Privacy (Sept.

15, 2016).

23 OMB M-17-12 § VIII.

10

Requirement: OMB requires a signed letter from the agency head to the OMB Director and DHS Secretary as part of the annual reporting package to OMB to verify the agency head’s awareness and validate the agency’s FISMA report. The letter must contain the following information:24 A. A detailed assessment of the adequacy and effectiveness of the agency’s information security policies, procedures, and practices, including details on their assessment of FY 2022 FISMA CIO metrics; B. Details on the total number of information security incidents, 25 including a specification of the total number of breaches, reported through the CISA Incident Reporting System; and C. A description of each major incident, if applicable, with the following details: o The incident description, including attack vector, response, and remediation actions the agency has completed; o If the major incident was a breach, a description of the affected information26 and the number of individuals potentially affected by the breach;27 o Threats and threat actors, vulnerabilities, and mission and system impacts; o Risk assessments conducted on the information system before the date of the major incident; and o The status of compliance of the affected information system with security requirements at the time of the major incident.

Reporting Method: Agencies must upload this letter to CyberScope as part of their annual submission. Agencies shall not send OMB or DHS hardcopy submissions. Section VIII : Annual Reporting to Congress and the Government Accountability Office

In addition to requiring the submission of agency annual FISMA reports to OMB and DHS, FISMA requires agencies to submit 28 their annual FISMA reports to the Chairperson and Ranking Member of the following Congressional committees:29

1. House Committee on Oversight and Government Reform;

2. House Committee on Homeland Security;

3. House Committee on Science, Space, and Technology;

4. Senate Committee on Homeland Security and Governmental Affairs;

5. Senate Committee on Commerce, Science, and Transportation; and

6. The appropriate authorization and appropriations committees of the House and Senate.

Additionally, agencies must provide a copy of their reports to the Comptroller General of the United States.

24 44 U.S.C.

§ 3554. 25 FISMA defines “incident” as “an occurrence that – (A) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (B) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies.”

26 44 U.S.C.

§ 3554(c)(1)(A)(iii)(II).

27 44 U.S.C.

§ 3554(c)(1)(A)(iii)(I). 28 Agencies should consult with their legislative affairs office (or equivalent) for instructions on how to submit materials to Congress and the GAO.

29 44 U.S.C.

§ 3554.

11

Agency FY22 reports are due to Congress and the Government Accountability Office (GAO) by March 1, 2023. 30

Section IX: Incident Reporting Requirements

OMB is providing the following guidance to assist agencies in submitting incident response data and to promote coordination with the responsible authorities.

Incident Reporting

Agencies must report incidents to CISA according to current and updated requirements in the CISA Federal Incident Notification Guidelines. 31 This includes events that have been under investigation for 72 hours without successful determination of the event’s root cause or nature (i.e., malicious, suspicious, benign).

T his reporting also includes determinations for the impact category, attack vector, and incident attributes. CISA then uses these details, as well as several other categories of information, to produce a CISA Cyber Incident Scoring System score, which provides a repeatable and consistent mechanism for estimating the risk of an incident.

T o ensure OMB is able to maintain appropriate situational awareness and oversight of incidents impacting the Federal enterprise, CISA shall provide OMB with the following:

# Action Deadline 1 Details for all incidents received through the CISA Incident Reporting System, to be delivered on a monthly basis. No later than the 15th of each month. 2 Summary report of all incidents scored as a medium

(yellow) priority-level and above, including whether these were elevated as a result of a campaign and the weights for each category. No later than the 15th of each month.

Modernizing Incident Reporting

As previously indicated in M-22-05, CISA will provide OMB real-time access to incident reporting information no later than December 2022. CISA will ensure this data is transmitted between agencies and CISA in a machine-readable format. By April 2023, CISA will provide OMB with data regarding both individual agencies’ performance in providing accurate, machine- readable data to CISA, as well as any gaps CISA has in receiving, updating, or maintaining such records.

30 OMB will not review, clear, or provide a template for the reports. Agencies should submit reports directly to Congress and the GAO. 31 FISMA also requires agencies to notify and consult with the Federal information security incident center established in 44 U.S.C. § 3556 regarding any information security incidents. 44 U.S.C. § 3554(b)(7)(C)(ii).

12

Major Incident Definition

FISMA directs OMB to define the term “major incident” and further instructs agencies to notify Congress in the event of a “major incident.” This memorandum provides agencies with a definition and framework for assessing whether an incident is a major incident for purposes of the congressional reporting requirements under FISMA and provides specific considerations for determining the circumstances under which a breach constitutes a major incident. This guidance does not preclude an agency from reporting an incident or breach to Congress that falls below the threshold for a major incident.

Appropriate analysis of the incident will include the agency CIO, CISO, mission or system owners, and, in the case of a breach, the SAOP, as well. Agencies may consult with OMB and CISA to make a major incident determination.

A major incident is EITHER:

A. Any incident that is likely to result in demonstrable harm to the national security interests, foreign relations, or the economy of the United States, or to the public confidence, civil liberties, or public health and safety of the American people.

32 Agencies

should determine the level of impact of the incident by using the existing incident management process established in National Institute of Standards and Technology

(NIST) Special Publication (SP) 800-61, Computer Security Incident Handling Guide,

OR

B. A breach that involves personally identifiable information (PII) that, if exfiltrated, modified, deleted, or otherwise compromised, is likely to result in demonstrable harm to the national security interests, foreign relations, or the economy of the United States, or to the public confidence, civil liberties, or public health and safety of the American people.

33

As with other incidents, agencies should assess each breach on a case-by-case basis to determine whether it meets the definition of a major incident. This memorandum requires a determination of major incident for any unauthorized modification of,34 unauthorized deletion of,35

32 Using the CISA Cyber Incident Scoring System, this includes Level 3 events (orange), defined as those that are "likely to result in a demonstrable impact to public health or safety, nation al security, economic security, foreign relations, civil liberties, or public confidence"; Level 4 events (red), defined as those that are "likely to result in a significant impact to public health or safety, national security, economic security, foreign r elations, or civil liberties"; and Level 5 events (black), defined as those that "pose an imminent threat to the provision of wide -scale critical infrastructure services, national government stability, or the lives of US persons."

33 The analysis for reporting a major breach to Congress is distinct and separate from the assessment of the potential risk of harm to individuals resulting from a suspected or confirmed breach. When assessing the potential risk of harm to individuals, agencies should refer to OMB Memorandum M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information (Jan. 3, 2017).

34 “Unauthorized modification” is the act or process of changing components of information and/or information systems without authorization or in excess of authorized access. 35 “Unauthorized deletion” is the act or process of removing information from an information system without authorization or in excess of authorized access.

13

unauthorized exfiltration of,36 or unauthorized access to37 the PII of 100,000 or more people; however, per the definition provided above, other factors also may lead an agency to determine that a breach is a major incident. OMB Memorandum M-17-12 details breach reporting requirements.

Reporting Major Incidents

A. Reporting to OMB and CISA

• Agencies must report to CISA and the OMB OFCIO within 1 hour of determining a major incident occurred, and should update OMB OFCIO and CISA within 1 hour of determining that an already-reported incident or breach is a major incident.

38 Agencies

must reach out to both entities directly.

• Pursuant to Presidential Policy Directive- 41 (PPD-41), United States Cyber Incident Coordination, if a cyber incident is a major incident, it is also a “si gnificant cyber incident.” Thus, a major incident as defined above will also trigger the coordination mechanisms outlined in PPD-41 and potentially require participation and actions from a Cyber Unified Coordination Group.

• A gencies should use the points of contact in Section X for reporting major incidents.

• When a breach is determined to be a major incident, the agency’s principal security operation center and SAOP must coordinate on tracking and documenting the major incident, in accordance with the roles outlined in OMB Memorandum M-17-12.39

B. Reporting to Congress and Inspectors General

• An agency must notify the appropriate Congressional committees and its Office of the Inspector General (OIG) of a major incident no later than seven days after the date on which the agency determines that it has a reasonable basis to conclude that a major incident, including a breach constituting a major incident, has occurred.

40

• This report should take into account the information known at the time of the report, the sensitivity of the details associated with the incident, and the classification level of the information.

• When a major incident has occurred, the agency must also supplement its initial notification to Congress with pertinent updates within a reasonable period of time after

36 “Unauthorized deletion” is the act or process of removing information from an information system without authorization or in excess of authorized access. 37 “Unauthorized access” is the act or process of gaining without permission logical or physical access to Federal information or a Federal information system, application, or other resource.

38 This reporting is limited to the time after a major incident determination is made and not just the detection of the incident; it is expected that an agency will take some time to determine if an incident or breach reaches the threshold to be considered “major.”

39 OMB M-17-12 § VIII.

40 FISMA requires notification of the appropriate authorization and appropriations committees of Congress, as well as the House of Representatives Committees on: (1) Oversight and Government Reform; (2) Homeland Security; and (3) Science, Space, and Technology. In the Senate, notification must be provided to the Committees on: (1) Homeland Security and Governmental Affairs, and (2) Commerce, Science, and Transpor tation. 44 U.S.C. § 3554(b)(7)(C)(iii)(III), (c)(1)(A).

14

additional information relating to the incident is discovered. The supplemental report must include summaries of: o The threats and threat actors, vulnerabilities, and impacts relating to the incident; o The risk assessments conducted of the affected information systems before the date on which the incident occurred; o The status of compliance of the affected information systems with applicable security requirements at the time of the incident; and o The detection, response, and remediation actions.

• In addition, agencies must supplement their major incident report to Congress that is to be sent no later than seven days after the date on which the agency determines that it has a reasonable basis to conclude that a major incident has occurred with another report no later than 30 days after the agency discovers a breach constituting a major incident.

41 This supplemental report must include: o A summary of information available about the breach, including how the breach occurred, based on information available to agency officials on the date the agency submits the report; o An estimate of the number of individuals affected by the breach, including an assessment of the risk of harm to affected individuals based on information available to agency officials on the date the agency submits the report; o A description of any circumstances necessitating a delay in providing notice to affected individuals; and o An estimate of whether and when the agency will provide notice to affected individuals.

Section X: Points of Contact for Incident Reporting

• Agencies should report a major incident to OMB OFCIO at CyberIncidentReport@omb.eop.gov.

• Agencies should report incidents to DHS via one of the following methods: o The CISA/US-CERT Incident Reporting Form (cisa.gov/report); o Send emails to soc@us-cert.gov; or, o Submit reports via Structured Threat Information eXpression (STIX) to autosubmit@us-cert.gov ( schema available upon request).

• Agencies should report incidents involving National Security Systems using the guidance contained in CNSSI 1010 Cyber Incident Response.

Section XI: Points of Contact for Agency Questions

• Agencies should direct questions about this memorandum, including questions regarding IoT device waivers (Section 2), and on information security program performance, to OMB OFCIO at ofcio@omb.eop.gov.

• Agencies should direct privacy-related matters to OMB’s Office of Information and Regulatory Affairs (OIRA) at privacy-oira@omb.eop.gov.

41 FISMA requires notification to be provided to the same committees identified above in the preceding footnote, plus the Committee on the Judiciary in each house of Congress. 44 U.S.C. § 3553 note.

15

• Agencies should direct questions on CyberScope reporting to CISA at FNR.FISMA@hq.dhs.gov.

• Agencies should direct questions on CDM automated reporting to CISA at CDM@cisa.dhs.gov.

• Agencies should direct questions on FISMA metrics to OMB and CISA at ofcio@omb.eop.gov and FNR.FISMA@hq.dhs.gov.

• Agencies should direct questions on submission of potentially classified information to CISA at NCCIC@dhs.ic.gov with the subject line “FISMA 2023 Submission.”

ATTACHMENT

Appendix A: Additional CISA Responsibilities and Agency Implications

16

APPENDIX A: Additional CISA Responsibilities and Agency Implications

Scanning Internet-Accessible Addresses and Systems

As required by FISMA, CISA presently provides numerous services to agencies in the interest of improving Federal information security. These responsibilities are subject to OMB oversight and applicable legal requirements.

In furtherance of its legal responsibilities and consistent with applicable law, regulation, policy, and existing Memoranda of Agreement with agencies, CISA scans internet-accessible addresses and segments of Federal civilian agency systems for vulnerabilities on an ongoing basis, as well as in response to newly discovered vulnerabilities.

No prior agency authorization is needed for one Federal agency to perform non-invasive vulnerability scanning of another Federal agency’s internet-accessible systems. Federal agencies should expect that any system accessible over the public internet is being scanned for vulnerabilities by various parties at all times, and factor this into their security operations accordingly.

For CISA’s vulnerability scanning service to be effective, it should, to the greatest extent possible, observe the same behavior in Federal systems that an adversary would be able to observe. Similarly, the origin and behavior of the scanning service should be unpredictable. To guarantee this type of emulation, CISA should initiate its vulnerability scanning service from multiple vantage points, including commercial cloud infrastructure, and from dynamically selected source addresses.

To ensure CISA can perform this function effectively, each Federal civilian agency shall:

• Ensure that CISA and agency security teams have points of contact on file with each other for rapid communication about any discovered vulnerabilities.

• On a semi-annual basis, provide, or continue providing, CISA a complete list of the agency’s internet-accessible Federal information systems and related addressing information, 42 including static internet protocol (IP) addresses for external websites, servers, and other access points, and Domain Name Service (DNS) names for dynamically provisioned systems.43

• Provide CISA with notice of changes to IP ranges at least one day in advance by emailing vulnerability@cisa.dhs.gov.

Facilitating Information Sharing

To ensure that agencies can identify, detect, and respond to emerging malicious-actor tactics, techniques, and procedures (TTPs), all agencies must ensure that, at a minimum, the CIO and the

42 CISA is not limited to the addresses and systems provided on this list when conducting its vulnerability scanning. 43 The term “dynamically provisioned system” refers to systems which are virtually hosted and operated from multiple sites, such that network traffic to the systems is distributed across multiple, discrete IP ranges or autonomous system numbers (ASNs).

17

CISO have Top Secret Sensitive Compartmented Information (TS-SCI) access. The TS-SCI clearance designation is necessary to view classified malicious-actor TTPs.

Agencies experiencing challenges in attaining the required clearances for CIO and CISO officials should contact OMB for assistance in determining how best to ensure that these officials are cleared to perform required functions and duties and fully participate in interagency information sharing. Agencies shall use the CyberScope application to report on the access of these users.