From the official source
FedRAMP’s historical Incident Communications Procedures require cloud service providers to “report any incident (suspected or confirmed) that results in the actual or potential loss of confidentiality, integrity, or availability of the cloud service, including the impact to federal customer data that it stores, processes, or transmits.”
These procedures have not been consistently followed or enforced because they are broad and often unclear. In practice, most cloud service providers with FedRAMP Certification rarely notify FedRAMP of an incident. FedRAMP believes that a clear set of reporting requirements must be established using a modern rules-based format to ensure cloud service providers understand and can implement incident reporting requirements to meet their ongoing FedRAMP certification requirements after initial certification. These rules should focus effort on reporting meaningful incidents that an agency customer would not otherwise be aware of and align with the potential adverse impact to agency operations.
This RFC proposes updates to the Incident Communications Procedures as follows:
For members of the public that have not followed recent developments in the FedRAMP modernization process, Public Notice NTC-0004 explains FedRAMP Certification and the related classes.
In addition to general feedback, FedRAMP would like to understand how we can effectively align these requirements with the existing reporting and informational fields that cloud service providers are creating during typical commercial incident response.
The final version of this set of rules will be included in the FedRAMP Consolidated Rules for 2026 by the end of June 2026 after incorporating feedback from public comment. It will apply to both Rev5 and 20x type FedRAMP Certifications (replacing the current Incident Communications Procedures for 20x).
The capitalized key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this documentation are to be interpreted as described in IETF RFC 2119.
This document exists within the full context of FedRAMP documentation , including FedRAMP Definitions . It is not intended to be a standalone document and often references terminology or requirements that are explained elsewhere. Members of the public that haven’t followed recent developments in the FedRAMP modernization process may need to review other materials for context.