Skip to content

FedRAMP Rev5 Community Update

PublishedGSA and FedRAMP · FedRAMP video · November 4, 2026
Play the video: FedRAMP Rev5 Community Update

The player loads from YouTube only when you press play.

What the video covers

Written by TubeOnAI's AI from the video. A person has not checked it; the video is the authority.

FedRAMP Rev 5 Community Update Summary

What FedRAMP said

FedRAMP announced implementation requirements for Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) rules under CISA Binding Operational Directive 2604. FedRAMP will collect implementation data from cloud service providers starting in early December, with a December 7 deadline set by CISA. Providers who do not fully implement VDR and VER by March 7 will be placed in remediation; those without approved corrective action plans or who fail red team assessments will have their FedRAMP certifications revoked and be banned for one year.

What changes for agencies

Agencies will receive vulnerability information from cloud service providers in a new format based on risk-based prioritization rather than all detected vulnerabilities. Agencies are responsible for their own risk decisions about cloud service use and may impose stricter timelines than FedRAMP's grace period. Agencies should expect to see provider status clearly marked as "in remediation" after February 3 if providers have not fully implemented VDR and VER.

What changes for cloud providers

Cloud providers must fully implement all "must" and "must not" requirements in VDR and VER rules and appropriately address all "should" requirements by December 7, 2024. Providers must document their implementation status for each of approximately 60 rules, provide short explanations and risk mitigation information, and submit sample vulnerability reports. Providers cannot claim vendor dependency for VDR and VER implementation. Providers should implement changes through their existing change management processes (SCN or STR) rather than requiring 3PAO assessment for most changes. Providers must respond to emergency test notifications from FedRAMP or face administrative action.

Dates and deadlines

  • December 1–10: FedRAMP sends emergency test notification
  • December 7: CISA deadline for VDR and VER implementation; official FedRAMP deadline
  • December 17: Deadline to respond to emergency test notification with implementation status and corrective action plan (if needed)
  • February 3: Deadline for corrective action plan target completion dates; after this date, FedRAMP will formally review and approve all corrective action plans
  • March 7: FedRAMP grace period deadline; all providers without full implementation or approved corrective action plan moved to remediation; providers without approved corrective action plans or who refuse red team assessment have certification revoked
  • Next week (after November 4): Public notice and website with implementation requirements, templates, schemas, CSV templates, corrective action plan template, FAQ, examples, and discussion forum

Documents and programs mentioned

  • CISA Binding Operational Directive 2604
  • Vulnerability Detection and Response (VDR) rules
  • Vulnerability Evaluation and Reporting (VER) rules
  • FedRAMP Rev 5
  • FedRAMP marketplace
  • Agency Provided Offerings (Class G certification)
  • Significant Change Notification (SCN)
  • Significant Technical Review (STR)
  • System Security Plan (SSP)
  • Plan of Action and Milestones (POAM)
  • Continuous Monitoring (ConMon)
  • Mini Security Decision Record (mini SDR)
  • GitHub (FedRAMP community)
  • feder.gov2026 log (for rule updates)
  • FISMA
  • A-130
  • USDA Connect
  • Login.gov
  • Cloud.gov
  • Go.gov
  • Red team assessment
Read the transcript

Why don't we go ahead and start with the disclaimer and stuff? Everybody's used to them by now. So obviously we're recording this meeting. Disclaimer today that we are communicating today in our official capacity on behalf of Fedramp at the General Services Administration. We hold these meetings to enhance transparency between industry and Fedramp so that we can open a dialogue and share new developments. Nothing we share constitutes business advice and any reference in this conversation to any specific commercial product or the use of any corporation name is for the information and communities of the public and does not constitute endorsement, recommendation or favoring by GSA. One of the other important things about this meeting is that we're going to talk about plans. Plans that Feder has plans that Feder has for you. Um, one of the things that makes this difficult at times, if you've been in the Feder game for a minute, you'll understand that sometimes the plans that we make get uh buses driven through them by other agencies and uh, you know, people with different amounts of authority and expectations. So, everything we're going to talk about today is the best of our intent, subject to change. So, as always, we'll ask you to just kind of like pay attention and follow along. The main topic of today is going to be all about the VDR and the VER, the vulnerability uh detection and response rules as well as the vulnerability evaluation and reporting rules. We're going to talk about enforcement, how what we expect, how we will ask cloud service providers to demonstrate they have met things and how we plan to collect data related to all of that. Um, and it should be fun. We'll have some time for questions and stuff like that at the end, too. Um, but if you have questions on particular topics as we go through, please feel free to ask. One thing to keep in mind is that we're going to follow up with this early next week with a notice. So, it's going to have a notice. It's going to have a bunch of a web page with a bunch of information. So today we're just trying to kind of put this out for you so you have it in the back of your mind so that when you get the notice uh you're not freaking out trying to interpret it because it's going to be like five pages. Um so you know it's there's I'm going to throw a ton of information at you today. Um but is what it is. Also, I'll just say I am sick with a fever and slightly mildly delirious. So if I start getting a little bit wonky and crazy, well that'll be fun. All right, let's go to the next page. All right. So, the first thing that we're going to uh recap is rules updates. Couple things about these. Remember, you go to feder.gov2026 log. We put updates in there. Uh I after some feedback from a lot of folks as well as we've gotten to the point where these rule changes are starting to be incredibly minor. We're intending to switch to a monthly release. So, at the beginning of each month, we'll release a updated set of rules that will have um these changes. Uh, I know it's hard to read these changes here, but they're basically typos and, you know, things like that. It's nothing really impactful or worth talking about. We're also going to be adding formal version releases on GitHub, which is something that, you know, we we hadn't done before, but it'll make things a lot easier for everyone in the future. All right, so let's start talking about Baud 2604, the Vader, and how we got here. So the first of all I want to make sure everyone understands and this is for both agencies and cloud service providers. The baud 2604 explicitly uh gives fed ramp the authority to uh ensure compliance with that directive for uh cloud services in the scope of fedramp. M2614 also tells us to um be the bridge and like the sole kind of communication for cloud service providers in cases like this. As we go through how we're responding to this and what we're doing, I just want to remind everyone though that agencies have their own kind of priorities. Uh, but we think that if you're not hearing a lot of pressure from agencies right now about the VDR and the VER, it's because they're expecting us to handle this. We have lots of conversations with agencies about it. Uh, and it creates a little bit of a tense situation, a weird situation for us because I've had a lot of conversations with cloud service providers over the last month that are like, "Nobody at my agency wants this." It's like, "No, they do. They absolutely 100% do." uh and they are going to start getting hammered about it very soon. Um if you go to the next slide. So how we got here was a little interesting. We Fedramp started developing the VDR and the VER actually a year before BA 2604 and we did it entirely based on feedback and complaints from cloud service providers. I think this is one of the fascinating things that we kind of some folks sort of lost track of during this process was that probably the number two complaint that cloud service providers had uh two years ago. Uh the first one was significant changes. The second one was how incredibly terrible and stupid the continuous monitoring process was for FedRAMP and that for a actual um you know commercial entity that does good security the idea of just running these monthly vulnerability scans and then fixing everything based on CVSS scores was just like not how anything works, right? we were asked repeatedly to allow uh the consideration of context to allow the consideration of reachability um things like that and that's what the VDR and the VR were intended to do on the flip side we acknowledge I certainly acknowledge that industry doesn't have this with each other right like in I've never used a cloud service that sent me information about the vulnerabilities that they detected before in private sector that's not a thing that that happens, right? You just post something when it's like really really serious or really important. So, it is still an extra burden, but we're trying to make it as close to what your engineering team is already doing and as far away from the typical old federal legacy requirements as possible. This works great for folks that uh didn't build a GovCloud based around this process. Um, but folks that built Gulf clouds based around just doing vulnerability scans are struggling a little bit and we acknowledge that. But so is the whole federal government. That's why SISA wanted to have this changed. Uh, go ahead to the next one. So before we get into the details of what's going to happen with the VDR and the VER and what the implementation deadlines going to look like and what the enforcement is going to look like and all that stuff, if we do have any agency uh provided cloud service offerings on the call, we we have reached out to some of you and we'll reach out to more of you over the coming weeks. But we want to be clear that agency provided cloud service offerings. Those are the ones that are listed in the marketplace as by government for government, they are not expected to implement the VDR or the VER. They are expected to follow their uh AOS's instructions on CISO 2604. Uh so we have a very soon very very very soon pro hopefully uh next week or the week after we'll be releasing the agency provided offerings rule set which establishes the class G certification which allows government uh cloud service providers like login.gov for example um to obtain a Fedramp certification just by following the uh FSMA process within their agency and not having to also do extra stuff for FedRAMP. All right. Okay. Let's talk deadlines. Let's talk life, what we're planning, what we know. So, we set the December 7 deadline because that is the deadline that SISA set in BA 2604. It's still the deadline. December 7 is the official deadline in CISOB 2604. We do not expect SISA to change that deadline. Uh I was in a meeting just last week with a lot of SISOs and some folks from SISA and the government SISOs were a little bit upset about that deadline and SISA was not planning on changing it. Um but in the weird extreme case that SISA does change that deadline, we will modify that deadline too. So if SISA says, "Hey, we're going to give everyone an extra 90 days," we'll push back all these timelines by 90 days. Again, I don't think that's going to happen. It seems we all the indications are not, but I just want to be really really clear that we are going to be responsive. Like that is why the December deadline 7 deadline is there. We did not want to do the December 7 deadline. Originally, this was intended to be like September or something like that. Um, I see a hand up. Uh, if you could put a Q&A into the uh Q&A in the chat and the nine dots in the corner, that would be better because I don't have control over everyone's uh questioning on this one. All right, go ahead and go to the next one. Something I want to always remind folks is that FedRAMP does not accept risk. Agencies do. So, Fedramp determines the level risk appropriate for a Feder certification, but agencies determine the level risk appropriate to their specific use case of a cloud service. What this means is that Fedramp has given by default a grace period of three months past what CISA gave. That is a Fedramp specific grace period. That is not a grace period that applies to federal agencies. So there is still a possibility that in some circumstances agencies will be happy about that and others won't. Um if you go to the next slide Todd, it's really really important if you are banking on Fedramp's grace period that you connect with some of your agency users and find out if they're okay with that or not. Um that's just a situation you have to navigate. What we're promising is that we're not going to take away people's fed certification uh without a little bit more time, but agencies may decide to stop using your services or require you to take poams or something like that just depending on how important they feel about this. And I have literally been in situations with agencies where directives like this have resulted in them just shutting down systems because it's they just weren't going to get up to speed in time. go. The reason why I keep saying this is because when you talk to agencies, just remember that they have different threshold. And so if you say, well, FedRamp said we had until March 7, that doesn't necessarily fly with them. Okay. Um, go to the next slide. All right. So, let's talk about what's next. Um, and some details. This is going to be a lot like nitty-gritty gritty gritty gritty. Um, sorry, I lost my mouse here. So, what's next? Next week, we'll publish a public notice and a small website that will have information on the VDR VR implementation requirements that will explain how we will collect information from cloud services for agencies. We were expecting by now to receive some instructions from uh other entities about how this collection should take place and what it should look like and when it should happen. We have not received that and so we're establishing our own approach um you know in order to meet this. I unless there is a you know strict directive to collect this information along a different timeline. This is the timeline that I intend for Feder to collect this information on. Uh we're going to send an emergency test notification in early December. So somewhere between December 1 and December 10, everyone will get an emergency test notification in their inbox. that emergency test notification uh or emergency test message will ask you to attach some information about your VDR VER implementation progress as well as answer some questions about it. We anticipate the deadline for responding to that emergency test will be December 17. If you are following government budgeting, uh it's entirely possible the government will be shut down at that time. We still would expect you to complete by that deadline and we'll process that data when the government reopens um depending on whatever happens with the budget in December this year. We'll be collecting a short description for each rule in the VDRve and we'll be asking for sample vulnerability reports as well as your status. As always, you will have administrative action if you do not respond to the communications. Right? So, this is separate from administrative action for not implementing the VDRVER, which I'll talk about next. Um, but this is administrative action for not responding to the inbox. That is very serious. You must respond to those emergency notifications. Um, there's a few questions that one question that is um kind of bespoke we'll talk about at the end and then some other questions that we'll we'll just get to later. Um, okay. So, we want to help everyone prepare. So, we're going to be providing a website that's going to have a bunch of information next week. It's going to include what the implementation requirements are, more details about the uh mini SDR that we're going to the mini security decision record that we'll be asking for. It's going to include schemas and templates, and we'll include a CSV template in there because we know that a lot of folks are still going to be doing this by hand, and that's okay. It's going to include a template, a very basic template for a corrective action plan. It's going to have a list of information that you need to have ready for when you get that emergency test so that you can just like prep and get ready. You'll have a month. You'll know what you need to have ready. We're not going to we're going to try our best. If if we need to add something, we'll add it to that website, you know, so that you'll at least have some warning. It's going to have additional guidance on how to prepare for that data collection. It's going to have frequently asked questions. We've been asked a lot of questions on the forums and stuff like that. So, we're putting together a fact based on that. It's going to have some simple examples, which is really interesting and and fun. Um, I hate examples. I think most people have heard me talk about this before because examples have a way of becoming a ghost rule, but we're going to give some uh super intelligence generated examples to kind of show that it's not that big a deal. Don't overthink it. Just be chill. And finally, we'll have the ability to comment, ask questions, and a discussion forum thread about that. So, over the next month, we expect a lot of focus in our FedRAMP community to be about that. Next slide. I cannot be clear enough that Fed Ramp does not want anyone to fail this transition. I probably received two to five questions a day over the last couple of months about people just absolutely worried that they are going to lose their FedRAP certification. And I like as long as you are working in good faith and you do not have egregious security issues, you will not lose your Feder certification. There is a difference between someone that is behind and struggling and their customers can make a riskbased decision to continue to use their product versus someone that is simply refusing or unwilling or unable to implement new rules. So, Fed Ramp is not out to get anyone. We're going to be working with people throughout this. The intent is full transparency, openness, and opportunity here. Um, so let's talk about enforcement deadlines. There's a ton of stuff that's going to come up here. Again, notice is going to come out. It's going to have all of this in writing for you to refer to it in in detail, but this is broadly what we're talking about. Uh the number one question is when when will I be publicly noted as in remediation. So on December 17, if you respond to our data collection and you say you have not fully implemented the VDR and VER and you do not provide a corrective action plan to implement it, then you will be listed as in remediation. Alternatively, or also if you haven't fully implemented it and you do provide a corrective action plan, but your target completion date is after February three, so that's two more months, then you're telling us that it's going to take you at least three months and you're going to be right up to the grace period deadline for your corrective action plan, then we will put you in remediation. Now, this is where I come back to what I said last time. this probably just means that everyone's going to say their target completion date is February 3rd. Um, and like it is what it is. Um, like that's, you know, be be honest, I think, in advance, but if uh if that's what you want to do, you do you. Um, we're we're being very intentional that we're saying we want to spend the last month of February really focusing on corrective action plans and we're hoping that most people will have them done before then. So after February 3, you must now have your corrective action plan approved formally by FedRAMP. So if you read between the lines there, it means whatever corrective action plan you submit on December 17th, Fedrap's not going to approve it or disapprove it. We're just going to look at it. Maybe we're going to trust you and you're going to go to town after February 3. We're going to look at every single corrective action plan. We're going to ask for an updated one at that time and we're going to hopefully depending on how many people are behind meet with everyone that is on a corrective action plan still. There is one particular important thing I want everyone to understand which is that you may propose a target completion date after March 7. But if you do, you have to agree to a red team assessment from FedRAMP and we will coordinate with SISA to do a red team assessment to determine if your slow implementation is creating risks for the federal government. If you do not agree to that red team assessment, your corrective action plan will be denied. So just to recap, February or December 17th, you have a two-month corrective action plan period where nothing happens. Then you have one month where things get really, really, really serious. But you may continue out past March 7 as long as you are showing and uh producing forward motion. Uh if you go to the next slide, we'll talk about this a bit more. >> This is the the next one after March 7. >> Oh, right. Okay. Sorry, they look so similar. Um, okay. So, after March 7, everyone that hasn't implemented the VDR and the VR will be moved to in remediation if you're operating under a corrective action plan. So, when March 7 comes around, you're like, "Hey, I'm three weeks away from doing this. I'm, you know, six weeks. Like, here's the reason it's approved. You've agreed to a red team assessment." Then you're good. You will continue to operate. You will not lose your federap certification, but you will be placed in remediation. No matter what, anybody that doesn't have stuff implemented by March 7 is going in remediation. Like it's very important that agencies have the ability to understand without pulling your package that you are have not fully implemented this. At the same time, this is where we get to the important part. So this is the part everyone wants to understand. After March 7, you will have your Feder app certification revoked and you will be banned from Feder for one year if you haven't fully implemented the VDR or VR and you're not operating under approved corrective action plan. So, by now you've heard a lot about corrective action plans. If somehow you get all the way to March and you don't have an approved corrective action plan, that means you are egregiously failing to participate in the process and you will be remove you will be revoked uh your certification. Um or if you deny the red team assessment, we say, "Hey, we want to do a red team assessment with you." You agreed to it, and you're like, "No, we don't want to do that anymore. We're going to go ahead and just pull your FedEmp certification on that." Uh if you fail the red team assessment, which will as always be generous, but like if we do a red team assessment and find out that you have terrible, terrible, terrible vulnerability management and it's already in March and you haven't done anything to fix that, you're going to lose your FedRAMP certification. And then finally, if you fail to show timely progress and communicate openly and clearly on your corrective action plan, you will also have your FUD app certification revoked. And um people always ask like what does that mean? What is timely progress and communicate openly? I think the answer is that if you are not sure, if you are uh demonstrating timely progress and communicating openly, then you probably aren't. Um whereas if you are, then you know, and you you are. Um, so like that will be uh keeping us up to date on what's going on with your corrective action plan and you'll be fine. Um, and we'll probably be having at least monthly meetings if not uh more frequent with anybody that is still in a corrective action plan past March. So again, just want to reiterate and we'll take a break for a second for me to catch up on some of these questions. As long as you're working in good faith to adopt the new rules, you will not lose your Feder certification. All right. Now, I'm going to pop in and look at some of these questions and see if there's any relevant to that section before we go on to the next section. Um, so there's a question here that says, "How can we connect to your backend to validate that we are doing it right and completely? We are still experimenting but are not sure we're doing it all and doing it correctly." Um, you don't need to worry about that. just produce the the correct information that you want in the way that you want and that's sufficient. We're not worried about whether or not Feder can eat it in a particular automated way. Um, we're going to focus on that later. We're everyone's focused on implementation right now. Um, there's a question about FedAmp 20X, which I'm just going to get out of the way because Federal Ramp 20X is not Rev 5 and this is our Rev 5 community update. Um, there are some other questions that I do not understand. Um, here's a question. VER VDR implementation is a significant change STR SCN. What do I need to do in regards with the 3PAO and sponsoring agency? Second question, what guidance does Feder have for adjusting all the control families in the SSP? So, this is a great question. We get asked this all the time. We'll put it into the fact. uh you are expected to implement new rules following whatever process is appropriate. Uh we recommend that folks have by now November 4 hopefully you've already transitioned to the SCN or prepared SCRS for this with compensating risk or you have declared emergency changes um and and done it that way. Uh you need to to move fast. As far as a 3PAO, you don't need a 3PAO to review all of these changes in detail. Um, and as far as sponsoring agencies, we always like to remind people that sponsoring agencies haven't existed for continuous monitoring for over two years. It's an example of kind of a a leftover thing from old federal app culture with the jab. And so, like, you don't have a sponsoring agency for continuous monitoring. you have agency customers and are required by the continuous monitoring uh controls to be doing your work with all of your agency customers. Um, okay. Uh there's a couple questions about uh timelines for uh when things are required and it's the same um it's it's like December 7 like you won't we if you are applying for a federant certification and you do that on January 5th and you don't have the VRVER implemented you will not be granted a Fed ramp certification because you have not implemented the rules properly. Um I just add to that Pete, right? Like if you've got a package that's in process, right, and we hit or or you know, you you want to submit on December 8th, the initial package checklist will outline like, hey, where are you on each of the individual um CR26 rules when they when they become um required, right? Um so that that in that checklist, you'll identify where you are, right? So if you just finished your assessment and it's December 8th, clearly we won't expect that in the SSP, but we will expect you to show us um if VDR or VER is implemented. >> Yes. Uh there's a question here. What if vendors we use for performing vol scans are still working on implementing VDR VR themselves? Can a CSP claim vendor dependency for the requirement the vendor would be implementing the BDRE? No. you should switch to a vendor that is providing that capability or um build out yourself. VDRVR is not something you're going to buy from a vendor. So, if you're trying to buy VDRVR from a vendor, you're going about it wrong. It is a cultural shift in the way that you do your uh uh sock and your vulnerability management. It's not just a vendor. And you definitely cannot just say, well, I don't have my vendor doesn't support this, so I'm not going to do it. That that's not going to fly. All right, let's go ahead and um push through a few more pieces. Um we're going to talk through some more details of stuff here. Uh so lots of questions. What is fully implemented? I keep saying the VDR VR must be fully implemented. This means all must and must not requirements have been implemented appropriately. Like full stop, right? If it's a must or a must not, you've done it. You've built it out. Like there's not that many of them. get it done. Uh all should requirements are addressed appropriately. Addressed means you have reviewed it, you have tried to understand it, you have implemented it where appropriate, you have documented valid reasons for not implementing if you haven't. Those reasons might be it's too expensive. It's too it's going to cost me too much money, it's too much risk, something like that. But you need to have that reason documented. um where we're going to ask for you to provide a little bit of information about every single rule. There's around 60 of them I think uh all in for the VDRve. You're going to provide the status for each rule. Is it fully implemented, partially implemented, not implemented, or not applicable, you're going to provide a short explanation of the rule and the reason or risk for not following it if appropriate. So this is when we say short explanations, we're talking about uh a few sentences. We're not looking for massive control paragraphs, right? Um you can just say, you know, uh we have weekly meetings where we assess all the vulnerabilities in a round table with a council of engineers who uh prioritize them one by one, you know, kind of thing like that's the we're not looking for full SSP level of detail. We're looking for an implementation status of detail. Um, if the rules are not fully implemented, you're going to need to provide us with some extra information such as a risk and mitigation information, which is like, okay, you haven't implemented the rule. What is the risk to the customer and what are you doing to mitigate the fact that you haven't implemented it and are there mitigations that customers can put in place? Finally, we'll ask you to share the completion target. Uh, next slide. accepted formats. Uh, as mentioned earlier, we're going to provide templates and schemas and validators. We're even going to give you a web viewer that you can like shove your CSV file or JSON file into and see what it looks like in kind of a pretty uh thing. We're going to make this all available as text. There's gonna be no Excel spreadsheets and no word docs, but you can theoretically edit stuff in Excel and save as CSV or edit stuff in Word and save as markdown. But like uh we're trying to make this really simple so that we can easily go and shove this into our tools to take a look at what you're saying. Again, we're looking for minimum amount of information necessary. All right. Now, uh last slide. some kind of like lots of questions to to come through. I'll catch up on on questions in a second. Um, but public notice and the website will be posted no later than Tuesday next week. There will be examples and facts and stuff added over time. So, it might not have the full content right when it comes out. I want to warn everyone about the examples. Again, they are super intelligence which we're required to call it now. They are super intelligence generated with cursory review. It's intended to illustrate the level of information acceptable. Do not do this like thing where you're like, "Oh, look at the way that that's structured. I should write it just like that." Right? We don't like that. Don't do that. This is just for you to go, okay, like cool. Like seriously, the number of times in Federam's history that an example has become a rule that three PAOs and stuff have been like, "No, you have to implement that way because Fedramp had an example that said that is way too high. So, let's not do that." Other important pro tips. Number one thing, I know this breaks every compliance person's brain. It breaks your brain. I get asked I have I get asked this all the time. People are like, "Well, like what what's the minimum do I need? What do I make?" You look at all this like this is about sharing important risk and security information with your customers. What information do you want your customers to know about your implementation? How how much detail do you want to provide? If you were a customer looking at this, what information do you want? We are leaving it up to you. You can do a terrible job. You can do you can write like some terrible terrible terrible mini SDRs with five you know word sentences and not a lot of information and that and like Fedramp's not going to you know drag you over a barrel for it but probably all of your customers will hate you. So, like balance that out, right? Like it's really important for you to actually think about what you're doing and make sure that it's good, that your customers like it. It can be literally like like life or death for you, right? Like the way that you present this information could be the difference between your service being turned off and your contract being cancelled or not with your agency. So, put some thought and effort into it. Talk to a designer, you know, talk to some folks. Um, don't just treat this as a compliance exercise where you're just filling out something and trying to make it look the same as everybody else's. Finally, just like don't when you're interacting with agencies, if they ask for something else, there's not really any point in you being like, well, Feder didn't ask us for that, so we're not going to provide that for you. I mean, if your customer wants something, you think about whether or not you want to give them that thing. Um, but it's not really helpful for anyone for people to be like, "Well, Federam didn't want this, so I'm not going to provide it for you." Like, take care of your customers. >> All right, let us uh address some questions. Okay, >> I I'll take some here that I got in here. Uh, what is the current backlog for Rev Five packages? What is the estimated review timeline for Rev Five packages? I think we've got 22 in active review as of this morning. And when I pulled metrics last week, I think we were at 34 days average. Now th that time does not include um time where we're waiting on you for documentation or whatever it is, it's only that it's in our active review queue, right? So if we ask you for something and it takes you a month to come back, that month's on you, not on us. U but yeah, 34 is what I think I pulled last week. Um 34 and change. 34.2, I think. Um there was a question around um what if we're not following SCN yet? How do we notify our agency of changes? Um, if you're not following SCN, you're following STR. Um, just a different process with some different timelines. So, roll with that. Um, trying to think, um, there's another question in here that we're we're we have an interesting situation. One of our products has an existing Fed rampert. Another one's not yet certified. Um, we're not sure what is required when it comes to obtain versus maintain. We adjusted wording because uh a few months ago on this um right if you are working to obtain an initial certification right that is the timeline associated with it. So the time that you go through um and you submit your Fed ramp rev 5 certification application form it'll actually ask you where you're at for all um for all CR26 rules and clearly if you have a certification you need to follow the maintain uh certification timeline. There's a question on here earlier you gave a login.gov gov example of a CSP having to comply with FISMA but not Fed ramp requirements. Um I would uh >> it it's um so private businesses are different from government cloud services. There's a few government cloud services and they're they don't they're they're legally already required to meet FSMA requirements as well as everything else A130 all that kind of stuff. It has nothing to do with commercial services at all. This is an entirely different scenario. That's why there will be a type it'll be a type A130 class G certification and is only available if your uh AO your system owner and your are federal employees at an agency and your council agrees that it is formally operated on behalf of the government. So this is things like login.gov, go.gov, cloud.gov, uh USDA connect, stuff like that. It is, you know, if you are an agency provided service, uh, and if there's no 20x related to that. Um, what if we want a SISA red team assessment without being on a cap? Uh, reach out to me. We might be able to make something happen. SISA is always asking us to to red team folks. Um, all right. Is Fedramp ready to ingest the VDR VER information? Yeah, the the VDR VR information is like really basic. We have we'll have no problem uh ingesting some of it and we're not particularly worried about it. There's also human readable versions. Like a general reminder that we always tell people is that the machine readability and automation requirements are intended to build a future ecosystem. They're not something that is just broadly in place at every agency right now. Um, so like DHS, HHS, USDA, some of these big agencies, they're in the process of implementing um, GRC tools to be able to do this, but right now they would expect to be looking at the human readable versions for a while. If we have USDA connect access and implement VDRV prior to implementing the CDS requirements, is this where we upload VDRVER data? Yes, exactly right. Um, and obviously some of those VDR v requirements you can't I think there's one particular requirement about um like uploading stuff every seven days or something like that if you're a class D and I could understand you wouldn't want to do that and you could just do a partial implementation there and do it every 30 days and just explain why and that would be perfectly reasonable. >> Make sure you explain why as part of the SCEN process, right? This way there's always a record in there. Um, also we're not going to create new folders, right? Put it in the POM folder where it belongs. Um, we've got a bunch of extra requests for random one-off folder generation and it's just we're not going to manage that. >> Yeah. Yeah. Uh, there's a question here about automated scan execution and if you're expected to have 247 support to meet uh, incident evaluation and communication procedures. I'm just going to say that depends on your class, but if you're class D and you don't have 27 support, you shouldn't be class D. let me know and we'll we'll to help you downgrade to class C or something because yes, if you are class D, you need to be able to uh call an incident and report on an incident 247. Um in the past when you mentioned CSPs can't make people sign NDAs, did you mean specifically for FedEnt, PMO, GSA or do you mean all agencies? All agencies actually. So it is that a federal employee is not allowed to bind the federal government to an agreement which means federal employees can't sign those things unless it goes through a very complicated long review process. Um on top of that every single federal employee and every single contractor is already under a bunch of laws about having to protect federal information. Uh believe it or not that includes information collected by the federal government. So when I get a copy of your system security plan, the copy that I have is considered federal information and I have to protect it just as much as I would have to protect veterans health data or something like that. So there is unlike industry there is no point in NDAs or government. there's much stricter enforcement already in process if you believe that something and I will actually say I have seen investigations and I have seen people go uh to jail for um sketchy stuff with system security plans um especially when one agency's uh digital data loss protection noted that system security plans are being shipped off uh somewhere so don't like yeah it's different than private sector Uh what happens if our underlying platform provider that we reside on does not meet the deadline for VDRVER? You better hope that they don't get uh their certification revoked. Realistically, I don't think that's going to happen. So, I don't think we need to worry about it. But as their customer, you should certainly be asking your platform infrastructure providers what their status is. and they should be sharing that with you as a good customer experience, right? Um so in a in a world where they're in remediation, that's fine. You're not going to inherit their in remediation, but it may affect um whether or not an agency wants to use your product as long as your infrastructure provider is in remediation. That's perfectly reasonable. if they get their uh their Feder app certification revoked, then we'll have to come talk to everyone built on that platform to talk about opportunities and risk. I think to be honest, I did not expect that that would happen. Um so if it does happen, it'll be messy, but it shouldn't happen. There's no reason for that to happen. Uh, can we go back to the VER VDR significant changes thing? We're not requiring 3PO assessment. SCM may not be implemented yet. What are the practical consequences of this? Just work with your agencies and figure it out. So, implementing the VER and the V implementing many of the rules within the VDR and the VER does not require significant changes. implementing some of the rules may require implementing significant changes. Most of those, depending on how you implement it, should be adaptive changes at the most and not really transformative changes, unless you're really, really, really just like doing things an entirely different way. The 3PAO assessment is not needed if you have a transformative change that you can't review the um security impacts of. When you do these changes and you implement these, what you can do is write down what you're doing, put the risk in there and document that and then that's sufficient for for this scenario. There's you don't need permission. um etc. If you're still doing SCRs for some reason, then you need to then coordinate that with all of your agencies doing collaborative conmon who are doing your STR approvals. That's obviously going to be a lot of work. We would recommend that you take that approach by just simply telling them that you are doing an STR and it's going to happen on this date and that they should speak now or forever hold their peace if they have concerns with it. And I don't think any of them will have concerns with it. So approval by fiat of um you know not having anyone deny it is the most efficient way to do that. Uh, I'm I'm just going to say I'm mildly concerned that people are still asking those questions in November because that implies that they haven't already thought through and worked with their agencies to implement this thing and you do not have much time left. So, please start doing that. And when you inevitably submit a corrective action plan, make sure that you have the way that you intend to make those changes thought through and coordinated. Uh, oh, I love this question. We're following the current SDR schema and written rules to document the VDRVER rule set implementation. Would that be good for what you mentioned? Uh, what you ask what you're going to ask for. We are asking for something that is a little bit less detailed than is in the SDR U because we want to make it easy and and chill. So, you should be able to generate what we want for the mini SDR from what you're doing in the SDR. So, you shouldn't lose any work. Um, but yes, uh, you don't you didn't want to make everyone do a full SDR style approach because it's a lot more complicated. It requires like five or six, uh, things and, um, we're not requiring that full depth. Wow, lots of questions about this. If our sponsor does not require an SCN, uh, this is these are very confusing when you get these questions. You don't have a sponsor, you have agency customers, you work with your agency customers to make changes. Um, it is absolutely okay with Fed Ramp. Sorry, let me read the rest of the question. If our sponsor does not require an SCN when we switch to the VR VDR process, but a simple transition notification we start using, is that okay with Fed Ramp or do we need to submit evidence of an official SCEN? It is totally okay for you to switch this stuff um over. I think that realistically you should have an SCEN, but it's like you should have that anyway, right? Like that's just like you you have a change ticket somewhere tracked. So you should do an SCN and make that change over and have that be clean. Fed 20X class A. I'm going to ignore this. Sorry Omar. This is Feder Rev 5. Um and I think this is related to 20X2. So I'm going to also skip that one. um question. Somebody would like to set up a meeting to discuss their situation. Um you can send an email to info@fedm.gov and we don't usually meet with cloud service providers to talk through how to implement the rules and stuff like that. Um because that's a lot of complexity, but if you reach out to info, we can certainly go back and forth over email to help you work through that. Oh, we have a rule specific question, which means I'm going to have to pick look up the rule. All right. Can you elaborate on VDR TFR PSD persistent sample detection? Is the class C 3-day and class D daily requirement only if sampling is implemented? A May rule? Uh, no. This is those are two different rules. The the you you should do sampling uh on these timelines and then there's another rule that says that you should do sampling in general. Those are those are two. you you if you were to think of should as like a must if you're doing things right you are constantly sampling resources on on a day-to-day basis for your wider VDR which is VDR cso sir you are encouraged and may do sampling for other resources so what that means is uh for the detection that you do if you've got a thousand containers and they're all the same they're all deployed with the same hash you only need to look at one of them you don't need to look at a thousand of because they're all the same. That's sampling. That's acceptable. That's different from being forced to sample and do detection every day or three days, etc. Um, okay. Where is Azure, GCP, and AWS stand on this front? They are the major three service providers that most everyone here is housed in. I'm not going to speak for a private commercial business and their um commercial processes. So will the mini SDR be the formatlanding place for the detail we'll provide for our implementation with each VER VDR rule? Will the sample vulnerability report JSON files be provided? Yes, the website will provide examples and explanations. Um and yes, the examples will also be in CSV and JSON. That's the advantage of using super intelligence. Um, does changing and implementing a new GRC tool qualify as a SCEN event? That depends on the situation. Cloud services vary considerably. A GRC tool can be used to do many, many, many different things. Follow the SCN categorization process to determine if it's an SCN for you. Last question coming in here. Since VDR, oh no, more questions popping in. All right. Since VDR and VR are primarily internal processes, do we need to ensure that all relevant data and findings are consolidated in one central location for tracking, reporting, and compliance purposes? Do the right thing for your business on your implementation here. Um, it doesn't necessarily mean that everything would be in the same place. Uh a lot of businesses will have things like um you know your security scanning information would be in one place and that will trigger a ticket that would get created over to product development in a different place and then they would go through and work that ticket and deploy code using u information in a different place and in that case it wouldn't make sense for it all to be in the same place. Uh so don't overindex on things being in the same place. just uh talk with your engineering team about how they handle and manage this and tap into the systems that they already are using. Okay, couple more questions. Should CSPs care or be responsible for agency adoption if we are using a GRC platform that can support traditional POM conmon and CR26 VDR VER reporting simultaneously? If I understand this question correctly, I would say the coolest thing you could possibly do right now uh would be to continue to provide traditional POM conmon alongside CR26 VDR VER reports. I think that would be great. I think that there's a lot of capability to do both those things side by side and it's helpful and comfortable for people to see the difference. Uh we don't require that. Some of your customers might want that. So, it would be a great customer experience to do that if they do. Um, how much version history is required to be in the data like last 30 days? Uh, the rules kind of go into that. It's um in a couple different rules. I don't have it off top of my head, so I'm not going to answer that here, but you can always go back to the rules for that. Um, all right. If you are successfully operating a traditional Rev 5 Conmon program as a Feder certified provider, how would you describe egregious security issues? I'm not 100% sure what this means. I think it maybe is like my comment earlier that um doing monthly vulnerability scanning and then uh fixing vulnerabilities over the the course of like a 30-day window. That's egregious security issues. I think like a good example of what we saw last week with PHP to shell is is this right? Like did anyone on this call be like, "Oh, I've got 30 days to fix my PHP." if you did, your security sucks. But that's what Federam required, right? And so you could be like, well, Feder just like required it to be 30 days, so like I'm just going to leave this thing out on the internet and get popped day after day after day after day. Um, like that's ridiculous. Don't don't do that. And so the new rules are designed to be more enforcing that you have to actually respond to egregious security events. have to respond to high-risisk security events. That is important. The flip side of that is that we are saying and CISA is saying you do not need to prioritize these janky unimportant things buried deep in your infrastructure that show up on scans that will have no likely impact on anything. Um, SISA said when they were testing this with agencies, they found that more than 90% of the vulnerabilities that were tracked were unimportant and could just be held off into like the next time that they did a patch. Whereas under the the previous rule, all of those vulnerabilities would have then had to fix in like 30 or 60 days. And so that's the whole point of doing riskbased vulnerability detection response. Um, and yes, if you just followed scanning and implementing like when you got around to stuff, it was it was not good security. All right, more questions coming in. Uh, we're coming up on near time and I feel like people are probably sick of me just like running off these questions. So, I'm going to do the ones that are in here and then we'll we'll stop doing any bumps down. Is that saying you are sick? You are sick of me. I don't know what it means. Thank you, Ben. With the new IEC rule sets, are the CSPs still required to report security instance to USERTT or is that strictly an agency thing now based off information? Yeah. So, under the IEC, the theory is that the cloud service provider, you don't if you get popped and some agency information gets taken, you don't know what that effect is on the government nine nine out of 10en times. So, you shouldn't be reporting that to the government. that agency should be reporting that to CISA cert etc. So the expectation is that this those the agencies when they get a notification from you that there's an incident that they follow incident reporting guidelines based on that. That should make things a lot more clear, a lot more accurate, uh, you know, and reasonable, but it makes the the incident communication so much more important from cloud services because the agency needs to get that in a timely manner and then respond to that and uh, notify other parties as needed. Um, something about KSIS which is not ref five. Ah, this is a good question. Are we expected to move any historical closed poems over into our VER VDR reports or can those simply live in our poem archive if needed for reference? Uh you totally do not have to move over historical stuff. Uh that is not expected. Uh whenever you implement a VRVR, you start from there. Um, but if you have open ones like 100% and in fact my guess is that a lot of cloud service providers are going to end up with a really big list of accepted weaknesses on day one because you have a lot of poems that were open for more than 192 days. Um, so that should be really interesting to see. But yes, you don't have to translate your historical ones, but if you have open ones, those should get moved over. Um, can you compare and contrast CISAB 2604 versus VDRVER? Do you see major differences? Um, so there's a lot to 2604 versus the VDR VER. Um the 2604 is primarily focused on kevs and on um timelines that are designed to force government to uh have a lot of complicated situations right there's like I think 30 different you you guys think our pain levels are complicated right this is sis lookup tables like 30 different things right in different ways um we had already published and finalized the VDR and the VER when BAD 2604 was published. So we collaborated with CISA to ask if we needed to change it to enforce the exact like 3D complicated thing that they had set up and they were very happy with what we had done with the VRV already and because you're commercial companies and not uh government cloud services they agreed to uh just forcing you to implement the VR VER to maintain a federant certification. So they are very different. The VDRVR is designed to generally allow you allow a cloud service to operate the way that a commercial cloud service handles um security vulnerabilities. So you know every in my experience when I uh was in private sector the first thing that you do when a vulnerability pops somewhere on a scan is you sit down with your engineers and evaluate it to figure out if it matters or not. and nine times out of 10 you're just like yeah okay whatever delete this like we'll fix it when we do an OS upgrade next you know quarter or something like that. Um so we wanted to enable folks to be able to do that. That's why the VRVR was done in advance. The other side is that we're focusing not on like the old way was like any vulnerability in your infrastructure you have to report on. The new way is any vulnerability that's likely that has likely potential impact on your agency customers. So if you got vulnerabilities that aren't going to likely impact agency customers, we don't care about them. You don't have to tell us about them. You don't have to track them like all this way. Just handle those on your own. This is very much intended to provide assurance for government customers that you're doing a good job. I think if I I'll just maybe this is like a good way to close out this meeting. Uh personally my goals long long long term would be to be able to move us away from this level of in-depth vulnerability reporting to the government customers. And I would love to be able to just have uh companies kind of summarizing their vulnerability information and just to to demonstrate that they take it seriously and not, you know, producing things that are like, you know, this CVE is on this server and stuff like that because that information is just not necessary or helpful uh for your your government customers to have and it creates a huge burden across the way. So one day uh down the road maybe CR27 maybe CR28 we hope the BDR to be even uh less and really just focus on you know methodology and wide widescale reporting. We'll see if it works. All right everyone, thanks for coming in today. Sorry to whoever's question just came into the Q&A. You got there a little bit too late. Uh as always, GitHub, our GitHub community is open all the time. We're seeing a lot more activity in there. If you haven't checked it out recently, go check it out. There's a ton of Q&A about the VDR in there and we'll be summarizing on our website and keep an eye out for our notice next week. We'll see everybody soon.

Watch and share

Watch it on YouTube

Share this page:LinkedInXEmail

Required agency actions

FedXchange has not recorded this document's agency actions yet.

Tell us what this document requires of agencies

What FedXchange has recorded

  1. FedRAMP posted a video: FedRAMP Rev5 Community Update.

Report a change or a mistake on this page

Issuer
General Services Administration (GSA), including the Federal Risk and Authorization Management Program (FedRAMP)
Type
FedRAMP video
Issued
November 4, 2026
Status
Published

A video or notice that explains a rule or process. It sets no rule by itself.

Get new governance by email

A weekly email on Fridays, an alert on the day the watch finds something new, or both. Free.

Send me
About

We use your address only to send what you choose, and every email has a one-click unsubscribe. Read the privacy notice.