Addressing FedRAMP communication
AFC-CSO-INBfailMaintain a FedRAMP Security Inbox. Providers MUST establish and maintain an email address to receive messages from FedRAMP; this inbox is a FedRAMP Security Inbox (FSI).AFC-CSO-NOCfailNotification of Changes. Providers MUST immediately notify FedRAMP of any changes to the email address for their FedRAMP Security Inbox.AFC-CSO-TFGfailTrust @fedramp.gov and @gsa.gov. Providers MUST treat any email originating from an @fedramp.gov or @gsa.gov email address as if it was sent from FedRAMP by default; if such a message is confirmed to originate from someone other than FedRAMP then the FedRAMP Security Inbox rules no longer apply.AFC-CSO-RCVfailReceive Email Without Disruption. Providers MUST receive and react to email messages from FedRAMP without disruption and without requiring additional actions from FedRAMP.AFC-CSO-CRAfailComplete Required Actions. Providers MUST complete the required actions in Emergency or Emergency Test designated messages sent by FedRAMP within the timeframe included in the message.AFC-CSO-EMRfailEmergency Message Routing. Providers MUST route Emergency designated messages sent by FedRAMP to a senior security official for their awareness.AFC-CSO-IMAfailImportant Message Actions. Providers SHOULD complete the required actions in Important designated messages sent by FedRAMP within the timeframe specified in the message.AFC-CSO-ACKfailAcknowledge Receipt. Providers SHOULD promptly and automatically acknowledge the receipt of messages received from FedRAMP in their FedRAMP Security Inbox.
Collaborative continuous monitoring
CCM-OCR-AVLfailReport Availability. Providers MUST supply an Ongoing Certification Report to all necessary parties every 3 months, covering the entire period since the previous summary, in a consistent format that is human readable; this report MUST include high-level summaries of at least the following information (if applicable):CCM-OCR-NRDfailNext Report Date. Providers MUST supply the target date for their next Ongoing Certification Report with other public FedRAMP Certification Data.CCM-OCR-FBMfailFeedback Mechanism. Providers MUST supply an asynchronous mechanism for all necessary parties to provide feedback or ask questions about each Ongoing Certification Report.CCM-OCR-AFSfailAnonymized Feedback Summary. Providers MUST supply an anonymized and desensitized summary of the feedback, questions, and answers about each Ongoing Certification Report as an addendum to the Ongoing Certification Report OR in the next Ongoing Certification Report.CCM-OCR-LSIfailLimit Sensitive Information. Providers MUST NOT irresponsibly disclose sensitive information in an Ongoing Certification Report that would likely have an adverse effect on the cloud service offering.CCM-OCR-SORfailSpread Out Reports. Providers SHOULD establish a regular 3 month cycle for Ongoing Certification Reports that is spread out from the beginning, middle, or end of each quarter.CCM-OCR-RPSfailResponsible Public Certification Report Sharing. Providers MAY responsibly supply some or all of the information an Ongoing Certification Report to the public or other parties if the provider determines doing so will NOT likely have an adverse effect on the cloud service offering.CCM-QTR-MTGfailQuarterly Review Meeting. Providers with Class A Certifications MAY host a synchronous Quarterly Review every 3 months, open to all necessary parties, to review aspects of the most recent Ongoing Certification Reports that the provider determines are of the most relevance to agencies.CCM-QTR-REGfailMeeting Registration Info. Providers MUST supply either a registration link or a downloadable calendar file with meeting information for Quarterly Reviews to all necessary parties.CCM-QTR-NRDfailNext Review Date. Providers MUST publicly supply the target date for their next Quarterly Review with other public FedRAMP Certification Data.CCM-QTR-NIDfailNo Irresponsible Disclosure. Providers MUST NOT irresponsibly disclose sensitive information in a Quarterly Review that would likely have an adverse effect on the cloud service offering.CCM-QTR-SARfailSchedule Around Reports. Providers SHOULD regularly schedule Quarterly Reviews to occur at least 3 business days after releasing an Ongoing Certification Report AND within 10 business days of such release.CCM-QTR-ACTfailAdditional Content. Providers SHOULD supply additional information in Quarterly Reviews that the provider determines is of interest, use, or otherwise relevant to agencies.CCM-QTR-RTRfailRecord/Transcribe Reviews. Providers SHOULD record or transcribe Quarterly Reviews and supply them to all necessary parties.CCM-QTR-RTPfailRestrict Third Parties. Providers SHOULD NOT invite third parties to attend Quarterly Reviews intended for agencies unless they have specific relevance.CCM-QTR-SRRfailShare Recordings Responsibly. Providers MAY responsibly supply recordings or transcriptions of Quarterly Reviews to the public or other parties ONLY if the provider removes all agency information (comments, questions, names, etc.) AND determines doing so will NOT likely have an adverse effect on the cloud service offering.CCM-QTR-SCRfailShare Content Responsibly. Providers MAY responsibly supply content prepared for a Quarterly Review to the public or other parties if the provider determines doing so will NOT likely have an adverse effect on the cloud service offering.
Certification data sharing
CDS-CSO-PUBpartialPublic Information. Providers MUST publicly share up-to-date information about the cloud service offering in both human-readable and JSON formats, including at least the following information that is available and applicable:CDS-CSO-SVCfailPublic Service List. Providers MUST publicly share a detailed list of specific services and their security categories that are included in the cloud service offering using clear feature or service names that align with standard public marketing materials; this list MUST be complete enough for a potential customer to determine which services are and are not included in the FedRAMP Minimum Assessment Scope without requesting access to underlying FedRAMP Certification Data.CDS-CSO-FIDfailAlways Include FedRAMP ID. Providers MUST always include the FedRAMP ID of the related cloud service offering in all FedRAMP Certification Data once assigned, including all reports, notifications, and other communication that results from FedRAMP rules.CDS-CSO-FRCfailFedRAMP Certification Reports. Providers MUST include FedRAMP Certification Reports with their FedRAMP Certification Data without inappropriate modifications, and make such reports available within 2 weeks of receiving the materials from FedRAMP.CDS-CSO-AVRfailAvailability Reporting. Providers with Class A Certifications SHOULD maintain a web service, available to all necessary parties, that indicates current and historical availability of core services within the cloud service offering over at least the past 30 days, including availability incidents, in both human-readable and machine-readable formats; this service SHOULD be available even if the primary cloud service offering is unavailable.CDS-CSO-UTCfailUse Trust Centers. Providers MUST use a FedRAMP-compatible trust center to store and share FedRAMP Certification Data with all necessary parties.CDS-CSO-CBFpassConsistency Between Formats. Providers MUST use automation to ensure information remains consistent between human-readable and machine-readable formats when FedRAMP Certification Data is provided in both formats.CDS-CSO-RISfailResponsible Information Sharing. Providers MUST provide sufficient information in FedRAMP Certification Data to support agency authorization decisions but SHOULD NOT include sensitive information that would likely enable a threat actor to gain unauthorized access, cause harm, disrupt operations, or otherwise have a negative adverse impact on the cloud service offering.CDS-CSO-IRPfailInclude Relevant Policies. Providers MUST supply all relevant policies and procedures in the FedRAMP Certification Data, including a human-readable and machine-readable reference that explains at least the following about each included policy and procedure:CDS-CSO-HADfailHistorical FedRAMP Certification Data. Providers MUST supply snapshots of FedRAMP Certification Data aligned to Ongoing Certification Reports to all necessary parties; these snapshots MUST be available for the duration of FedRAMP Certification.CDS-CSO-PSMfailPer-Service Certification Materials. Providers with Class A Certifications MAY supply per-service FedRAMP Certification materials.CDS-CSO-RPSfailResponsible Public Package Sharing. Providers MAY responsibly share some or all of the information in a FedRAMP Certification Package publicly or with other parties if the provider determines doing so will NOT likely have an adverse effect on the cloud service offering.CDS-TRC-USHfailUninterrupted Sharing. Trust centers MUST share FedRAMP Certification Data with all necessary parties without interruption.CDS-TRC-PACpassProgrammatic Access. Trust centers MUST provide documented programmatic access to all FedRAMP Certification Data, including programmatic access to human-readable materials.CDS-TRC-AAIpassAgency Access Inventory. Trust centers MUST maintain an inventory and history of federal agency users or systems with access to FedRAMP Certification Data and MUST make this information available to FedRAMP upon request.CDS-TRC-ACLfailAccess Logging. Trust centers MUST log access to FedRAMP Certification Data and store summaries of access for at least six months; such information, as it pertains to specific parties, SHOULD be made available upon request by those parties.CDS-TRC-HMRfailHuman and Machine-Readable Certification Data. Trust centers SHOULD make FedRAMP Certification Data available to view and download in both human-readable and machine-readable formats.CDS-TRC-SSMfailSelf-Service Access Management. Trust centers SHOULD include features that encourage all necessary parties to provision and manage access to FedRAMP Certification Data for their users and services directly.CDS-UTC-AADfailAgency Access Denial. Providers MUST notify FedRAMP within 5 business days of denying an agency access request for FedRAMP Certification Data.CDS-UTC-AGAfailAgency Access. Providers SHOULD supply access to the FedRAMP Certification Package with agencies upon request.
Cryptographic module use
CMU-CSO-CMDfailCryptographic Module Documentation. Providers MUST document the cryptographic modules used in each service (or groups of services that use the same modules) where cryptographic services are used to protect federal customer data, including whether these modules are validated under the NIST Cryptographic Module Validation Program or are update streams of such modules.CMU-CSO-UVMfailUsing Validated Cryptographic Modules. Providers with Class A Certifications MAY use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when using cryptographic services to protect federal customer data.CMU-CSO-CATfailConfiguration of Agency Tenants. Providers SHOULD configure agency tenants by default to use cryptographic services that use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when such modules are available.
Certification package overview
CPO-CSO-OVRfailOverview of the Cloud Service Offering. Providers MUST supply a Certification Package Overview within their FedRAMP Certification Package, in both human-readable and JSON formats, that includes at least all of the information required by the following rules:CPO-CSO-MTDfailCertification Package Overview Metadata. Providers MUST also include the following basic metadata in their Certification Package Overview:CPO-CSO-OSAfailOverall Summary of Assessment in Certification Package. Providers seeking Class A Certification MAY also include an overall summary of their FedRAMP independent assessment in their Certification Package Overview.CPO-CSX-CPMfailCertification Package Maintenance for 20x. Providers with 20x Class A Certifications SHOULD persistently maintain their FedRAMP Certification Package to ensure it is up to date and complete at least once every 3 months.
FedRAMP certification
FRC-CSO-FCPfailFedRAMP Certification Profile. Providers MUST identify a target FedRAMP Certification Profile and apply all relevant FedRAMP Practices to the cloud service offering.FRC-CSO-PKGfailFedRAMP Certification Package. Providers seeking a Certification MUST supply a complete FedRAMP Certification Package to FedRAMP for initial certification; the FedRAMP Certification Package MUST include at least the following information:FRC-CSO-JSNpartialFedRAMP JSON Schemas. 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; public JSON data MUST be supplied in a manner compatible with modern web frameworks, including:FRC-CSO-MRAfailMaintain Responsibility and Accountability. 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.FRC-CSO-POPpassPick One Program Certification Type. Providers MUST NOT seek both FedRAMP Rev5 Program Certification and FedRAMP 20x Program Certification for the same cloud service offering; pick one type.FRC-CLA-ASFfailApproved Alternative Security Frameworks. 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:FRC-CLA-EAMfailExternal Assessment Materials. Providers seeking a FedRAMP Class A Certification MUST supply the following materials from their alternative security framework assessment to all necessary parties:FRC-CLA-MFRfailMandatory FedRAMP Rules for Class A. 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 A rules; the appropriate artifacts or information mapping for all rules MUST be supplied in the FedRAMP Certification Package.FRC-CLA-RFRfailRecommended FedRAMP Rules for Class A. Providers seeking a Class A FedRAMP Certification SHOULD address the following additional recommended FedRAMP Class A rules (if applicable):FRC-CLA-OFRfailAddress Optional FedRAMP Rules for Class A. Providers seeking a Class A FedRAMP Certification MAY address the following additional optional FedRAMP Class A rules (if applicable):FRC-CLA-IVVfailOptional Independent Verification and Validation. 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.FRC-APP-MLFfailMarketplace Listing First. Providers MUST be listed in the FedRAMP Marketplace before applying for FedRAMP Certification, including:FRC-APP-AFCfailApplying for FedRAMP Certification. Providers MUST complete the FedRAMP Certification Application Form in full to request an initial assessment by FedRAMP.FRC-APP-FCPfailFresh FedRAMP Certification Package. 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.FRC-APP-FIAfailFresh Independent Assessment. Providers seeking Class A Certification MAY supply a fresh initial FedRAMP independent assessment that was completed by a FedRAMP Recognized independent assessment service within the previous 3 months.FRC-APP-NTPpassNo Third-Party Applicants. Providers MUST NOT use a third party to apply for a FedRAMP Certification on their behalf; this includes independent assessment services.FRC-APP-USAfailUpdating Stale Assessments. 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.FRC-APS-ATOfailAgency Authorization to Operate. Providers seeking a FedRAMP Rev5 Agency Certification MUST have completed the Authorization to Operate (ATO) process with their agency sponsor for the cloud service offering, concluding with a formal signed ATO letter that the agency has sent over official government channels to FedRAMP.FRC-CCL-UCCfailUpgrading Certification Class. Providers MUST apply for a new FedRAMP Certification to upgrade their Certification Class; all applicable requirements MUST be met in advance.FRC-CCL-DCCfailDowngrading Certification Class. Providers MUST apply for a new FedRAMP Certification to downgrade their Certification Class.FRC-CCL-DNPfailDowngrade Notification Period. Providers SHOULD notify all necessary parties at least 120 days in advance of an intended downgrade or cancellation of FedRAMP Certification.FRC-CSX-VVKfailAutomated Verification and Validation of Key Security Indicators. Providers seeking 20x Class A Certification MAY implement automated methods to persistently verify and validate the accuracy and completeness of Key Security Indicators.FRC-CSX-VVRfailAutomated Verification and Validation of FedRAMP Rules. Providers seeking 20x Class A Certification MAY implement automated methods to persistently verify and validate the accuracy and completeness of the Security Decision Record for FedRAMP rules when applicable.FRC-CSX-MASfailApplication within MAS. Providers SHOULD apply ALL Key Security Indicators to ALL aspects of their cloud service offering that are within the FedRAMP Minimum Assessment Scope.
Incident evaluation and communication
IEC-CSO-EFRfailEvaluate FedRAMP Reportability. 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.IEC-CSO-DPRfailDefault PAIN Rating. 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).IEC-CSO-IIRfailInitial Incident Report. 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:IEC-CSO-OIRfailOngoing Incident Reports. 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:IEC-CSO-FIRfailFinal Incident Report. 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.IEC-CSO-EFIfailEstimate Federal Impact. 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.IEC-CSO-AIRfailAutomated Incident Reporting. Providers SHOULD use automation to minimize human intervention in the process of reporting FedRAMP Reportable Incidents to all affected parties.
Independent verification and validation
IVV-CSO-FIAfailFedRAMP Independent Assessments. Providers with Class A Certifications MAY persistently complete an independent verification and validation assessment of all applicable FedRAMP rules with a FedRAMP Recognized independent assessment service OR FedRAMP at least once per year; this is a FedRAMP independent assessment.IVV-CSO-SEIfailSupply Evidence of Implementation. Providers MUST supply evidence to all necessary assessors of the implementation of the measures that have been documented to meet FedRAMP Practices; this evidence is the result of verification.IVV-CSO-SEEfailSupply Evidence of Effectiveness. Providers MUST supply evidence to all necessary assessors of the effectiveness of the measures that have been implemented to meet FedRAMP Practices; this evidence is the result of validation.IVV-CSO-ICPfailInclusion in Certification Package. Providers MUST supply the results of FedRAMP independent assessments in their FedRAMP Certification Package without inappropriate modification.IVV-CSO-DUSfailDocument Use of Representative Samples. Providers MUST document and explain the use of representative samples during verification and validation when using representative samples as allowed by IVV-CSO-USR (Use Representative Samples).IVV-CSO-STEfailSupply Technical Explanations. Providers SHOULD supply all necessary assessors with technical explanations, demonstrations, and other relevant supporting information about the technical capabilities they employ to address FedRAMP rules; this SHOULD be supplied as necessary to ensure the assessor can effectively complete verification and validation.IVV-CSO-USRfailUse Representative Samples. Providers MAY use representative samples as appropriate during verification and validation.IVV-CSO-RAAfailReceiving Assessor Advice. Providers MAY ask for and accept advice from their assessor during assessment regarding techniques and procedures that will improve their security posture or the effectiveness, clarity, and accuracy of their verification, validation and reporting procedures, UNLESS doing so is likely to compromise the objectivity and integrity of the assessment.IVV-CSX-AIAfailAnnual Independent Assessments for 20x. Providers with 20x Class A Certifications MUST meet the expectations of their underlying alternative security framework as part of their persistent independent verification and validation assessment.
Minimum assessment scope
MAS-CSO-IIRfailIdentify Information Resources. Providers MUST identify a set of information resources to assess for FedRAMP Certification that includes all information resources that are likely to handle federal customer data or likely to impact the confidentiality, integrity, or availability of federal customer data handled by the cloud service offering; this set of information resources is the cloud service offering.MAS-CSO-FLOfailInformation Flows and Security Categories. Providers MUST clearly identify, document, and explain information flows and security categories for ALL information resources or sets of information resources in the cloud service offering.MAS-CSO-TPRfailThird-Party Information Resources. Providers MUST address the potential impact to federal customer data from third-party information resources used by the cloud service offering, ONLY IF MAS-CSO-IIR (Identify Information Resources) APPLIES, by documenting the following information about each applicable third-party information resource:MAS-CSO-MDIfailMetadata Inclusion. Providers MUST include metadata (including metadata about federal customer data) in the Minimum Assessment Scope ONLY IF MAS-CSO-IIR (Identify Information Resources) APPLIES.MAS-CSO-SUPfailSupplemental Information. Providers MAY include additional materials about other information resources that are not part of the cloud service offering in a FedRAMP Certification Package supplement; these resources will not be FedRAMP Certified and MUST be clearly marked and separated from the cloud service offering.
Marketplace listing
MKT-CSO-MLRfailMarketplace Listing Requirements. Providers MUST address at least these FedRAMP rules to apply for a new FedRAMP Marketplace listing OR to request updates to an existing listing:MKT-CSO-PMLfailProvider Marketplace Listing Requests. Providers MUST notify FedRAMP using the FedRAMP Marketplace Providing Listing Request Form to request a listing in the FedRAMP Marketplace.MKT-IIP-AGUfailAgency Use Cases. Providers MUST demonstrate that a cloud service offering is intended for one of the following use cases:MKT-IIP-DCPfailDemonstrating Continuous Progress. Providers MUST demonstrate continuous progress towards a FedRAMP Certification, documented in their Trust Center or website and updated at least quarterly; progress is measured by the provider against documented goals and milestones.MKT-IIP-DLAfailDeadline for Assessment. Providers MUST demonstrate that an assessment for a FedRAMP Certification Class B, C, or D has been scheduled within 2 years of initial listing in the Initial Implementation Phase.
Secure configuration guide
SCG-CSO-RSCfailRecommended Secure Configuration. Providers MUST create, maintain, and make available recommendations for securely configuring their cloud services (the Secure Configuration Guide) that includes at least the following information:SCG-CSO-AUPfailUse Instructions. Providers MUST include instructions in the FedRAMP Certification Package that explain how to obtain and use the Secure Configuration Guide.SCG-CSO-PUBfailPublic Secure Configuration Guidance. Providers SHOULD make the Secure Configuration Guide available publicly.SCG-CSO-SDFfailSecure Defaults. Providers SHOULD set all settings to their recommended secure defaults for top-level administrative accounts and privileged accounts when initially provisioned.SCG-ENH-CMPfailComparison Capability. Providers SHOULD offer the capability to compare all current settings for top-level administrative accounts and privileged accounts to the recommended secure defaults.SCG-ENH-EXPfailExport Capability. Providers SHOULD offer the capability to export all security settings in a machine-readable format.SCG-ENH-APIfailAPI Capability. Providers SHOULD offer the capability to view and adjust security settings via an API or similar capability.SCG-ENH-MRGfailMachine-Readable Guidance. Providers SHOULD also provide the Secure Configuration Guide in a machine-readable format that can be used by customers or third-party tools to compare against current settings.SCG-ENH-VRHfailVersioning and Release History. Providers SHOULD provide versioning and a release history for recommended secure default settings for top-level administrative accounts and privileged accounts as they are adjusted over time.
Significant change notification
SCN-CSO-EVAfailEvaluate Changes. Providers MUST evaluate all potential significant changes to determine the type of significant change and follow the appropriate Significant Change Notification rules.SCN-CSO-MARfailMaintain Audit Records. Providers MUST maintain auditable records of the significant change evaluation activities required by SCN-CSO-EVA (Evaluate Changes) and make them available to FedRAMP as requested.SCN-CSO-INFfailRequired Information. Providers MUST include at least the following information in Significant Change Notifications:SCN-CSO-HISfailHistorical Notifications. Providers MUST keep 12 months of historical Significant Change Notifications available with their FedRAMP Certification Data.SCN-CSO-HRMfailHuman and Machine-Readable Notifications. Providers MUST make ALL Significant Change Notifications and related audit records available in human-readable and JSON formats.SCN-CSO-ARIfailAdditional Relevant Information. Providers MAY include additional relevant information in Significant Change Notifications.SCN-CSO-NOMfailNotification Mechanisms. Providers MAY notify necessary parties in a variety of ways as long as the mechanism for notification is clearly documented in the FedRAMP Certification Package and easily accessible.SCN-CSO-EMGfailEmergency Changes. Providers MAY execute significant changes (including transformative changes) during an emergency or incident without following the Significant Change Notification rules in advance. In such emergencies, providers MUST follow all relevant procedures, notify all necessary parties, retroactively provide all Significant Change Notification materials, and complete appropriate assessment after the incident.SCN-ADP-NTFfailNotification Requirements. Providers MUST notify all necessary parties within 10 business days after finishing adaptive changes, also including the following information:SCN-RTR-NNRfailNo Notification Requirements. Providers SHOULD NOT make formal Significant Change Notifications for routine recurring changes; this type of change is exempted from notification requirements.SCN-TRF-NIPfailNotification of Initial Plans. Providers MUST notify all necessary parties of initial plans for transformative changes at least 30 business days before starting transformative changes, including a summary of any likely security impacts or changes in risk.SCN-TRF-NFPfailNotification of Final Plans. Providers MUST notify all necessary parties of final plans for transformative changes at least 10 business days before starting transformative changes, including updates to all previously sent information.SCN-TRF-NAFfailNotification After Finishing. Providers MUST notify all necessary parties within 5 business days after finishing transformative changes, including updates to all previously sent information.SCN-TRF-NAVfailNotification After Verification. Providers MUST notify all necessary parties within 5 business days after completing the verification, assessment, and/or validation of transformative changes, also including the following information:SCN-TRF-UPDfailUpdate Documentation. Providers MUST publish updated service documentation and other materials to reflect transformative changes within 30 business days after finishing transformative changes.SCN-TRF-TPRfailThird-Party Review. Providers SHOULD engage a third-party assessor to review the scope and impact of the planned change before starting transformative changes if human validation is necessary; such reviews SHOULD be limited to security decisions that require human validation.
Security decision record
SDR-CSO-FRRfailFedRAMP Rules. Providers MUST supply a Security Decision Record, in both human-readable and JSON formats, that includes at least all of the following information for each applicable FedRAMP rule:SDR-CSO-MTDpassSecurity Decision Record Metadata. Providers MUST also include the following basic metadata in their Security Decision Record:SDR-CSX-KSIfailKey Security Indicators. Providers MUST also include short and simple high-level summaries of at least the following for each applicable Key Security Indicator:SDR-CSX-KMTfailKey Security Indicator Metrics. Providers with 20x Class A Certifications MAY also include historical metrics in their Security Decision Record.
Vulnerability detection and response
VDR-CSO-DETfailVulnerability Detection. Providers MUST systematically, persistently, and promptly discover and identify vulnerabilities within their cloud service offering using appropriate techniques such as assessment, scanning, threat intelligence, vulnerability disclosure mechanisms, bug bounties, penetration testing, incident response, automated control testing, supply chain monitoring, and other relevant capabilities; this process is called vulnerability detection. Vulnerability detection includes persistently verifying and validating that information resources and processes are operating as intended and documented for FedRAMP Practices.VDR-CSO-RESfailVulnerability Response. Providers MUST systematically, persistently, and promptly track, evaluate, monitor, mitigate, remediate, assess exploitation of, report, and otherwise manage all detected vulnerabilities within their cloud service offering; this process is called vulnerability response.VDR-CSO-FAVfailFailures Are Vulnerabilities. Providers MUST treat problems or failures with their vulnerability detection and response processes as vulnerabilities.VDR-CSO-DFRfailDesign For Resilience. Providers SHOULD make design and architecture decisions for their cloud service offering that mitigate the risk of vulnerabilities by default AND decrease the risk and complexity of vulnerability detection and response.VDR-CSO-ADTfailAutomate Detection. Providers SHOULD use automated services to improve and streamline vulnerability detection and response.VDR-CSO-DACfailDetect After Changes. Providers SHOULD automatically perform vulnerability detection on representative samples of new or significantly changed information resources.VDR-CSO-MSPfailMaintain Security. Providers SHOULD NOT weaken the security of information resources to facilitate vulnerability scanning, detection, or assessment activities.VDR-CSO-AKEfailAvoid KEVs. Providers SHOULD NOT deploy or otherwise activate new machine-based information resources with Known Exploited Vulnerabilities.VDR-CSO-SIRfailSampling. Providers MAY sample effectively identical information resources, especially machine-based information resources, when performing vulnerability detection UNLESS doing so would decrease the efficiency or effectiveness of vulnerability detection.VDR-TFR-NMVfailNon-Machine Verification and Validation. Providers MUST verify and validate the status of non-machine-based information resources at least once every 3 months.VDR-TFR-PDDfailPersistent Drift Detection. Providers with Class A Certifications SHOULD persistently perform vulnerability detection on all information resources that are likely to drift, at least once every 3 months.VDR-TFR-PCDfailPersistently Complete Detection. Providers with Class A Certifications SHOULD persistently perform vulnerability detection on all information resources that are NOT likely to drift, at least once every 6 months.VDR-TFR-PVRfailMitigation and Remediation Expectations. Providers with Class A Certifications SHOULD partially mitigate vulnerabilities, fully mitigate vulnerabilities, or remediate vulnerabilities to a lower potential agency impact within the timeframes from evaluation shown below, factoring for the current Potential Agency Impact N-rating as defined in VER-EVA-EPA (Estimate Potential Agency Impact), internet reachability, and likely exploitability.VDR-TFR-RMNfailRemaining Vulnerabilities. Providers SHOULD mitigate or remediate remaining vulnerabilities during routine operations as determined necessary by the provider.VDR-TFR-KEVfailRemediate KEVs. Providers SHOULD remediate Known Exploited Vulnerabilities according to the due dates in the CISA Known Exploited Vulnerabilities Catalog (even if the vulnerability has been fully mitigated) as required by CISA Binding Operational Directive (BOD) 26-04 or any successor guidance from CISA.VDR-TFR-PSDfailPersistent Sample Detection. Providers with Class A Certifications SHOULD persistently perform vulnerability detection on representative samples of similar machine-based information resources, at least once every 14 days.VDR-TFR-MVXfailPersistent Machine Verification and Validation for 20x. Providers of FedRAMP 20x Class A offerings SHOULD verify and validate the status of machine-based information resources at least once every month.
Vulnerability evaluation and reporting
VER-EVA-ELXfailEvaluate Exploitability. Providers MUST evaluate detected vulnerabilities, considering the context of the cloud service offering, to determine if they are likely exploitable vulnerabilities.VER-EVA-EIRfailEvaluate Internet-Reachability. Providers MUST evaluate detected vulnerabilities, considering the context of the cloud service offering, to determine if they are internet-reachable vulnerabilities.VER-EVA-EPAfailEstimate Potential Agency Impact. Providers MUST evaluate detected vulnerabilities, considering the context of the cloud service offering, to estimate the likely potential agency impact of exploitation on government customers AND assign one of the following Potential Agency Impact N-ratings (PAIN):VER-EVA-AIAfailAssume It's Automatable. Providers MUST assume the exploitation of vulnerabilities can be automated UNLESS they have evidence proving otherwise.VER-EVA-GRVfailGroup Vulnerabilities. Providers SHOULD evaluate detected vulnerabilities, considering the context of the cloud service offering, to identify logical groupings of affected information resources that may improve the efficiency and effectiveness of vulnerability response by consolidating further activity; FedRAMP Vulnerability Detection and Response rules are then applied to these consolidated groupings of vulnerabilities instead of each individual detected instance.VER-EVA-EFPfailEvaluate False Positives. Providers SHOULD evaluate detected vulnerabilities, considering the context of the cloud service offering, to determine if they are false positive vulnerabilities.VER-EVA-EFAfailEvaluation Factors. Providers SHOULD consider at least the following factors when considering the context of the cloud service offering to evaluate detected vulnerabilities:VER-RPT-PERfailPersistent Reporting. Providers MUST report vulnerability detection and response activity (including persistent verification and validation) to all necessary parties persistently, summarizing ALL activity since the previous report; these reports are FedRAMP Certification Data and are subject to FedRAMP Certification Data Sharing rules.VER-RPT-VDTfailVulnerability Details. Providers MUST include the following information (if applicable) on detected vulnerabilities when reporting on vulnerability detection and response activity, UNLESS it is an accepted vulnerability:VER-RPT-AVIfailAccepted Vulnerability Info. Providers MUST include the following information on accepted vulnerabilities when reporting on vulnerability detection and response activity:VER-RPT-NIDfailResponsible Disclosure. Providers MUST NOT irresponsibly disclose specific sensitive information about vulnerabilities that would likely lead to exploitation, but MUST disclose sufficient information for informed risk-based decision-making to all necessary parties.VER-RPT-HLOfailHigh-Level Overviews. Providers SHOULD include high-level overviews of ALL vulnerability detection and response activities conducted during this period for the cloud service offering; this includes vulnerability disclosure programs, bug bounty programs, penetration testing, assessments, etc.VER-RPT-RPDfailResponsible Public Disclosure. Providers MAY responsibly disclose vulnerabilities publicly or with other parties if the provider determines doing so will NOT likely lead to exploitation.VER-TFR-MHRfailMonthly Activity Report. Providers MUST report vulnerability detection and response activity to all necessary parties in a consistent format that is human readable at least monthly.VER-TFR-MAVfailMark Accepted Vulnerabilities. Providers MUST categorize any vulnerability that is not or will not be fully mitigated or remediated within 192 days of evaluation as an accepted vulnerability.VER-TFR-MRHfailHistorical Activity. Providers with Class A Certifications MAY make all recent historical vulnerability detection and response activity available in JSON format for automated retrieval by all necessary parties (e.g. using an API service or similar); this information MAY be updated persistently, at least once every month.VER-TFR-EVUfailEvaluate Vulnerabilities Quickly. Providers with Class A Certifications SHOULD evaluate ALL vulnerabilities as required by VER-EVA (Evaluation) within 14 days of detection.VER-TFR-IRIfailInternet-Reachable Incidents. Providers with Class A Certifications MAY treat internet-reachable likely exploitable vulnerabilities where Potential Agency Impact N-rating > 3 as a FedRAMP Reportable Incident until they are partially mitigated vulnerabilities at N3 or below.VER-TFR-NRIfailNon-Internet-Reachable Incidents. Providers with Class A Certifications MAY treat likely exploitable vulnerabilities that are NOT internet-reachable where Potential Agency Impact N-rating = 5 as a FedRAMP Reportable Incident until they are partially mitigated vulnerabilities at N4 or below.