Repository navigation
Rev5 questions and discussion on the Consolidated Rules for 2026 (or Legacy) #146
Replies: 63 comments 171 replies
|
Can you confirm whether the March 7, 2027 grace period defined in NTC-0014 remains accurate and unchanged? Specifically, is this grace period still authoritative, or has it been superseded or modified by the CR26 Consolidated Rules timeline, including the January 1, 2027 mandatory adoption date? As per NTC-0014: "FedRAMP will provide a grace period through March 7, 2027 where cloud service offerings may maintain their FedRAMP Certification under a corrective action plan (which will include notice to all agencies). After this date, FedRAMP Certification will be revoked for all cloud service offerings not following these rules." |
|
After review of the Rev 5 SCN process ahead of the July 4 optional adoption date, we noticed the published schema (fedramp-significant-change-notification-schema-2026-06-24.json) does not match the SCN-CSO-INF required fields SCN-CSO-INF, which mandates 10 fields in every notification. The schema marks only 3 as required (certificationPackageOverviewUri, changeType, changeDescription) and does not include:
|
|
Thanks Pete--I appreciate the approach your describe, however, the schema marks 3 fields as "required" with one, certificationPackageOverviewUri not even being in SCN-CSO-INF. Can we change "required" to "recommended"? |
|
If going for a new Rev5 certification prior to Jan 1, 2027, are CSPs required to follow the new CR26 Rev5 baseline/control guidance, or can they still use the old Legacy Rev5 parameters, SSP templates, SAP/SAR templates, etc? Similarly for assessors, for new Rev5 certification assessments prior to Jan 1, are they required to assess against the new CR26 Rev5 baseline/control guidance, or should/can they continue to follow the Legacy Rev5 rules/templates? Or is this choice up to the CSP/agency? I think I can intuit the answer from the Important Dates/Deadlines, without an explicit statement about which elements of Legacy Rev5 are still officially allowed (though maybe I am just not finding that statement) - which is that this is ultimately up to what the agency customer wants/agrees to with the CSP. Ie, the assessor can assess against the set of rules they are directed to assess by the CSP/agency, whether Legacy Rev5 or CR26 Rev5, up until a given CR26 rule or the full CR26 ruleset is explicitly stated to be mandatory for Rev5. This is especially relevant to CSPs who were already well along the path toward Rev5 and did not want to wait for the finalized CR26 rules to be available. For example, if they are about to be assessed now or in the next few months, and had worked over X time period to set up their system/documentation/etc using Legacy Rev5 rules, templates, etc. Corollary - what needs to be done by Jan 1, 2027 - is it enough to have completed the Legacy Rev5 assessment with the assessor, or does the agency/FedRAMP need to also approve the Legacy Rev5 certification prior to Jan 1? |
|
For a Rev5 Class C (Moderate) CSO with multiple agency ATOs, what are the consequences if they do not implement any CR26 Rev5 rules? At which date would they be exposed to those consequences? |
|
For the CDS-TRC-USH Rev. 5 requirement stating that “Trust Centers MUST share FedRAMP certification data with all necessary parties without interruption,” we are considering leveraging our Trust Center as the primary mechanism for providing stakeholders, including agency customers, with access to certification information. Under this model, we, as the Cloud Service Provider (CSP), would retain responsibility for provisioning and deprovisioning access to the Trust Center. Our interpretation is that the existence of a dedicated Trust Center, combined with an established operational process and support team responsible for managing access, satisfies the intent of providing certification data to authorized stakeholders without interruption. Given that we maintain a dedicated process and team to provision access, support affected customers, and provide alternative access mechanisms when necessary to the same Trust Center, our position is that these customer-imposed network restrictions should not constitute noncompliance with the “without interruption” requirement. We believe we are taking reasonable and proactive measures to ensure continuous availability of certification information to authorized parties despite circumstances that are outside our direct control. Do you have any concerns or objections to this interpretation and approach? |
|
I know the answer to this question will be "we're reasonable people", but confusion is still rampant. For the deadline where "FedRAMP will stop accepting any new FedRAMP Rev5 Certifications on June 11, 2027," does this mean a CSP cannot apply for a new Rev5 Marketplace Listing after June 10, 2027? Or FedRAMP will not accept Rev5 packages for CSPs who are already in process? Thanks. |
|
VDR-TFR-NMV states "Providers MUST verify and validate the status of non-machine-based information resources at least once every 3 months" and once you break down the definitions, I'm interpreting the requirement as: "CSPs must verify and validate documentation, personnel, and budgets every 3 months"
Is this an accurate interpretation of the requirements involved? And while the -1 controls in each control family in Rev5 would revert back to the ODPs, wouldn't this effectively create a new and different requirement for the policies and procedures (as well as various other documents)? Instead of reviewing them every 1/3 years, now they'd need to be verified and validated every 3 months. And then finally, if all of the above is true, would it make sense to notate this on the "Rev5 Control Guidance" page, given there's no direct mention that a VDR rule is impacting documentation? |
|
We have a Class D CSO with an existing Rev5 Agency ATO that does not meet the Cloud Native Architecture (KSI-CNA) requirement. Since no current 20x pathway exists for a non-cloud-native CSO of this Certification Class, we request clarification on the following: Pathway & Timeline
ATO Continuity
Marketplace Listing
Tracking & Escalation
|
|
Did I hear correctly on this afternoon's CWG call, that if a Rev5 CSP doesn't adopt VDR and VER by 12/7/26 they will be considered non-compliant and labeled as such on the Marketplace? So, even though there is a grace until 3/7/27 we are non-compliant on 12/8/26 if we haven't adopted all of VDR and VER? I also heard that we could let FedRAMP PMO know where we are in implementation and supply a CAP to get there by 3/7/27. Does that mean if we provide implementation status and CAP to get there by 3/7/27 that we wouldn't be labeled as non-compliant on Marketplace? Also, wondering if a Significant Change Assessment is considered an independent assessment for Grace Ends. We are a Rev 5 CSP who has their annual assessment in November 2026 who will receive SAR after 1/1/2027. Do we have a grace period until our next assessment in November 2027, or do we have to adopt the 1/1/2027 rulesets with our first Significant Change Assessment in 2027? Or must we adopt 1/1/2027 rulesets with our November 2026 annual assessment? |
|
For VDR-CSO-SIR, the following is written: "Providers MAY sample effectively identical information resources...". This points to sampling being a optional rule, but not strictly necessary. However, a later VDR rule, VDR-TFR-PSD, states the following: "Providers with Class C Certifications SHOULD persistently perform vulnerability detection on representative samples of similar machine-based information resources, at least once every 3 days." Understanding that technically SHOULD rules have some wiggle room, does the combination of these two rules read as:
|
|
I have similar questions as @zeesharfcspab stated in a comment above. For CSPs who completed their legacy Rev5 annual assessment before CR26 Rev5 was published, and whose next annual assessment does not begin again until H1 of 2027. This creates a window where several rulesets reach their maintain date without an intervening FedRAMP independent assessment. I am trying to confirm how conformance is demonstrated in the interim to avoid the stated CAP that will be given to CSPs if the maintain date is not met (stated in the CR26 Rev5 community update 8/5). My questions are as follows:
|
|
Hello! Question: for an existing Rev 5 adoption of CR 26, I understand that the only rules we are required to implement are those classified as "Rev 5" and "All," and that any that are labeled 20x would be filtered out. Can I get a confirmation on this please? We want to make sure we scope correctly. |
|
Hello, for a Lost Sponsor/Readiness Conversion Rev 5 path, what deliverables are expected at our next annual assessment? I understand that SAP/SAR/RET are legacy now, so it would be great to get clarity on scoping the audit with our independent assessor. Thank you! (and happy Friday!!) |
|
Hello, for CSPs with an existing Rev5 Class C certification looking to uplift their offering to Rev5 Class D via agency sponsor, will this have to be completed/submitted by the June 2027 Rev5 cutoff for new Rev5 submissions? Thanks! |
|
Hello FedRAMP PMO team, Hoping to get some clarification on who incident reports actually go to under the Incident Report rules (IEC-CSO-IIR / OIR / FIR). The rule statement and the notification requirement seem to point to two different, separately-defined groups: Rule statement: notify all affected parties = "FedRAMP and directly impacted federal customer agencies." Our reading is that the affected parties receive the incident reports, while all necessary parties review certification-wide reporting like the quarterly OCR (which already summarizes incidents). Sharing full incident reports with all necessary parties would also seem to tension with CDS-CSO-RIS (don't share detail that would enable a threat actor). Could the PMO confirm which is intended? |
|
For Ready Conversion applicants with a penetration test performed by an independent third party that is not a FedRAMP-recognized independent assessor, may the designated independent assessor conducting the Ready Conversion assessment review, validate, and incorporate those results into the CSP's initial certification assessment, or must the independent assessor independently execute another penetration test? |
|
Under CR26's IEC and VDR/VER reporting requirements, how should a CSP handle a vulnerability that falls within its authorization boundary but is subject to an active coordinated disclosure embargo with the affected vendor, particularly where the vulnerability meets the threshold for a FedRAMP Reportable Incident, requiring prompt notification to FedRAMP and affected agencies? Does CR26 provide any mechanism to defer or redact CVE-specific details in government-facing reports while an embargo is in effect, and if not, what is the recommended approach to reconciling these conflicting obligations without breaking the embargo or falling out of compliance? Additionally, is there an existing FedRAMP or CISA coordination process that CSPs can leverage in these situations? |
|
Apologies in advance if some of these questions overlap with topics covered during previous community updates. However, I’d rather seek a bit more clarification than make assumptions, particularly since there are a few specific scenarios that I don’t believe have been fully addressed. Per the September A&A Community Update, the PMO suggested that assessors only need to IV&V what a CSP says they are doing to meet a control…and if a CSP disregards particular aspects of controls, then the assessor does not have to perform IV&V on those particular control requirements (https://www.youtube.com/watch?v=eU--WLLxkbE&t=2134s). This approach meets rule IVV-IAS-VIM for verification (e.g., ensuring that the implemented measures match what’s documented by the CSP). However, I am unclear if this approach fully meets rule IVV-IAS-VEF for validating effectiveness (e.g., ensuring that the implemented measures produce “the intended outcome for meeting FedRAMP practices”). In the context of a rev5 assessment, it seems that the “intended outcome” has to include the elements of the control baseline. If instead assessors limit the assessment to just what the CSP says they care about, then it’s not clear how the assessor can perform independent validation as it is defined in the rules. To provide some context for the questions below, I want to use NIST 800-53, AC-2 (Account Management) control as an example. The Rev5 control has 14 Determine If (assessment) objectives. For simplicity, let’s focus on 4 of them: i. Determine if accounts are created, enabled, modified, disabled, and removed in accordance with [organization-defined policy, procedures, prerequisites, and criteria] Using the above 4 objectives as examples, I'd appreciate clarification on the following scenarios: Question 1: If a CSP’s “Implementation” and “Verification and Validation” statements speak to objectives (i), (ii), and (iii) only, should the assessor flag a gap for the CSP not speaking to objective (iv)? Question 2: For the above scenario under Question 1, is the assessor still expected to independently assess objective (iv), even though the CSP did not include it in its own implementation description and verification/validation activities? Or does the assessor just note the CSP has not implemented the objective or done V&V? Or is it the case that the assessor doesn’t even have to mention it because it wasn’t in the CSP’s implementation and V&V for AC-2 to begin with? Question 3: Suppose a CSP’s validation of objective (i) is insufficient or flawed…for example, the CSP only validates (and intends to validate) that a sample of terminated user accounts is currently disabled but does not determine whether those accounts were disabled within the required timeframe following their actual termination date (as defined by the CSP in their ODP). Is the assessor's IV&V responsibility limited to only confirming that the CSP performed its stated validation activities, or is the assessor expected to identify deficiencies in the CSP’s validation approach and perform additional testing, as necessary, to determine whether the applicable control requirements are fully satisfied? Question 4: [Ties a bit to question 3 but want to ask it more directly] Rules IVV-CSO-SEI and IVV-CSO-SEE imply that CSPs are to gather evidence to perform their own V&V and then pass that same evidence along to the assessor for the IV&V. Is the assessor expected to perform IV&V using only the evidence collected and evaluated by the CSP, or is the assessor expected to request additional evidence if CSP has not effectively gathered sufficient documentation? |
|
Good morning. I've been looking everywhere, but I cannot seem to find the answer. If a CSP is wanting to go for a 20x certification, but already has a Rev5 ATO, for the next AA, can they do a 20x to get certified or do they need to still do a Rev5 while trying to obtain a 20x? What is the process for transitioning from Rev5 to 20x? Sorry if this has been asked and answered however I am not able to locate this process anywhere. Thank you. |
|
Question on FedRAMP's handling of the JSON from CDS-CSO-PUB. The rule and schema require a Sales and a Security contact (matches Marketplace). Both rule and schema:
How will the Marketplace handle additional contacts and additional contact types? For example: will it list all types as headings, with all contacts of that type under the heading? Will the Marketplace use the JSON's additional fields (phone, or custom fields we add)? Or only continue to display name + email? Our current security contact is our Certifications team, which is also our FedRAMP Security Inbox. If we add our PSIRT team as a second Security contact, how will the FSI be identified? The schema doesn't support multiple types (e.g. Security + Primary) for a given contact to denote it as the FSI. And without additional context (e.g. a "contactRole" field to describe the function) it won't be clear on Marketplace when to engage which "security" contact. Thanks |
|
We are planning the CR26 transition and would appreciate clarification on what FedRAMP expects from CSPs in supporting agency adoption. Could you clarify:
We want to support agencies appropriately while avoiding unnecessary duplicate reporting and open-ended follow-up. What level of outreach and agency education is expected from CSPs, and should unresolved agency adoption be referred to FedRAMP? In my recent discussions with multiple agencies, the contacts I spoke with were unfamiliar with CR26. What communications or guidance has FedRAMP provided to agencies, and what additional outreach and education will FedRAMP perform? |
|
Good morning, FedRAMP team. We have a few CSPs reaching out about uplift requirements from Rev5 Class C to Rev5 Class D. We understand that the uplift will have to be submitted to FedRAMP prior to the June 11, 2027 deadline, but wanted to get clarity on what's required to be submitted. Based on SCN-CSO-EVA and FRC-CCL-UCC, it states that an uplift assessment cannot be considered a significant change and would require a new assessment and the provider would need to apply for a new FedRAMP Certification. Does that mean that a CSP with an established FedRAMP Certification would need to have a full initial assessment done by an independent assessor or could they submit their most recent (or upcoming) annual assessment and test results against the additional Class D FRRs and Rev. 5 controls assessed? Thank you! |
|
Thanks for the info about the VDR-VER enforcement process in this week's townhall. In anticipation of more details being released next week, I have a question for the CSPs who will be in limbo in December (kinda like FedRAMP purgatory), which is where they will have just finished their initial Rev 5 assessment or be in the middle of one in early December and are most likely still trying to implement a VDR-VER process. Will they get the email you mentioned during the townhall and have to submit the mini-SDR and sample vuln report, even though they officially aren't FedRAMP Certified yet? I assume yes, but just wanted to check. |
|
Our independent assessor team is putting together our templates and processes for doing CR26 rev 5 assessments and would appreciate some clarified expectations. As a base, our IA write-ups will probably be phrased around verification and validation, with a pass or fail for each of those. Just for context, we are asking because previous reviewers got VERY particular with what they wanted to see in writing and kicked work back to the team until it met their (unpublished) expectations. We would prefer to not repeat this experience.
|
|
I have a very specific Accepted Vulnerability question. Per Rule VER-TFR-MAV: 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. Given the following:
Is this following statement correct: |
|
I have a question about the difference between the required VER-RPT-VDT and VER-TFR-MRH reports for a Rev5 Class D provider. Since both reports cover a seven-day period, our engineering team is trying to understand whether the MRH report should include every currently active vulnerability and every accepted vulnerability. We understand that the VER-RPT-VDT report is a rollup over the previous 7 days of VDR/VER activity - we're just trying to understand the outer bounds for how large the MRH report could get. For example, if we have hundreds of accepted vulnerabilities over a three-year term, will the MRH report continue to grow as each one is added, or should it be limited to a defined look-back period, such as the past 90 days or year? Understanding the expected scope will help us design the VDR/VER API request and response parameters to store and deliver the reports effectively. |
|
We have recently listed PowerTrain Government Enclave Azure on the FedRAMP Marketplace. We are working with our sponsor to complete the FedRAMP Agency Authorization - In-Process Request form to send to intake@fedramp.gov. The form specifies that a WWBS is required. However, when clicking the link in the form for the WBS template, it's a dead link. We have already completed the 3PAO assessment, and we have the final SAR which was completed less than 6 months ago. We will be providing our Sponsor with the SAR and other security documentation who will then review them and issue an ATO for the system. Questions:
We also have an existing Government Learning Enclave in FedRAMP. How much time will we be provided to migrate this system to the FedRAMP 20x? |
|
For the FedRAMP Incident Evaluation and Communication (IEC) rule related to ongoing incident notifications, IEC-CSO-OIR, could you provide guidance on which of the following reporting approaches CSPs should follow?
|



Uh oh!
There was an error while loading. Please reload this page.
This thread is for any and all Q&A or general discussion related to FedRAMP Rev5 in general that does not need to have its own thread.
FedRAMP released the Consolidated Rules for 2026 on June 24, 2026 with a considerable set of changes for FedRAMP Rev5 that will apply to all cloud service providers.
These changes include:
Some of these changes take effect for all cloud service providers on certain dates no matter what, others take effect at the next annual assessment. In general, these are sweeping changes that will require all cloud service providers to begin planning now to continue to meet FedRAMP Rev5 requirements.
Historical materials are available at https://fedramp.gov/legacy.
You may see some of the following folks from FedRAMP responding in this thread:
pete-gov- Pete, FedRAMP Directornicole-gov- Nicole, Security Directordan-fedramp- Dan, Lead Cloud Security Engineerpaulagosta- Paul, Lead Cloud Security Engineer (Bastion)emu-gov- Emu, Lead Cloud Security Engineer (Vanguard)rhoesing- Ryan, Chief of Staff & Policy Branch ChiefAll reactions