Skip to content

Blog

FedRAMP's February 2026 Rev5 update: review times, continuous monitoring audits, the security inbox, and secure configuration

At its February 4, 2026 Rev5 Community Update, FedRAMP reported a 28.75-day average review time against a 30-day target, began flagging inactive continuous monitoring folders, and reminded providers of the security inbox and secure configuration requirements.

By FedXchange ·

Play the video: FedRAMP Rev5 Community Update (formerly known as the FedRAMP Rev5 Working Group)
FedRAMP's video, on its governance tracker page. The player loads from YouTube only when you press play.

The Federal Risk and Authorization Management Program (FedRAMP) held its monthly Rev5 Community Update on February 4, 2026. Rev5 is FedRAMP's older certification process. At the time, FedRAMP still called its approval a FedRAMP authorization. In Notice 0004, published February 25, 2026, FedRAMP said it will use one label, FedRAMP Certification. The FedRAMP Consolidated Rules for 2026 (CR26) use that current term.

In short:

  • Review times. FedRAMP said it will publish its Rev5 review times every quarter. The target is 30 days from a complete package to a decision. For Q1 2026, FedRAMP reported a 28.75-day average.
  • Continuous monitoring audits. FedRAMP began flagging continuous monitoring (ConMon) folders with 60 or more days of inactivity. About 82 of more than 490 services were flagged. Providers would hear from FedRAMP by email.
  • Security inbox. The security inbox requirements took effect on January 5, 2026. Every provider must keep, and answer, the security contact email FedRAMP has on file.
  • Secure configuration. FedRAMP's rules list March 1, 2026 for this requirement, and July 1, 2026 as the last date for existing providers. FedRAMP asked providers to write guides for the federal tenant their agency customers use.
  • Requests for comment. FedRAMP asked for formal comments on its six open requests for comment (RFCs).
Rev5 review time in Q1 2026, as FedRAMP reported it
0102030Calendar days, Target: 30 calendar days30TargetCalendar days, Q1 2026 average: 28.8 calendar days28.8Q1 2026 averageCalendar days, Q1 2026, shutdown days removed: 21 calendar days21Q1 2026, shutdown daysremoved

Source: FedRAMP Rev5 Community Update, February 4, 2026. A speaker said the third value is "about 21 days" once the 45 days of the shutdown are taken out.

Show the numbers
Calendar days
Target30
Q1 2026 average28.8
Q1 2026, shutdown days removed21

How long does a FedRAMP review take?

A FedRAMP speaker said RFC-0020, FedRAMP Authorization Designations, describes the review target. RFC-0020 was a proposal at the time. In the video's words: "30 days is the target." The clock runs from the point FedRAMP has a complete package to its decision. RFC-0020 says the target is "less than 30 days if the package is truly complete."

The speaker said the Q1 2026 average was 28.75 days. In the video's words: "Those are calendar days not business days." The speaker added that there were 45 days of shutdown when FedRAMP could not make decisions, so the average without them is a little over 21 days. FedRAMP will now report these times every quarter.

What are the new continuous monitoring audits?

The speaker said OMB Memorandum M-24-15 requires FedRAMP to give a standard level of continuous monitoring support. The Joint Authorization Board (JAB) process, which once gave its systems a monthly review, is gone. So FedRAMP began working with the Department of Agriculture (USDA) and its Connect.gov data analytics team.

How FedRAMP said it would handle a flagged continuous monitoring folder
1Automated checkQueries look for 60 or more days of inactivity in Connect.govcontinuous monitoring folders.2Manual reviewFedRAMP staff review every flagged folder by hand.3Administrative flagWrong file format or wrong folder: a non-punitive email with generalsteps to fix it.4Inactivity flagAn email asking for a written reply: the issues, the fixes, and atimeline.5RepeatFedRAMP plans to run the checks again, quarterly or monthly.

Source: FedRAMP Rev5 Community Update, February 4, 2026.

Read the steps as text
  1. Automated check. Queries look for 60 or more days of inactivity in Connect.gov continuous monitoring folders.
  2. Manual review. FedRAMP staff review every flagged folder by hand.
  3. Administrative flag. Wrong file format or wrong folder: a non-punitive email with general steps to fix it.
  4. Inactivity flag. An email asking for a written reply: the issues, the fixes, and a timeline.
  5. Repeat. FedRAMP plans to run the checks again, quarterly or monthly.

The speaker said about 82 of more than 490 services were flagged. About half were administrative problems, such as a file in a format other than the template. The other half showed real inactivity. FedRAMP would email providers at the provider email on the Marketplace, through February.

The speaker said a provider that keeps its authorization must still keep up its continuous monitoring, even when its agency customers lose staff. In the question period, speakers said the first check did not cover annual assessments, and that FedRAMP was not auditing High packages, which are not in Connect.gov.

What must providers do about the security inbox?

A speaker said the requirements responded to Cybersecurity and Infrastructure Security Agency (CISA) emergency directives, because many FedRAMP emails to listed security contacts bounced. Notice 0003 says the requirements "are mandatory and went into effect on January 5, 2026." CR26 now calls them Addressing FedRAMP Communication.

The speaker described the first test as informational. In the video's words: "We are very chill about this test." Later tests may be quarterly, with adverse actions for providers that do not respond. The speaker's request: "So please just respond to us when we send you an email." FedRAMP ran the test on March 9, 2026, with 635 cloud service offerings, and reported an 80% overall response rate.

What should a secure configuration guide cover?

A speaker said the secure configuration requirement takes effect in March. The CR26 Secure Configuration Guide rules list March 1, 2026, with a grace period that ended July 1, 2026. The speaker asked providers to "please make it relevant to the specific federal tenant," since help pages often describe commercial features. In the question period, a speaker said of the guide: "It is not an internal only thing." It is for customers.

What else did FedRAMP say about the RFCs?

Speakers said FedRAMP can use only formal comments, not social media posts or hallway talk. FedRAMP set up an informal board for questions. On FedRAMP Ready, a speaker said "a proposed RFC is a request for comment on proposed changes." RFC-0023 proposed ending new FedRAMP Ready submissions after July 28, 2026. Notice 0008 later confirmed that date.

Sources

Share this post:LinkedInXEmail

Get new posts and federal 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.