Skip to main content

FedRAMP 20x Class A: Which Incident Reports Are Required?

For Class A under the 2026 ruleset, prompt FedRAMP reportability evaluation and a Final Incident Report are mandatory. Initial and ongoing incident reports are SHOULD where applicable. Preserve the Class A timing tables, document how recommendations are handled, and follow recipient-specific channels and agency procedures.

Written by Boundera Team|November 19, 2026|6 min read

Main question

Which incident reporting tasks are mandatory for FedRAMP 20x Class A?

A Class A incident runbook needs separate decisions for reportability, the first notification, continuing updates, and closure. Under the FedRAMP Consolidated Rules for 2026, prompt reportability evaluation and the Final Incident Report are mandatory for Class A. Initial and ongoing incident reports are recommended with SHOULD, where applicable. That distinction belongs in the runbook before the next incident.

This guide explains the existing Class A rules for providers using the 2026 ruleset. It is an implementation guide, rather than an announcement of a policy change. The Class A certification rules explicitly identify which incident rules to address. FedRAMP Class A certification rules.

FRC-CLA-MFR includes Evaluate FedRAMP Reportability (IEC-CSO-EFR) and Final Incident Report (IEC-CSO-FIR) among the mandatory Class A rules. FRC-CLA-RFR lists Initial Incident Report (IEC-CSO-IIR) and Ongoing Incident Reports (IEC-CSO-OIR) among additional recommended rules, if applicable. The Class A versions of those two reporting rules use SHOULD. Class A related rules.

TaskClass A forceDecision to record
Evaluate FedRAMP reportabilityMUSTWhether federal customer data confidentiality or integrity is affected or likely to be affected, and why
Provide an Initial Incident ReportSHOULD, if applicableHow the team handles the recommendation and the first notification
Provide Ongoing Incident ReportsSHOULD, if applicableHow the team handles updates during incident response
Provide a Final Incident ReportMUSTWhen resolution and recovery are complete, and how final updates reach affected parties

SHOULD carries an expectation. FedRAMP's definition permits justified exceptions in particular circumstances only after the full implications are understood and weighed; parties MUST explain their decisions for handling SHOULD rules in security documentation. Record the reasoning for your reporting approach before relying on an exception. Official rule-force definitions.

Evaluate reportability promptly

IEC-CSO-EFR requires providers to promptly evaluate whether an incident affects, or is likely to affect, the confidentiality or integrity of federal customer data. Incidents meeting that test are FedRAMP Reportable Incidents and are reported under the applicable Incident Evaluation and Communication rules. FedRAMP defines promptly as acting without unnecessary delay. Class A reportability rule.

For implementation, give the evaluation an owner and record the affected data, known facts, uncertainties, decision time, and rationale. The rule's artifact guidance calls for an incident log showing an evaluation and the reason for the determination; examples may come from real or simulated incidents.

Keep the decision tied to the stated confidentiality-or-integrity test. As operating guidance, reassess the decision when new facts change what the team knows about federal customer data.

Keep each reporting timeframe attached to its report

The Class A tables give these timeframes for Potential Agency Impact N-ratings (PAIN). Preserve the report's force when copying a timeframe into an internal procedure. Class A incident reporting tables.

ReportPAIN 1–2PAIN 3–5Class A force
Initial Incident Report1 business day6 hoursSHOULD
Ongoing Incident Report1 business day1 business daySHOULD
Final Incident Report3 business days3 business daysMUST

The initial-report statement refers to notification after identifying a FedRAMP Reportable Incident. The ongoing-report statement concerns new information during response, including updates or the lack of updates to previously reported information. The final-report statement requires notification once the incident is resolved and recovery is complete, with final updates to previously reported information.

In your procedure, record incident start, detection, completed reportability evaluation, and recovery completion as separate milestones. Tie the due-time calculation to the applicable report statement, timing table, and agency procedure. This is implementation advice: the table alone does not establish one universal clock start for every report or recipient.

Prepare the report while facts are developing

For the Class A Initial Incident Report, IEC-CSO-IIR recommends providing the available information or current relevant status for the listed items: coordinator contact details; the provider's tracking identifier; incident description and timeline; historical and current PAIN estimates with an explanation where applicable; functional impact and affected federal customer data types; estimated recovery plans and milestones; and likely affected agencies. Initial Incident Report.

IEC-CSO-OIR adds observed activity, indicators of compromise, relevant CVE identifiers where applicable, root cause, and response and recovery activities as information becomes available. It includes updates or lack of updates to earlier information. Ongoing Incident Reports.

A practical template can distinguish confirmed facts, estimates, unknowns, and the next person responsible for checking each item. That makes it easier to update an earlier report without silently changing the incident history.

Route notifications by recipient

The structured notification entries for the initial, ongoing, and final reports identify FedRAMP email at fedramp_security@fedramp.gov and agency customer reporting through agency-specific procedures. They also list an optional update for all necessary parties through the provider's trust center or USDA Connect. Official structured incident rules.

Keep a recipient list with the channel and applicable agency instructions beside each reporting task. Check those instructions when planning timing and delivery. Preserve the individual delivery records so the team can establish what reached each recipient.

FedRAMP's definition of responsibly cautions against broadcasting details that could assist adversaries or facilitate further compromise. Use that guidance when deciding what each recipient receives. FedRAMP definitions.

Make closure a reporting task

For Class A, IEC-CSO-FIR requires the Final Incident Report once the incident is resolved and recovery is complete. Its PAIN 1–5 table gives three business days. Include final updates to previously reported information. Final Incident Report.

For implementation, use a short closure record with these fields:

  1. Reportability decision, rationale, and owner.
  2. Reporting task, Class A force, applicable timing table, and documented handling of recommendations.
  3. Recipient, channel, agency instructions, and delivery evidence.
  4. Resolution and recovery milestones, final report owner, and completion evidence.

Keep incident reporting distinct from the Ongoing Certification Report. FedRAMP defines an Ongoing Incident Report as a recurring report about an ongoing incident under the incident rules; an Ongoing Certification Report is a regular agency-customer report under Collaborative Continuous Monitoring. Official report definitions.

A useful exercise is to run a simulated incident through the procedure, then check whether another responder can reconstruct the evaluation, reporting decisions, delivery history, and final closure from the saved record.

Frequently asked questions

Are initial and ongoing incident reports mandatory for Class A?

The Class A versions use SHOULD, and FRC-CLA-RFR recommends addressing them if applicable. FedRAMP requires documented decisions about handling SHOULD rules and careful consideration of any exception.

When is the Class A Final Incident Report required?

IEC-CSO-FIR requires it once the incident is resolved and recovery is complete, including final updates to previously reported information. The Class A PAIN 1–5 table gives three business days.

What are the Class A initial and ongoing reporting timeframes?

The initial-report table gives six hours for PAIN 3–5 and one business day for PAIN 1–2. The ongoing-report table gives one business day for PAIN 1–5. Both Class A reports use SHOULD; apply each report statement and recipient procedure when determining timing.

Is an Ongoing Incident Report the same as an Ongoing Certification Report?

No. FedRAMP defines the Ongoing Incident Report under incident evaluation and communication, while the Ongoing Certification Report is a regular report under Collaborative Continuous Monitoring.

Next step

If you want to turn this guidance into an execution plan, the product side handles control mapping, SSP drafting, and evidence collection.

Related articles