Skip to content
Log inRegister

CISA's New Incident Form Speaks ATT&CK: Get Your Reporting Ready Before CIRCIA

Dr. Abeer Alshammari · Published 11/16/2026

IntermediateProfessionalsCISOsExecutives

On Monday 9 November 2026, CISA released a revised version of its cyber incident reporting form on the Incident Reporting Portal. On the surface it is a modest change: fewer duplicate questions, more specific ones. Underneath, it signals something more important for every security and GRC team. The form now asks reporters to describe observed adversary activity using MITRE ATT&CK, the widely used catalogue of attacker tactics and techniques. Incident reporting is moving from free-text narrative to structured, comparable data.

What actually changed

According to reporting by Nextgov/FCW, MeriTalk and Help Net Security, the updated form adds questions on whether an incident involved malware, social engineering, hacking techniques or an insider threat, and it uses ATT&CK terminology for describing what the attacker did. CISA says the aim is to link incidents that look unrelated in isolation and to spot emerging campaigns sooner. As CISA's acting executive assistant director for cybersecurity, Chris Butera, put it, "one organization's detection is another's protection."

A few practical details matter. Reports can be submitted without signing in, but signing in through Login.gov with a work email lets you save drafts, track submissions and follow up. CISA's paperwork notice estimates about 30 minutes to complete a response. Malware samples go through a separate malware analysis form, linked using the CISA incident ID after the main report is filed. Email reporting to CISA remains possible, although the online form is preferred.

Equally important is what did not change. The update does not create new legal obligations and does not implement the Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA). Federal civilian agencies continue to report under their existing requirements; everyone else reports voluntarily, for now.

Why the timing matters: CIRCIA is at the White House

CISA submitted the CIRCIA final rule to the Office of Information and Regulatory Affairs on 1 October 2026, after missing both the October 2025 statutory deadline and its own September 2026 target. As of 11 November it was still under review and had not been published in the Federal Register. Under the 2024 proposed rule, covered entities would report substantial cyber incidents within 72 hours of reasonably believing one occurred, and ransom payments within 24 hours. The final text, scope and effective date are not yet public, so no one should plan around exact details.

What can be planned around is direction. A voluntary form that already speaks ATT&CK is a strong hint about the kind of structured detail regulators will expect once reporting becomes mandatory. Organizations that can only produce a narrative timeline under a 72-hour clock will struggle; those that already record technique-level observations will not.

The governance gap this exposes

In many organizations I review, ATT&CK lives inside the SOC: in detection rules, threat hunting notes and vendor dashboards. It rarely reaches the incident record that legal, compliance and executives rely on. The result is two versions of the same incident: a technical one that analysts understand and a business one that regulators receive. When a report has to be filed quickly, someone translates between them under pressure, and accuracy suffers.

The fix is not a new tool. It is a decision about what the authoritative incident record contains and who owns it.

Five steps to take before CIRCIA lands

1. Add ATT&CK fields to your incident record. Include tactic, technique and a confidence level for each observation. Allow "unknown" as a valid answer; reporting a guess as fact is worse than reporting uncertainty.

2. Build one intake record for every notice. The same facts feed CISA, sector regulators, SEC disclosure assessments, privacy notifications and insurers. Capture them once, with timestamps, and generate each notice from the same source so the stories never diverge.

3. Define the "reasonable belief" moment. A 72-hour clock needs a clear start. Decide in advance who declares that a substantial incident is reasonably believed to have occurred, and log when that decision is made.

4. Pre-authorize the reporter. Name who submits reports, set up Login.gov access with work accounts, and decide what can be shared with CISA without fresh legal review. Rehearse a submission in a tabletop exercise using the actual form fields.

5. Separate the ransom-payment workflow. If payments are ever considered, the proposed 24-hour window runs from payment, not discovery. Treasury, legal and the incident lead need a pre-agreed path.

The board-level question

Boards do not need to understand ATT&CK technique identifiers. They do need one answer: if we had to report a significant incident to a regulator within 72 hours tomorrow, would the facts be ready, consistent and owned? CISA's revised form is a low-cost way to test that today, voluntarily, before the obligation arrives.

Disclaimer: This article is for general information and does not constitute legal advice. It is based on public reporting by Nextgov/FCW, MeriTalk and Help Net Security published 9 to 11 November 2026; CISA's own announcement page could not be opened directly when this was written. CIRCIA final rule requirements were not public at the time of writing and may differ from the proposed rule.

Try it yourself

An interactive CyberAbeer experience for this topic is in development.

Coming soon
Back to insights