Federal civilian agencies
- Confirm with the CISO which rows apply; record in T1 who decided each clock started.Legal advisor
- Record in T1 when the top-level security operations center (SOC) identified the incident; the clock for the Cybersecurity and Infrastructure Security Agency (CISA) starts there.Planning
- Report to CISA within 1 hour with what you know; save the incident number.Liaison
- Open T17 for the CISA report, the major incident report and the congressional notice.Planning
- Tell the Senior Agency Official for Privacy (SAOP) of any personally identifiable information (PII) and convene the breach response team.Legal advisor
- Hand any classified information to the security office before anyone copies evidence.Incident Commander
Then work the page: Reporting obligations, Terms, Roles, What changes in each phase, Records, Who you work with.
This page is for responders at federal civilian executive branch (FCEB) agencies, and at contractors and cloud providers that run systems on an agency's behalf. Department of Defense components and defense contractors use Defense and defense contractors.
The agency reports to CISA within 1 hour of identification, decides whether the incident is a major incident, and tells Congress within 7 days of one. CISA can hunt on agency networks and issue directives mid-response. A breach of PII brings in the SAOP and a breach response team.
This page adds to the phase playbooks for scope, contain, eradicate and recover. Incident Command seats for this sector are on Command by incident type.
This sector page is an addition to the book. Primary sources checked: FISMA 2014 at 44 U.S.C. 3554; Office of Management and Budget (OMB) M-25-04, M-17-12 and M-26-14; CISA Federal Incident Notification Guidelines; Executive Order 14028; FedRAMP incident rules; NIST SP 800-61r3. The OMB memoranda, the CISA guidelines, the FedRAMP rules and CISA's directives were checked October 2026; the statute, NARA GRS 3.2 and CISA's EINSTEIN and CDM pages were checked October 2026; the executive order and NIST SP 800-61r3 were checked September 2026.
Reporting obligations
Counsel and the CISO confirm which rows apply. Record in T1 who decided that each clock started, and when. The notification deadlines table lists other regimes.
| Obligation | Who reports to whom | Clock | Starts when | What the report contains |
|---|---|---|---|---|
| Incident notification, CISA Federal Incident Notification Guidelines; breach of PII, M-17-12 | Agency's top-level SOC to CISA (M-17-12 says US-CERT, now CISA) | 1 hour | The agency's top-level CSIRT, SOC or IT department identifies an incident that potentially compromises the confidentiality, integrity or availability of a federal information system, or a suspected or confirmed breach of PII | Functional impact, information impact, recoverability, time first detected, number of systems, records and users affected, network location, and a point of contact; attack vector, indicators and mitigations if known. Best estimates first, updates as facts arrive. No sensitive PII |
| Major incident, M-25-04 | Agency to CISA and the OMB Office of the Federal Chief Information Officer, contacting both directly | 1 hour | The agency determines a major incident occurred, including an incident already reported that becomes major | The major incident determination and the incident facts |
| Major incident, 44 U.S.C. 3554(b)(7)(C)(iii) and M-25-04 | Agency to its Office of Inspector General and to Congress: the House Oversight, Homeland Security, and Science, Space, and Technology committees; the Senate Homeland Security and Governmental Affairs and Commerce, Science, and Transportation committees; and the appropriate authorization and appropriations committees | No later than 7 days | The agency determines it has a reasonable basis to conclude a major incident occurred | Initial notice, then updates within a reasonable time as information is discovered, covering threats and threat actors, vulnerabilities and impacts |
| Breach that is a major incident, M-25-04 | Agency to Congress | No later than 30 days | The agency discovers a breach constituting a major incident | How the breach occurred, the number of individuals affected and the risk of harm to them, any reason for delaying notice to them, and whether and when they will be notified |
| Notice to individuals, M-17-12 | Agency to affected individuals | As expeditiously as practicable and without unreasonable delay | The agency head decides to notify, after the breach response team assesses the risk of harm | What happened and when it was discovered, the PII involved, steps the agency took and services offered, what individuals can do, and agency contacts |
| Contractor or provider to agency | Contractor to the agency, under the contract clause | The clause's deadline. M-17-12 requires contracts to demand reports "as soon as possible and without unreasonable delay" | Suspected or confirmed breach or incident, as the clause defines it | What the clause lists. EO 14028 section 2 directed clauses requiring providers to preserve incident data and share it with the agency; check whether the contract carries one |
| FedRAMP cloud provider | Provider to FedRAMP and to each affected agency customer. Legacy procedures also send the report to CISA | Legacy procedures: 1 hour, then daily updates. Consolidated Rules for 2026, Class C: 1 hour for PAIN ratings 3 to 5, then updates every 6 hours; 24 hours for PAIN 2; 1 business day for PAIN 1. Class D: 15 minutes for PAIN 3 to 5 | Identification of an incident. Under the 2026 rules, of one that affects or is likely to affect the confidentiality or integrity of federal customer data | Contact, tracking ID, description, timeline, Potential Agency Impact N-rating (PAIN) with rationale, functional impact, recovery plan, affected agencies. A provider that has not estimated PAIN reports at PAIN 5. The 2026 rules may be adopted from July 4, 2026, are required for Rev5 certifications from January 1, 2027, and have a grace period to June 1, 2027 |
| Emergency directive or binding operational directive | Agency to CISA | Set in each directive. ED 25-03 (September 25, 2025) gave agencies about one day to submit forensic data and a week for an inventory report. ED 26-03 (February 25, 2026, Cisco SD-WAN) required patches within about two days, and a March 11, 2026 update added actions and reporting, with deadlines through March 23, 2026 (confirm against the directive on cisa.gov) | Issuance of the directive | What the directive requires, often inventory, actions taken and forensic data |
| Logs during a compromise, M-26-14 | Agency to CISA and the FBI | On request | A known or suspected compromise of a federal network | Logs and other relevant data, including from systems third parties run for the agency |
| Classified information lost or possibly compromised, 32 CFR 2001.48 | Anyone who knows to the official the agency designates. The agency head to the Director of ISOO for cases that meet the rule's criteria | Immediately | Knowledge that classified information has been or may have been lost, compromised or disclosed | Handled by the agency security office under its procedures |
Sources: 44 U.S.C. 3554; OMB M-25-04, Fiscal Year 2025 Guidance on Federal Information Security and Privacy Management Requirements, January 15, 2025, which rescinded M-24-04. OMB's memoranda list, which runs through M-26-19 of September 10, 2026, shows no FY2026 or FY2027 FISMA guidance. A July 16, 2026 inspector general FISMA evaluation still cites M-25-04, which is the current annual guidance as of October 10, 2026; OMB M-17-12, January 3, 2017; CISA Federal Incident Notification Guidelines, effective April 1, 2017; EO 14028, May 12, 2021; FedRAMP legacy incident communication and the Consolidated Rules for 2026 Incident Evaluation and Communication rules, launched June 24, 2026 and renamed from Incident Response on July 2, 2026. The Consolidated Rules gather the FedRAMP 20x requirements into one ruleset. FedRAMP published the outcome of its incident procedures comment request in notice 0012, June 3, 2026; CISA ED 25-03; ED 26-03 as dated in FedRAMP's directives page, with the patch deadline from FedRAMP notice 0006 (February 25, 2026), the update from CISA's March 11, 2026 bulletin (checked November 2026) and WaterISAC, and the final reporting date from Infosecurity Magazine, because the directive pages on cisa.gov would not open for the October and November checks; OMB M-26-14, May 22, 2026, which rescinded M-21-31; 32 CFR 2001.48.
Terms
| Term | Meaning | PIVTR-D equivalent |
|---|---|---|
| FCEB | Federal civilian executive branch agencies, the agencies CISA's directives bind | none |
| FISMA | Federal Information Security Modernization Act of 2014, 44 U.S.C. 3551 and following. Sets agency security duties, CISA's role and incident reporting to Congress | none |
| CISA | Cybersecurity and Infrastructure Security Agency. Runs the federal incident center agencies report to | Liaison contact |
| US-CERT | Former name of the federal incident center, now part of CISA. Older memoranda such as M-17-12 still say US-CERT | none |
| Major incident | An incident or PII breach likely to cause demonstrable harm to national security, foreign relations, the economy, public confidence, civil liberties, or public health and safety. A breach of PII of 100,000 or more people is a major incident. Defined in OMB's annual FISMA guidance, currently M-25-04 | A determination recorded beside the risk level in T1 |
| Breach | Loss of control or compromise of PII, including access or potential access by someone other than an authorized user, or an authorized user's access for an unauthorized purpose | T16 notices |
| PII | Personally identifiable information | none |
| Functional impact, information impact, recoverability | CISA's three impact ratings in the incident notification. Recoverability runs Regular, Supplemented, Extended and Not Recoverable | Inputs to the risk level |
| Attack vector | CISA's cause categories: Unknown, Attrition, Web, Email/Phishing, External/Removable Media, Impersonation/Spoofing, Improper Usage, Loss or Theft of Equipment, Other | Classification in T1 |
| SOC, CSIRT | Security operations center; computer security incident response team. The top-level one reports to CISA | Operations and Intelligence/Investigations |
| ED | Emergency directive. CISA orders agencies to act on a specific threat under 44 U.S.C. 3553(h), often within days | A containment trigger in T1 |
| BOD | Binding operational directive. Standing CISA requirement under 44 U.S.C. 3553(b)(2). BOD 26-04 of June 10, 2026 replaced BOD 22-01 and BOD 19-02, which CISA lists as revoked | none |
| KEV | CISA's Known Exploited Vulnerabilities catalog. Under BOD 26-04 a KEV listing is one of four factors that set remediation deadlines, with public exposure, automatability and technical impact. Agency policies had to support the new process by August 7, 2026, and the BOD 26-04 deadlines apply from December 7, 2026. The fastest tier is 3 days with forensic triage for prior compromise, and it covers KEV entries that give total control of a system. Published summaries differ on whether public exposure or an automatable exploit must also be present (confirm against Table 1 of the directive on cisa.gov) | Forensic triage follows Verification and triage |
| HVA | High value asset: a system or data set whose compromise would seriously affect the agency's mission or the public | Critical system in the containment triggers |
| FIPS 199 | Standard that rates each system Low, Moderate or High for confidentiality, integrity and availability | Input to the risk level |
| ATO | Authorization to operate. The authorizing official's written acceptance of a system's risk | T8 System owner acceptance |
| AO | Authorizing official. Senior official who accepts risk for a system and can withdraw its ATO | Signs T6 |
| SSP | System security plan. The system's boundary, components and controls | none |
| POA&M | Plan of action and milestones. Tracks each weakness to a fix date | T14 Improvement register |
| ISSO, ISSM | Information system security officer and manager. Keep a system's security posture and paperwork | none |
| CIO, CISO | Chief information officer; chief information security officer, called the senior agency information security officer in statute and OMB policy | CISO |
| SAOP | Senior Agency Official for Privacy. Leads the breach response team | none |
| CDM | Continuous Diagnostics and Mitigation. CISA program supplying tools and dashboards for asset, identity and vulnerability data | none |
| TIC | Trusted Internet Connections. Federal program for securing agency network traffic | none |
| EINSTEIN | CISA's sensors on agency internet traffic. EINSTEIN 1 still monitors traffic between agency networks and the internet. CISA retired EINSTEIN 2 and EINSTEIN 3 Accelerated in 2024 | none |
| M-26-14 maturity levels | Logging maturity from Ineffective (Level 0) to Optimal (Level 4). Replaced the M-21-31 event logging tiers EL0 to EL3, rescinded May 22, 2026 | none |
| FedRAMP | Federal program that authorizes cloud services for agency use | none |
| 3PAO | Third party assessment organization. Assesses cloud services for FedRAMP | none |
| CUI | Controlled unclassified information, governed by 32 CFR 2002 | Restricted data scenario |
| Spillage | Classified information on a system or with people not authorized for it | none. Hand to the security office |
| JCDC | Joint Cyber Defense Collaborative. CISA-led planning and sharing with industry and government | none |
| OIG | Office of Inspector General. Independent auditor and investigator inside the agency | Liaison contact |
| PPD-41, Cyber UCG | Presidential Policy Directive 41 (July 26, 2016). FBI leads threat response, CISA leads asset response. A Cyber Unified Coordination Group coordinates a significant incident | Unified command |
Roles
| Sector role | What they do in an incident | PIVTR-D or Incident Command seat |
|---|---|---|
| Agency head | Final decision on notifying individuals. Signs congressional notices when agency policy requires | Executive group |
| CIO | Takes part in the major incident determination | Executive group |
| CISO (senior agency information security officer) | Runs the response program, joins the major incident determination and the breach response team | CISO |
| SAOP | Leads breach assessment and notification to individuals | Technical Specialist beside the Legal advisor; joins unified command for a breach |
| Office of General Counsel | Advises on reporting, law enforcement and records | Legal advisor |
| Authorizing official, system owner | Approve containment and restoration on their systems, accept residual risk | Operations input; sign T3, T6 and T8 |
| ISSO, ISSM | Know the system boundary and controls, supply the SSP and inventory | Planning |
| Top-level SOC or CSIRT | Detects, reports to CISA, investigates | Operations and Intelligence/Investigations |
| Legislative affairs | Sends congressional notices and answers committee staff | Liaison |
| Public affairs | Public statements and media | Public Information Officer |
| Contracting officer | Enforces contract clauses on contractors and cloud providers | Finance/Admin |
| Records officer, FOIA officer | Set retention for incident records, and review any release | Planning |
What changes in each phase
Preparation
| # | Item | Owner |
|---|---|---|
| 1 | Write the major incident procedure: who determines (CIO, CISO, mission or system owners, SAOP for a breach), when to consult OMB and CISA, and the 1-hour and 7-day clocks | CISO |
| 2 | Review the breach response plan at least every 12 months and name the team: SAOP, CIO or designee, CISO, counsel, legislative affairs, communications | Legal advisor |
| 3 | Run a tabletop exercise with the breach response team at least once a year | Planning |
| 4 | Name the staff who report to CISA, and test their route to the CISA reporting form and the phone number 888-282-0870 | Liaison |
| 5 | Agree the congressional notice template and the committee list with legislative affairs | Liaison |
| 6 | Bring logs up to M-26-14: searchable for at least 6 months, retrievable for 12 months, clocks synchronized to a traceable time source the agency designates, and contractor systems included | Operations |
| 7 | Confirm CISA's access to endpoint detection and response (EDR) data under the agency's agreement, and check that CDM data is current | Operations |
| 8 | Write into every contractor and cloud contract a reporting deadline, evidence preservation, and access for CISA, the FBI and the OIG | Finance/Admin |
| 9 | Store the HVA list, FIPS 199 ratings and SSPs where responders can reach them during an outage | Planning |
Identification and verification
| # | Item | Owner |
|---|---|---|
| 1 | Record in T1 the time the top-level SOC identified the incident, as the CISA clock start | Planning |
| 2 | Send the CISA report within 1 hour with the required elements. If the attack vector is not known, report it as Unknown. Save the CISA incident number | Liaison |
| 3 | Rate functional impact, information impact and recoverability in CISA's terms in T2 | Intelligence/Investigations |
| 4 | Decide whether the incident is a major incident or leave the question open, and record when a reasonable basis existed and who decided | CISO |
| 5 | Report a major incident to CISA and OMB within 1 hour of the determination | Liaison |
| 6 | Tell the SAOP of any PII and convene the breach response team. M-17-12 requires the team to meet for every breach that is a major incident | Legal advisor |
| 7 | Check open CISA directives for the affected product | Intelligence/Investigations |
| 8 | Notify the OIG, the FBI and general counsel as the agency's procedures require, and record each contact in T13 | Liaison |
| 9 | If classified information may be on the system, hand it to the security office before anyone copies evidence | Incident Commander |
Response loop
| # | Item | Owner |
|---|---|---|
| 1 | Give the CISA hunt or response team accounts, tool access, logs and a named escort | Logistics |
| 2 | Give logs and data to CISA and the FBI on request, and record each transfer | Intelligence/Investigations |
| 3 | Complete directive actions by the directive's deadline and report them to CISA | Operations |
| 4 | Update CISA when an impact rating, the vector or the scope changes | Liaison |
| 5 | Get the authorizing official's approval in T3 before containment on an HVA or mission system | Incident Commander |
| 6 | Notify Congress and the OIG within 7 days of a reasonable basis to conclude a major incident occurred, then update Congress as facts arrive | Liaison |
| 7 | For a breach, assess the risk of harm: sensitivity of the PII, likelihood of access and use, and type of breach | Legal advisor |
| 8 | Record the agency head's notification decision, and send notices with T16 | Legal advisor |
| 9 | Send the 30-day report to Congress for a breach that is a major incident | Legal advisor |
| 10 | Collect the FedRAMP provider's reports and tracking ID, and request records with T19 | Liaison |
Debrief
| # | Item | Owner |
|---|---|---|
| 1 | Send response and remediation results to CISA for review and validation, as EO 14028 section 6 provides | CISO |
| 2 | Send final updates to CISA, OMB and Congress | Liaison |
| 3 | Enter control failures as POA&M items, update the SSP, and ask the authorizing official whether the ATO stands | CISO |
| 4 | Feed breach lessons into the breach response plan | Legal advisor |
| 5 | Supply incident facts for the agency's annual FISMA report | Planning |
| 6 | Schedule incident records under GRS 3.2 item 020 or the agency schedule, and note any legal hold | Planning |
Sources: M-25-04; M-17-12; EO 14028 sections 6 to 8; M-26-14; CISA reporting page; CISA Cybersecurity Incident and Vulnerability Response Playbooks (November 2021); CISA threat hunting report to Congress, July 13, 2023, citing 44 U.S.C. 3553(b)(7).
Records
| Record | What changes |
|---|---|
| T1 Incident record | Add the CISA incident number, the time the top-level SOC identified the incident, and the major incident determination (yes, no, or not ruled out) with time and deciders. Add the FIPS 199 level, HVA yes or no, and any directive in force |
| T2 Triage brief | State functional impact, information impact and recoverability in CISA's terms, and whether CISA's incident playbook applies |
| T13 Law enforcement and insurer contact | Record the FBI field office and case number, the OIG contact, and CISA contacts |
| T16 Notice to affected individuals or customers | Use the M-17-12 content. Record the agency head's decision and the SAOP's review |
| T17 Regulator notification worksheet | One worksheet each for the CISA report, the major incident report to CISA and OMB, the 7-day congressional notice, the 30-day breach report, and each directive report |
| T19 Vendor evidence and preservation request | Cite the contract clause or the FedRAMP rules as the legal basis, and ask for the provider's own incident report |
| Sector records | The CISA report and its updates, congressional letters, directive status reports and POA&M items join the incident record. Under NARA GRS 3.2 item 020, incident handling records are destroyed 3 years after follow-up actions are complete, or kept longer for business use. As federal records they are open to FOIA requests; the FOIA office and counsel review any release |
Sources: NARA General Records Schedule 3.2 (Transmittal 33), item 020, checked October 2026; M-17-12.
Who you work with
| Body | What they do for you | How to reach them |
|---|---|---|
| CISA | Takes incident reports, hunts and responds on agency networks with or without advance notice under 44 U.S.C. 3553(b)(7), issues directives, leads asset response under PPD-41 | The reporting form linked from cisa.gov/report, or 888-282-0870, staffed 24 hours |
| OMB Office of the Federal Chief Information Officer | Receives major incident reports, consults on the determination | Direct contact, per M-25-04 |
| FBI | Leads threat response under PPD-41: investigation, attribution, charges. May ask for logs under M-26-14 | The local FBI field office |
| Office of Inspector General | Receives major incident notice. May investigate insider or fraud aspects and review the response | The agency's OIG |
| Congressional committees | Oversight of major incidents | Through legislative affairs |
| FedRAMP | Receives cloud provider incident reports, and can act on a provider's certification | fedramp.gov |
| NARA and ISOO | NARA sets records schedules. ISOO oversees classified information and CUI policy | Through the records officer and the security office |
Sources: PPD-41; 32 CFR 2002 (section 2002.16(a)(6) on CUI holders' reports of non-compliance to the disseminating agency); EO 14306 (June 6, 2025), which left EO 14028's incident provisions in place; FedRAMP notice 0014, June 16, 2026, which records BOD 26-04 as issued June 10, 2026, names its four factors, and gives the August 7, 2026 and December 7, 2026 dates; CISA's directives pages title BOD 22-01 and BOD 19-02 as revoked; Tenable, Wiley and Datadog describe the 3-day forensic triage tier and differ on its conditions; the directive page on cisa.gov would not open for the October and November 2026 checks; CISA's EINSTEIN and CDM pages; NIST SP 800-61r3 (April 2025), which replaced Rev. 2, and the SP 800-53 IR family (IR-4, IR-6, IR-8) as the agency control standard.
- The CISA clock starts when the top-level SOC, CSIRT or IT department identifies the incident. Report within the hour with what you know and update later.
- The 7-day congressional clock starts at a reasonable basis to conclude a major incident occurred. Record that moment and who judged it, because Congress and the OIG will ask.
- Runbooks that cite BOD 22-01 deadlines or M-21-31 EL levels are out of date. BOD 26-04 and M-26-14 replaced them in 2026.
- Under FedRAMP's 2026 rules a provider reports to FedRAMP and its agency customers. The agency makes its own CISA report.
- Classified information found on an unclassified system goes to the security office. Stop copying, imaging or forwarding it until that office directs.