Diligent Logo
Diligent Logo
Products
arrow_drop_down
Solutions
arrow_drop_down
Resources
arrow_drop_down
Diligent AI

FedRAMP 20x explained: KSIs, vulnerability management and continuous compliance

November 11, 2026
•
7 min read
FedRAMP 20x boardroom meeting
The Diligent team

The Diligent team

GRC trends and insights

FedRAMP 20x is the first significant modernization of the Federal Risk and Authorization Management Program in over a decade. The program isn't being replaced. It's being updated to reflect how cloud services actually work and what continuous security oversight now requires.

The core shift is from static documentation and point-in-time assessments toward continuous validation, real-time data and risk-based decision-making.

For cloud service providers (CSPs), federal contractors and the GRC platforms they rely on, that shift has practical consequences at every layer of the compliance program.

Here's what's changing, what it looks like in practice and what it means for your organization.

What is FedRAMP 20x?

FedRAMP 20x introduces four interconnected changes to how compliance is demonstrated and maintained:

  • Key Security Indicators (KSIs): Machine-readable metrics that replace static artifact submissions as the primary evidence of compliance
  • Risk-based vulnerability management: Remediation timelines tied to actual risk and exploitability, not scanner ratings alone
  • VDR and VER: Continuous, per-finding vulnerability workflows that replace the monthly Plan of Action and Milestones (POA&M)
  • Significant Change Notifications (SCNs): A standardized, more predictable process for reporting and reviewing system changes

Each change points in the same direction: Compliance as a continuous operational discipline, not a periodic exercise.

1. Key Security Indicators (KSIs)

What's changing: In the past, proving compliance meant submitting artifacts: Screenshots, policies and narrative descriptions. Under 20x, compliance hinges on machine-readable metrics that provide real-time validation instead of static evidence.

What it looks like in practice: Previously, to show that multi-factor authentication (MFA) was in place, you might have uploaded a screenshot of your identity provider settings and a copy of your access policy. With KSIs, you need to demonstrate through automated data feeds how many active accounts exist, how many have MFA enabled and where exceptions remain.

Impact: This doesn't eliminate the need for policies or oversight, but it fundamentally changes how compliance is proven. Organizations need tools that generate data at the right level of detail and GRC platforms that can ingest and analyze that data in real time. Continuous monitoring becomes the standard expectation, not an optional enhancement.

2. Risk-based vulnerability management

What's changing: Remediation timelines are no longer one-size-fits-all. Critical vulnerabilities carry shorter deadlines, while other findings may be assigned more flexible windows depending on context and exploitability.

What it looks like in practice: A scanner flags 200 vulnerabilities. Under the old model, "highs" had to be closed in 30 days and "moderates" in 90, regardless of where they sat or whether they were realistically exploitable.

Under 20x:

  • An internet-facing flaw with a known exploit must be closed quickly
  • A high-severity issue behind two layers of authentication may have a longer remediation window

Impact: The total workload isn't reduced. Every vulnerability still has to be addressed. What changes is that timelines are now tied to actual risk rather than scanner ratings alone. That allows teams to move faster on what matters most. The challenge is proving — with evidence — that prioritization decisions are defensible.

3. VDR and VER: Continuous vulnerability workflows

What's changing: Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) replace the traditional monthly POA&M cycle with a continuous, per-finding workflow. Every vulnerability is evaluated within days of detection; every output is machine-readable.

Where risk-based remediation changes how vulnerabilities are prioritized, VDR and VER change how they're tracked and reported: Continuously and automatically, with structured outputs rather than monthly snapshots.

What it looks like in practice: Under the old POA&M model, teams would compile open findings, track remediation status and submit a report on a fixed monthly schedule. Under VDR and VER, each finding enters a structured workflow from the moment it's detected, evaluated against risk context, assigned to a remediation owner and tracked continuously until closed. The outputs are machine-readable, designed for automated ingestion rather than manual review.

Impact: This is a workflow change as much as a technical one. Teams that have relied on monthly POA&M cycles need to move to a continuous process. GRC platforms that can't ingest vulnerability data continuously and surface it in a structured format create a bottleneck at exactly the point the program demands speed.

4. Significant Change Notifications (SCNs)

What's changing: SCNs are being reworked to bring more structure and predictability to how system changes are reported and reviewed. The goal is to reduce ambiguity while maintaining oversight.

What it looks like in practice: Today, adding a new system component or changing your authorization boundary often triggers lengthy back-and-forths with an agency sponsor. Under 20x, the SCN process is standardized, with clearer definitions of what counts as "significant" and more consistent handling of reviews.

Impact: This doesn't remove scrutiny. Agencies still want to understand how changes affect your security posture. A more structured SCN process means fewer delays, less confusion and a smoother path for organizations making necessary updates to their environments.

What FedRAMP 20x means for your organization

These changes share a common thread: FedRAMP 20x raises the operational bar. Organizations need platforms that can:

  • Aggregate data across dozens of tools
  • Normalize it into evidence that maps to KSIs
  • Support continuous vulnerability workflows for VDR and VER
  • Surface compliance status in real time
  • Handle structured processes like SCNs without derailing operations

Not every GRC platform is built for that scale, and not every stack can feed data at the depth required. That's where the platform you use, and the partners behind it, matter.

How FedRAMP 20x has rolled out

FedRAMP 20x has been rolling out in phases since early 2025. Here's how the program has progressed:

  • March 2025: FedRAMP 20x officially announced by GSA
  • August 2025: Authorization Data Sharing Standard released; FedRAMP 20x Low Authorization Standard published
  • September 2025: Continuous Vulnerability Management Standard introduced; Key Security Indicators finalized for FedRAMP Moderate
  • October 2025: Continuous Validation Standard and updated POA&M guidance released
  • November 2025: Moderate-level pilot submissions open
  • December 2025: Final FedRAMP 20x Moderate Authorization Standard published
  • 2026 onwards: VDR and VER requirements introduced for Rev5-authorized providers; phased adoption of 20x across Moderate and High authorizations continues

The direction is consistent across every phase: Compliance programs built on continuous data, automated evidence and structured workflows, not periodic reviews and static documentation.

Building a FedRAMP program for the long term

FedRAMP 20x doesn't change the mission: Protecting federal data in the cloud. What it changes is what proof of that protection looks like.

For organizations building or maintaining a FedRAMP program, the practical implications run deep: From the tools your security team uses to generate data, to how your GRC platform ingests and surfaces it, to whether your vulnerability workflows can run continuously rather than on a monthly cycle.

The organizations managing this well aren't treating 20x as a one-time transition. They're building the infrastructure and processes that make continuous compliance a standard operating capability — something that runs alongside the work, not in spite of it.

Explore Diligent's FedRAMP-authorized solutions and speak to our team about what a continuous FedRAMP program looks like in practice.

FedRAMP 20x FAQs

What is FedRAMP 20x? FedRAMP 20x is the first major modernization of the Federal Risk and Authorization Management Program in over a decade. It introduces automation, real-time monitoring and risk-based prioritization to streamline how cloud service providers achieve and maintain compliance.

What is the difference between FedRAMP and FedRAMP 20x? Traditional FedRAMP relied on static documentation and point-in-time assessments. FedRAMP 20x shifts to continuous validation using Key Security Indicators, automated evidence and structured change management. The goal is faster authorizations, lower costs and stronger security outcomes.

Why is FedRAMP being updated? The legacy FedRAMP model was slow, expensive and difficult to scale. FedRAMP 20x responds to years of feedback from agencies and CSPs, aiming to reduce friction, improve agility and make compliance more accessible, especially for small and mid-sized providers.

What are the main goals of FedRAMP 20x?

  • Accelerate cloud adoption across federal agencies
  • Reduce the cost and complexity of authorization
  • Improve security through automation and continuous monitoring
  • Enable real-time visibility into compliance posture
  • Standardize processes like SCNs and vulnerability management

What are VDR and VER in FedRAMP 20x?

VDR (Vulnerability Detection and Response) and VER (Vulnerability Evaluation and Reporting) are continuous monitoring requirements introduced for Rev5-authorized providers. They replace the monthly POA&M with a continuous, per-finding workflow: Every vulnerability evaluated within days of detection, every output machine-readable.

Explore More

Online survey and digital form checklist by laptop computer, Document Management Checking System, online documentation database and process manage files.

Blog

· Nov 9, 2026

· 5 min read

Why FedRAMP authorization matters for GRC platforms

By The Diligent team

FedRAMP proves your GRC platform meets government-grade security standards. Learn why it’s essential for protecting sensitive compliance data. Read here.

Woman In Office Using Laptop

Blog

· Aug 19, 2026

· 5 min read

From spreadsheets to real-time: How federal agencies are modernizing FISMA, RMF and Zero Trust Compliance

By Jason Venner

Federal agencies still run FISMA, RMF and Zero Trust on spreadsheets. See how automation and CCM close the compliance gap. Read more.

Team mates discussing about FedRAMP

Blog

· Aug 9, 2026

· 15 min read

FedRAMP compliance: What it is, what it requires and how to achieve it

Writing on governance, risk, compliance and audit since 2020

By Kezia Farnham

Understand FedRAMP compliance requirements, impact levels and the path to authorization, plus how automation simplifies the process.