Skip to content
‹ Back to IndustriesSoftware & Technology

550+ FedRAMP cloud services must rethink how they rank flaws

FedRAMP requires more than 550 certified cloud services to adopt new vulnerability rules by Dec. 7, prioritizing flaws by internet reachability and exploitability. Corrective action plans can extend remediation until March 7, 2027. Many vendors are shopping for new tools, but the shift can require broader engineering changes beyond a scanner swap.

This story was produced through MarketScale. See how Software & Technology teams put it to work with Executive Thought Leadership.

By MarketScale Newsroom · FedrampVdr and Ver RulesVulnerability ManagementCisa Binding Operational Directive
Share
550+ FedRAMP cloud services must rethink how they rank flaws

Key takeaways

01

A high-severity bug walled off from the internet can now wait its turn, while a reachable, exploitable one moves to the front of the patch queue at more than 550 FedRAMP cloud services.

02

Reachability depends on how each environment is built, so vendors whose current scanning tools can't rank flaws by exposure face an engineering decision before March 7, 2027, and a simple purchase may not settle it.

Free workspace

Turn your Software & Technology expertise into content.

Record interviews, organize footage, and write with AI on a free trial of the MarketScale platform for qualifying companies. No demo required, no credit card.

Try it Free

More than 550 cloud services hold FedRAMP certification, and every one of them has until Dec. 7 to change how it finds, ranks and reports software flaws. The General Services Administration's cloud security program is moving them onto two new rule sets, Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER), Federal News Network's Justin Doubleday reported on Nov. 13.

Services that can't finish in time may file corrective action plans for the requirements they miss. Ignoring the deadline is a different matter. In a Nov. 10 notice, FedRAMP said any service that hasn't fully migrated and isn't working under an approved plan by March 8, 2027, will lose its certification and be barred from the program for a year.

That puts the change on two desks at once: the security and compliance teams inside cloud vendors, who have weeks to rebuild a core process, and the agency IT leaders who depend on those services staying certified. The useful question is what the new process actually asks for, and why so many vendors are finding that their current tools can't supply it.

Sorting the patch queue by exposure

The legacy routine was familiar. Scan monthly, line the findings up against vulnerability severity scores, patch in that order. FedRAMP's new rules call for a move away from that legacy scanning toward what the program calls an exposure and threat-based approach. Providers now have to judge whether a vulnerability is likely reachable over the internet and how far it can actually be exploited.

On Federal News Network's Federal Drive, Doubleday walked through what that means in practice. An internet-accessible flaw rises in priority. A flaw with a high severity score that is cordoned off from the internet drops, because it is less likely to be exploited. A high-severity bug walled off from the internet can now wait its turn, while a reachable, exploitable one jumps the queue at more than 550 FedRAMP cloud services.

The logic mirrors the binding operational directive CISA issued to federal agencies this summer, which tells them to patch the vulnerabilities that pose higher risk to their operations and networks first and defer lower-risk bugs, rather than rely only on uniform patch deadlines. With FedRAMP following suit, agencies and the vendors hosting their workloads now sort vulnerabilities by the same rule.

What changes in practice: under the legacy FedRAMP rules, a severity score largely set a flaw's place in line. Under VDR and VER, the score is still an input, but two questions decide priority: is the vulnerable software likely reachable from the internet, and how exploitable is it?

FedRAMP's stated reason for moving so fast is that AI is helping attackers go after unpatched bugs more quickly. The Nov. 10 notice said the threat that justified the deadline five months ago has only grown, and pointed to Black October, the name the security community gave to last month's run of AI-driven vulnerability disclosures. Doubleday described October as a month when new vulnerabilities and exploits poured in, many of them AI-generated, with little clarity about which ones actually worked. That detail suggests why reachability works as a filter. When claimed exploits pile up faster than anyone can verify them, asking whether a flaw can be reached at all tells a team where to look first.

Four dates between now and March

Enforcement starts before the deadline does. FedRAMP has laid out a sequence that begins with a simple test of whether vendors are paying attention:

  1. Early December: FedRAMP runs its first quarterly security inbox emergency test, emailing certified services for progress reports on their adoption of the new processes.
  2. Dec. 7: All certified services are directed to migrate to VDR and VER, or file corrective action plans for the requirements they can't yet meet.
  3. March 7, 2027: The three-month grace period ends.
  4. March 8, 2027: Services that have neither migrated nor begun work under an approved plan face revocation and a one-year ban.

The inbox test is part of the same push, and FedRAMP expects every authorized service to answer when the program reaches out. Doubleday's reading of FedRAMP's message to vendors was plain: follow the rules and stay engaged with the program.

So the first thing FedRAMP checks is whether anyone at the vendor answers the email. That's an editorial read, but a practical one: confirming who monitors the security inbox FedRAMP has on file costs nothing and avoids a 30-day public timeout.

The schedule is softer than the revocation language makes it sound. FedRAMP wrote that its primary concern is getting certified providers migrated swiftly, safely and appropriately, and that it won't take unnecessary administrative action against services working safely and in good faith. Vendors still short of full compliance on March 7 will keep working with the program in remediation status under corrective action plans, Doubleday said. The ban is aimed at services that neither migrate nor engage.

Why a new scanner may not be enough

Matt Bruggeman, director of go-to-market federal at A-LIGN, which helps cloud providers meet requirements like these, called the shift a "drastic change" in an interview with Federal News Network. Many vendors are turning to third-party tooling. Plenty already had scanning tools, he said, but a lot of those tool providers can't meet the new requirements, so vendors are shopping for replacements. He described the overall effort as a substantial amount of work.

The tooling gap points to something deeper. Many providers built government-specific versions of their clouds and tuned vulnerability management to the legacy monthly-scan model, Doubleday noted, and how hard the shift is depends on how those environments were built. A severity score comes attached to the vulnerability. Reachability doesn't. It belongs to the environment, which is why Federal News Network framed the rules as a broader engineering challenge for some vendors than a tool upgrade.

The providers likely to feel it first are those whose government environments were designed around the old scan-and-score routine. A provider that already keeps an accurate picture of what in its environment faces the internet would probably have a smaller lift, since the reachability judgment rests on exactly that picture. For everyone else, choosing a tool and changing the environment around it are the same project.

Budgeting for the next migration

FedRAMP's notice told vendors to expect more. Providers need enough budget, planning and engineering capability for continuous operational improvements, it said, and must be able to show federal customers they are meeting changing expectations for automated assurance in the coming years. The VDR and VER migration is the first of many, according to the notice, which added that yearly paperwork exercises are "no longer appropriate or sufficient" for continuously evolving threats.

That fits the program's FedRAMP 20X initiative, which is moving toward automated, real-time security monitoring and away from large authorization document packages. Bruggeman tied the vulnerability rules to the same shift: FedRAMP wants to see a provider's security at any given moment, plus a history of it, without leaning on a report that's 10 months old.

For a vendor's finance and security leads, this means the Dec. 7 spending is likely the first payment in a series. A tool bought only to clear this deadline would be a poor fit if the next migration asks for automated evidence it can't produce.

Before signing with a new vulnerability tool, ask two things: can it record each finding's internet reachability and exploitability, and can it keep a time-stamped history of those judgments? The first is what VDR and VER require now. The second is where FedRAMP 20X is heading.

For agency buyers, the signal is public. Any service placed in remediation status shows up on the FedRAMP marketplace, and the early December inbox test, landing days before the Dec. 7 deadline, will be the first read on how many of the 550-plus services are on track.

Featured companies

Your experts belong here

Every story in MarketScale Software & Technology starts with a company putting its solutions engineers, product teams, and customer engineers on the record. Buyers are already reading this topic. The only question is whose experts they find.

Buyers ask AI engines who to consider, and published expert answers are what those engines cite.

Book DemoSee how it works15 minutes, straight to a calendar.

About the author

MarketScale Newsroom
MarketScale NewsroomEditorial Team, MarketScale

The MarketScale Newsroom reports on the companies, technologies, and trends shaping 16 B2B industries. It turns primary sources and expert commentary into clear, useful coverage for the people doing the work.

B2B Weekly

The week in Software & Technology, and sixteen other industries, every Monday.

Ten stories, one-line takes, five minutes. Free.

Software & Technology: are you visible to AI?

Before they reach out, Software & Technology buyers ask AI engines which vendors to trust. Explore how your experts, customers, and partners can become useful content for buyers and AI search.

Free Trial

You just read one Software & Technology expert. Your company is full of them.

This article was produced through MarketScale. The same platform turns your solutions engineers, product teams, and customer engineers into the articles, video, and social content Software & Technology buyers are searching for. Start a free trial and see it with your own people. For qualifying companies, no credit card, no demo required.

NPS +73 · 1,000+ creators · 38+ countries

What your free trial includes

Hands-on access to the MarketScale platform
Media requests to your crowd, remote recording, AI writing tools
No demo required. No credit card.
For qualifying companies. Company confirmation required.

More Software & Technology Insights

55% of enterprises plan to own part of their AI infrastructure, research finds

55% of enterprises plan to own part of their AI infrastructure, research finds

Commissioned research finds 55% of enterprises plan to own at least part of their AI infrastructure, a choice the article links to control concerns in regulated sectors. For organisations that own the hardware, power and cooling demands can shift onto the facility. Respondents’ top rollout hurdles were scaling AI IT clusters, cost, and sourcing power and cooling infrastructure.

  • 0155% of enterprises plan to own at least part of their AI infrastructure, motivated by control over data, privacy, and compliance in regulated sectors like healthcare, finance, and government.
  • 02Three hurdles block AI deployment at nearly equal rates: scaling clusters (27%), cost (25%), and power and cooling sourcing (22%), with no single obstacle dominating.
  • 03More than half of enterprises say fewer than one in five AI proofs of concept reach production, delayed by lack of in-house expertise (33%) and integration complexity (32%).

Nov 20, 2026

CloudWatch Omni rollouts are decided before the first team signs in

CloudWatch Omni rollouts are decided before the first team signs in

Amazon CloudWatch Omni puts application and AI agent observability behind one sign-in URL. Its key setup choices are hard to undo: the domain stays in the IAM Identity Center primary Region and centralization rules skip historical data. According to AWS, Omni does not automatically detect or redact personally identifiable information, and no data is removed unless you configure it.

  • 01Omni centralization rules capture only telemetry that arrives after they are created, so the date the rules go live sets how far back incident teams can look.
  • 02Omni does not detect or redact personal data on its own; capture-time redaction is the only layer that meets the requirement that data never be exported and it cannot be reversed.
  • 03Organizations with data residency rules should settle their IAM Identity Center primary Region before creating the Omni domain, because the domain has to stay in that Region.

Nov 19, 2026

ServiceNow wants AI agents to chase the unpaid invoices too small for staff

ServiceNow wants AI agents to chase the unpaid invoices too small for staff

ServiceNow's EmployeeWorks reached $100 million in its first three quarters, and the company is now aiming AI agents at accounts payable and receivable. Kahn suggested a volume-priced AP agent could end up compared with outsourced AP contracts as much as other software. Finance teams will mostly meet these tools through existing ServiceNow contracts, and the strongest benchmarks still come from IT, where Leidos expects up to 60% of tickets resolved with no human involved.

  • 01For now, ServiceNow's autonomous finance tools are selling mostly to existing ServiceNow customers, so the first accounts payable agent many finance teams evaluate will arrive through a platform the company already pays for.
  • 02AP and AR agents can be judged on before-and-after finance metrics—duplicate invoices caught, discounts captured and days sales outstanding—rather than broad productivity claims.
  • 03ServiceNow estimates that 10% to 20% of revenue in its Core Business unit may involve hands-on engineering help, a reason to price implementation work into complex finance projects up front.

Nov 18, 2026

Explore More Software & Technology Insights

Read more expert perspectives from across Software & Technology.

Browse Software & Technology Hub

About the Expert

MarketScale Newsroom
MarketScale Newsroom

Editorial Team

MarketScale

The MarketScale Newsroom reports on the companies, technologies, and trends shaping 16 B2B industries. It turns primary sources and expert commentary into clear, useful coverage for the people doing the work.

For B2B teams

Your experts could be publishing here

Stories like this one run on content MarketScale captures from real practitioners. See how your team's expertise becomes coverage in Software & Technology and beyond.

Book a Demo

Or call us. No forms required. We pick up. 214-945-2512