IEC-CSO General Provider Responsibilities

Providers MUST promptly evaluate incidents to determine if they affect confidentiality or integrity of federal customer data or are likely to affect confidentiality or integrity of federal customer data; such incidents are FedRAMP Reportable Incidents and must be reported following the FedRAMP Incident Evaluation and Communication rules.

Artifacts

• An incident log showing an example of one or more incidents being evaluated including the reason for the determination. The log can be from real incidents, simulated incidents, or a combination of sources.

NIST SP 800-53 Rev. 5 controls: AU-5(2), IR-4(11)

Defined terms: FedRAMP Reportable Incident, Federal Customer Data, Incident, Likely, Promptly

Providers MUST treat FedRAMP Reportable Incidents as if they have a Potential Agency Impact N-rating (PAIN) of 5 UNLESS they promptly estimate the PAIN rating following the rule in IEC-CSO-EFI (Estimate Federal Impact).

Related rules: IEC-CSO-EFI

Defined terms: FedRAMP Reportable Incident, Incident, Potential Agency Impact, Promptly

Notification

• FedRAMP via email – fedramp_security@fedramp.gov
• Agency Customers via varies – Follow agency-specific incident reporting procedures: varies by agency
• All Necessary Parties via update – Provider's Trust Center or USDA Connect: trust center

Class A

Providers with Class A Certifications SHOULD responsibly notify all affected parties after identifying FedRAMP Reportable Incidents by providing an Initial Incident Report with as much of the following information that is available at the time of reporting and/or the current relevant status for each item:

• Contact information for the federal incident response coordinator
• Provider's internally assigned tracking identifier
• Description of the incident
• Timeline of the incident, including start time, time and source of detection, time of completed FedRAMP Reportable Incident evaluation, and other major incident milestones determined by the provider
• Historically and currently estimated Potential Agency Impact N-rating (PAIN) of the incident, including an explanation of the evaluation following the requirements in IEC-CSO-EFI (Estimate Federal Impact) (if applicable)
• Functional impact to federal agency customers (include impact to confidentiality and/or integrity and the impacted federal customer data types)
• Estimated recovery plan, milestones, and timelines
• List of likely affected customer agencies

Timeframes by impact level

Artifacts

• An Initial Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class B

Providers with Class B Certifications MUST responsibly notify all affected parties after identifying FedRAMP Reportable Incidents by providing an Initial Incident Report with as much of the following information that is available at the time of reporting and/or the current relevant status for each item:

• Contact information for the federal incident response coordinator.
• Provider's internally assigned tracking identifier
• Description of the incident
• Timeline of the incident, including start time, time and source of detection, time of completed FedRAMP Reportable Incident evaluation, and other major incident milestones determined by the provider
• Historically and currently estimated Potential Agency Impact N-rating (PAIN) of the incident, including an explanation of the evaluation following the requirements in IEC-CSO-EFI (Estimate Federal Impact) (if applicable)
• Functional impact to federal agency customers (include impact to confidentiality and/or integrity and the impacted federal customer data types)
• Estimated recovery plan, milestones, and timelines
• List of likely affected customer agencies

Timeframes by impact level

Artifacts

• An Initial Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class C

Providers with Class C Certifications MUST responsibly notify all affected parties after identifying FedRAMP Reportable Incidents by providing an Initial Incident Report with as much of the following information that is available at the time of reporting and/or the current relevant status for each item:

• Contact information for the federal incident response coordinator.
• Provider's internally assigned tracking identifier
• Description of the incident
• Timeline of the incident, including start time, time and source of detection, time of completed FedRAMP Reportable Incident evaluation, and other major incident milestones determined by the provider
• Historically and currently estimated Potential Agency Impact N-rating (PAIN) of the incident, including an explanation of the evaluation following the requirements in IEC-CSO-EFI (Estimate Federal Impact) (if applicable)
• Functional impact to federal agency customers (include impact to confidentiality and/or integrity and the impacted federal customer data types)
• Estimated recovery plan, milestones, and timelines
• List of likely affected customer agencies

Timeframes by impact level

Artifacts

• An Initial Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class D

Providers with Class D Certifications MUST responsibly notify all affected parties after identifying FedRAMP Reportable Incidents by providing an Initial Incident Report with as much of the following information that is available at the time of reporting and/or the current relevant status for each item:

• Contact information for the federal incident response coordinator.
• Provider's internally assigned tracking identifier
• Description of the incident
• Timeline of the incident, including start time, time and source of detection, time of completed FedRAMP Reportable Incident evaluation, and other major incident milestones determined by the provider
• Historically and currently estimated Potential Agency Impact N-rating (PAIN) of the incident, including an explanation of the evaluation following the requirements in IEC-CSO-EFI (Estimate Federal Impact) (if applicable)
• Functional impact to federal agency customers (include impact to confidentiality and/or integrity and the impacted federal customer data types)
• Estimated recovery plan, milestones, and timelines
• List of likely affected customer agencies

Timeframes by impact level

Artifacts

• An Initial Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Schema: FedRAMP Incident Report (IEC-CSO-IIR / IEC-CSO-OIR / IEC-CSO-FIR)

Related rules: IEC-CSO-EFI

NIST SP 800-53 Rev. 5 controls: AU-5(2), IR-5

Defined terms: All Affected Parties, FedRAMP Reportable Incident, Incident, Initial Incident Report (IIR), Responsibly

Notification

• FedRAMP via email – fedramp_security@fedramp.gov
• Agency Customers via varies – Follow agency-specific incident reporting procedures: varies by agency
• All Necessary Parties via update – Provider's Trust Center or USDA Connect: trust center

Class A

Providers with Class A Certifications SHOULD responsibly notify all affected parties of ongoing activity as new information becomes available during incident response for FedRAMP Reportable Incidents, including updates (or lack of updates) to all previously reported information and as much of the following additional information that is available and/or the current relevant status for each item:

• Observed incident activity
• Indicators of compromise
• Related Common Vulnerabilities and Exposures (CVE) identifier (if applicable)
• Root cause
• Response and recovery activities

Timeframes by impact level

Artifacts

• An Ongoing Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class B

Providers with Class B Certifications MUST responsibly notify all affected parties of ongoing activity as new information becomes available during incident response for FedRAMP Reportable Incidents, including updates (or lack of updates) to all previously reported information and as much of the following additional information that is available and/or the current relevant status for each item:

• Observed incident activity
• Indicators of compromise
• Related Common Vulnerabilities and Exposures (CVE) identifier, if applicable
• Root cause
• Response and recovery activities

Timeframes by impact level

Artifacts

• An Ongoing Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class C

Providers with Class C Certifications MUST responsibly notify all affected parties of ongoing activity as new information becomes available during incident response for FedRAMP Reportable Incidents, including updates (or lack of updates) to all previously reported information and as much of the following additional information that is available and/or the current relevant status for each item:

• Observed incident activity
• Indicators of compromise
• Related Common Vulnerabilities and Exposures (CVE) identifier, if applicable
• Root cause
• Response and recovery activities

Timeframes by impact level

Artifacts

• An Ongoing Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class D

Providers with Class D Certifications MUST responsibly notify all affected parties of ongoing activity as new information becomes available during incident response for FedRAMP Reportable Incidents, including updates (or lack of updates) to all previously reported information and as much of the following additional information that is available and/or the current relevant status for each item:

• Observed incident activity
• Indicators of compromise
• Related Common Vulnerabilities and Exposures (CVE) identifier, if applicable
• Root cause
• Response and recovery activities

Timeframes by impact level

Artifacts

• An Ongoing Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Schema: FedRAMP Incident Report (IEC-CSO-IIR / IEC-CSO-OIR / IEC-CSO-FIR)

NIST SP 800-53 Rev. 5 controls: IR-5

Defined terms: All Affected Parties, FedRAMP Reportable Incident, Incident, Responsibly, Vulnerability Response

Notification

• FedRAMP via email – fedramp_security@fedramp.gov
• Agency Customers via varies – Follow agency-specific incident reporting procedures: varies by agency
• All Necessary Parties via update – Provider's Trust Center or USDA Connect: trust center

Class A

Providers with Class A Certifications MUST responsibly notify all affected parties by providing a Final Incident Report once the incident has been resolved and recovery is complete, including final updates to all previously reported information.

Timeframes by impact level

Artifacts

• An Final Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class B

Providers with Class B Certifications MUST responsibly notify all affected parties by providing a Final Incident Report once the incident has been resolved and recovery is complete, including final updates to all previously reported information.

Timeframes by impact level

Artifacts

• An Final Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class C

Providers with Class C Certifications MUST responsibly notify all affected parties by providing a Final Incident Report once the incident has been resolved and recovery is complete, including final updates to all previously reported information.

Timeframes by impact level

Artifacts

• An Final Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Class D

Providers with Class D Certifications MUST responsibly notify all affected parties by providing a Final Incident Report once the incident has been resolved and recovery is complete, including final updates to all previously reported information.

Timeframes by impact level

Artifacts

• An Final Incident Report for one or more incidents. The report can be from real incidents, simulated incidents, or a combination of sources.

Schema: FedRAMP Incident Report (IEC-CSO-IIR / IEC-CSO-OIR / IEC-CSO-FIR)

NIST SP 800-53 Rev. 5 controls: IR-5

Defined terms: All Affected Parties, Final Incident Report (FIR), Incident, Responsibly

Providers SHOULD promptly estimate the likely adverse impact of an incident on agency customers to assign a Potential Agency Impact N-rating; this step is called Incident Rating.

• N1 for a likely minimal customer effect on 1 or more agencies.
• N2 for a likely narrow customer effect on 1 or more agencies.
• N3 for a likely disruptive customer effect on 1 agency.
• N4 for a likely debilitating customer effect on 1 agency or a likely disruptive customer effect on more than 1 agency.
• N5 for a likely debilitating customer effect on more than 1 agency.

Note

All incidents must be assigned a default PAIN-5 as required by IEC-CSO-DPR (Default PAIN Rating) if this step is not completed.

Artifacts

• An incident log showing an example of one or more incidents being evaluated including the reason for the determination. The log can be from real incidents, simulated incidents, or a combination of sources.

Schema: FedRAMP Incident Report (IEC-CSO-IIR / IEC-CSO-OIR / IEC-CSO-FIR)

Related rules: IEC-CSO-DPR

Defined terms: Debilitating Customer Effect, Disruptive Customer Effect, Incident, Likely, Minimal Customer Effect, Narrow Customer Effect, Potential Agency Impact, Promptly

Providers SHOULD use automation to minimize human intervention in the process of reporting FedRAMP Reportable Incidents to all affected parties.

Warning: Modern cloud services should not be reporting incidents by hand-crafting emails!

Defined terms: All Affected Parties, FedRAMP Reportable Incident, Incident