FedRAMP Certification¶

Providers MUST identify a target FedRAMP Certification Profile and apply all relevant FedRAMP Practices to the cloud service offering.

Note: Information resources (including third-party information resources) MAY vary by security category as appropriate to the type of information handled by or impacted by the information resource.

Terms: Certification Profile, Cloud Service Offering, FedRAMP Practices, Handle, Information Resource, Security Category, Third-Party Information Resource

Providers seeking a Class B Certification MUST supply a complete FedRAMP Certification Package to FedRAMP for initial certification; the FedRAMP Certification Package MUST include at least the following information:

1. A Certification Package Overview
2. A Security Decision Record
3. A real or example Ongoing Certification Report following CCM-OCR-AVL (Report Availability)

Terms: Certification Package, FedRAMP Certification Report, Initial Certification, Ongoing Certification, Ongoing Certification Report (OCR), Security Decision Record (SDR)

Providers MUST supply machine-readable information in JSON documents that are valid against the corresponding JSON schema when a rule contains a FedRAMP JSON schema, UNLESS otherwise specified in the rule.

Note: FedRAMP JSON schemas are designed to be lightweight and flexible to establish a minimum set of structured information while allowing providers to improve on the format and structure of the information as needed to meet their needs and the needs of their customers.

Terms: Machine-Readable

Providers MUST maintain responsibility and accountability for the accuracy and completeness of all information in the FedRAMP Certification Package, especially when they engage a third party (such as an independent assessor, advisory service, or external tools) to supply information on their behalf.

Terms: Certification Package

Providers MUST NOT seek both FedRAMP Rev5 Program Certification and FedRAMP 20x Program Certification for the same cloud service offering; pick one type.

Note: This rule does not prevent a provider from seeking and maintaining a FedRAMP Rev5 Agency Certification and a FedRAMP 20x Program Certification for the same cloud service offering, however, doing so is strongly discouraged due to the increased complexity and risk of confusion for all parties.

Terms: Cloud Service Offering

Providers seeking a FedRAMP Class A Certification MUST have completed a certification or equivalent process, including an independent assessment if applicable, from one of the following alternative security frameworks within the past 12 months:

1. FedRAMP Rev5 (including FedRAMP Ready) at any historical Impact Level
2. SOC 2 Type II
3. GovRAMP at any Impact Level

Terms: Security Category

Providers seeking a FedRAMP Class A Certification MUST supply the following materials from their alternative security framework assessment to all necessary parties:

1. SOC 2 Type II: Complete report, bridge or gap letter (if applicable), verified audit engagement documentation, estimated schedule for upcoming report, supplemental compliance evidence (if applicable)
2. FedRAMP Ready: Readiness Assessment Report, Security Assessment Plan, and any other materials required by FedRAMP.
3. GovRAMP: Readiness Assessment Report, Security Assessment Plan, and any other materials required by GovRAMP.

Terms: All Necessary Parties, Verification

Providers seeking a Class A FedRAMP Certification MUST address all rules in this FedRAMP Class A Certification subset (FRC-CLA) AND the following additional FedRAMP Class Arules; the appropriate artifacts or information mapping for all rules MUST be supplied in the FedRAMP Certification Package.

1. FedRAMP Certification: FRC-CSO-PKG (FedRAMP Certification Package)
2. FedRAMP Certification: FRC-CSO-JSN (FedRAMP JSON Schemas)
3. FedRAMP Certification: FRC-CSO-POP (Pick One Program Certification Type)
4. Minimum Assessment Scope: MAS-CSO-IIR (Identify Information Resources)
5. Certification Data Sharing: CDS-CSO-PUB (Public Information)
6. Certification Data Sharing: CDS-CSO-UTC (Use Trust Centers)
7. Certification Data Sharing: CDS-UTC-AAD (Agency Access Denial)
8. Certification Data Sharing: CDS-CSO-AVR (Availability Reporting)
9. Addressing FedRAMP Communication: AFC-CSO-INB (Maintain a FedRAMP Security Inbox)
10. Addressing FedRAMP Communication: AFC-CSO-RCV (Receive Email Without Disruption)
11. Addressing FedRAMP Communication: AFC-CSO-CRA (Complete Required Actions)
12. Incident Evaluation and Communication: IEC-CSO-EFR (Evaluate FedRAMP Reportability)
13. Incident Evaluation and Communication: IEC-CSO-FIR (Final Incident Report)
14. Vulnerability Detection and Response: VDR-CSO-DET (Vulnerability Detection)
15. Collaborative Continuous Monitoring: CCM-OCR-AVL (Report Availability)
16. Collaborative Continuous Monitoring: CCM-OCR-NRD (Next Report Date)
17. Independent Verification and Validation: IVV-CSX-AIA (Annual Independent Assessments for 20x)
18. Independent Verification and Validation: IVV-CSF-AIA (Annual Independent Assessments for Rev5)
19. Key Security Indicators: KSI-CMT-LMC (Logging Changes)
20. Key Security Indicators: KSI-CNA-RNT (Restricting Network Traffic)
21. Key Security Indicators: KSI-CED-RAT (Reviewing All Training)
22. Key Security Indicators: KSI-IAM-AAM (Automating Account Management)
23. Key Security Indicators: KSI-IAM-APM (Adopting Passwordless Methods)
24. Key Security Indicators: KSI-INR-RIR (Reviewing Incident Response Procedures)
25. Key Security Indicators: KSI-SVC-SIN (Securing Information)

Notes:

• Some of these specific FedRAMP rules may not have similar counterparts in external frameworks and providers will need to implement new processes to follow these rules.
• In general, for each of these FedRAMP requirements, providers should include a sufficiently detailed summary that reviewers will not need to dig into the related security framework materials to understand the related decisions - just saying "see SOC 2 report" is not particularly helpful.
• Information about how the provider addresses the included Key Security Indicators are required for both Rev5 and 20x Class A Certifications.

Terms: Artifacts, Certification Data, Certification Package, Certification Type, FedRAMP Security Inbox, Final Incident Report (FIR), Incident, Information Resource, Initial Incident Report (IIR), Ongoing Certification Report (OCR), Trust Center, Validation, Verification, Vulnerability, Vulnerability Detection, Vulnerability Response

Providers seeking a Class A FedRAMP Certification SHOULD address the following additional recommended FedRAMP Class A rules (if applicable):

1. Certification Data Sharing: CDS-CSO-AVR (Availability Reporting)
2. Certification Package Overview: CPO-CSF-CPM (Certification Package Maintenance for Rev5)
3. Certification Package Overview: CPO-CSX-CPM (Certification Package Maintenance for 20x)
4. Incident Evaluation and Communication: IEC-CSO-IIR (Initial Incident Report)
5. Incident Evaluation and Communication: IEC-CSO-OIR (Ongoing Incident Reports)
6. Vulnerability Detection and Response: VDR-TFR-MVX (Persistent Machine Verification and Validation for 20x)
7. Vulnerability Detection and Response: VDR-TFR-PCD (Persistently Complete Detection)
8. Vulnerability Detection and Response: VDR-TFR-PDD (Persistent Drift Detection)
9. Vulnerability Detection and Response: VDR-TFR-PSD (Persistent Sample Detection)
10. Vulnerability Detection and Response: VDR-TFR-PVR (Mitigation and Remediation Expectations)
11. Vulnerability Evaluation and Reporting: VER-TFR-EVU (Evaluate Vulnerabilities Quickly)

Terms: Certification Data, Certification Package, Drift, Incident, Initial Incident Report (IIR), Ongoing Incident Report (OIR), Persistently, Validation, Verification, Vulnerability, Vulnerability Detection, Vulnerability Response

Providers seeking a Class A FedRAMP Certification MAY address the following additional optional FedRAMP Class A rules (if applicable):

1. Collaborative Continuous Monitoring: CCM-QTR-MTG (Quarterly Review Meeting)
2. Certification Data Sharing: CDS-CSO-PSM (Per-Service Certification Materials)
3. Cryptographic Module Use: CMU-CSO-UVM (Using Validated Cryptographic Modules)
4. FedRAMP Certification: FRC-APP-FIA (Fresh Independent Assessment)
5. Independent Verification and Validation: IVV-CSO-FIA (FedRAMP Independent Assessments)
6. Security Decision Record: SDR-CSX-KMT (Key Security Indicator Metrics)
7. Vulnerability Evaluation and Reporting: VER-TFR-IRI (Internet-Reachable Incidents)
8. Vulnerability Evaluation and Reporting: VER-TFR-MRH (Historical Activity)
9. Vulnerability Evaluation and Reporting: VER-TFR-NRI (Non-Internet-Reachable Incidents)

Terms: Certification Data, FedRAMP Independent Assessment, Incident, Quarterly Review, Security Decision Record (SDR), Validation, Verification, Vulnerability

Providers seeking a FedRAMP Class A Certification MAY have the FedRAMP Certification Package independently verified and validated by a FedRAMP Recognized assessor before submission to FedRAMP.

Terms: Certification Package, FedRAMP Recognized, Validation, Verification

Providers MUST be listed in the FedRAMP Marketplace before applying for FedRAMP Certification, including:

1. FedRAMP Marketplace: MKT-CSO-MLR (Marketplace Listing Requirements),
2. FedRAMP Marketplace: MKT-CSO-PML (Provider Marketplace Listing Requests)
3. FedRAMP Marketplace: MKT-IIP-AGU (Agency Use Cases)
4. FedRAMP Marketplace: MKT-IIP-DCP (Demonstrating Continuous Progress)

Providers MUST complete the FedRAMP Certification Application Form in full to request an initial assessment by FedRAMP.

Providers MUST supply a fresh initial FedRAMP Certification Package that shows the current status of the cloud service offering as verified and validated by the provider within the previous 7 days.

Terms: Certification Package, Cloud Service Offering, Validation, Verification

Terms: FedRAMP Independent Assessment, FedRAMP Recognized

Providers MUST NOT use a third party to apply for a FedRAMP Certification on their behalf; this includes independent assessment services.

Notes:

• FedRAMP previously allowed independent assessment services to submit applications on behalf of providers, but this caused confusion about who was responsible for the application and the information in it. Providers should apply directly to ensure clear accountability.
• Providers may use third parties to help them prepare their application and assessment materials for submission.

Providers MAY freshen a stale initial independent verification and validation assessment by having a FedRAMP Recognized independent assessment service review any changes between the original assessment and the current status of the cloud service offering in place of a full re-assessment, UNLESS the stale assessment is more than 9 months old.

Terms: Cloud Service Offering, FedRAMP Recognized, Validation, Verification

Terms: Persistently, Validation, Verification

Note: For initial FedRAMP Certification, providers will need to have mechanisms in place and agree to meet this requirement in the event the cloud service has not been operating with related metrics available for the required period prior to applying for initial certification.

Terms: Initial Certification, Persistently, Validation

Note: Different rules will be easy to automate for different providers, depending on the implementation, so FedRAMP generally leaves this implementation up to providers based on what makes the most sense for their own business and approach.

Terms: Persistently, Security Decision Record (SDR), Validation, Verification

Providers SHOULD apply ALL Key Security Indicators to ALL aspects of their cloud service offering that are within the FedRAMP Minimum Assessment Scope.

Terms: Cloud Service Offering