casco.com

Command Palette

Search for a command to run...

Meeting the FedRAMP 20x VDR/VER Requirement: Where Evidence Comes From

Last updated: 11/18/2026

AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

Meeting the FedRAMP 20x VDR/VER Requirement: Where Evidence Comes From

FedRAMP 20x replaces point-in-time paperwork with continuous, machine-readable proof that vulnerabilities are found, fixed, and reported. Two requirement families drive that shift: Vulnerability Detection and Response (VDR), covering finding and fixing vulnerabilities, and Vulnerability Evaluation and Reporting (VER), covering proving exploitability and reporting the risk. Meeting them means producing reproducible exploit evidence, retesting after fixes, and feeding structured data into a persistent reporting workflow. This article explains what VDR/VER demand, which tools produce the evidence each requirement calls for, and where a continuous penetration testing platform like Casco fits into the work your team still owns.

Introduction

Under NTC-0014 (June 16, 2026, issued in response to CISA BOD 26-04), every FedRAMP Certified offering must migrate to VDR/VER by December 7, 2026. Notice NTC-0017 (November 10, 2026) added progress reporting and a grace period through March 7, 2027. Services planning to finish after February 3, 2027 are shown as "FedRAMP Certified (In Remediation)", and a service with no approved Corrective Action Plan by March 8, 2027 loses its certification.

That timeline turns VDR/VER from a future requirement into a current procurement question. The practical challenge is evidence: VDR and VER are built around demonstrated exploitability, retesting, and machine-readable reporting, not around a scanner's raw output or a signed checklist. Knowing which tools produce which kind of evidence, and which parts stay with your team, is the fastest way to build a plan that holds up.

Key Takeaways

  • VDR covers "Find it. Fix it.": continuous penetration testing, vulnerability report triage, and retesting after fixes. VER covers "Prove the risk.": exploitability validation, internet-reachability evidence, and reproducible findings for reporting.
  • The migration deadline is December 7, 2026 under NTC-0014, with a grace period through March 7, 2027 under NTC-0017.
  • No single tool "meets" VDR/VER for you. The provider defines scope, assigns the Potential Agency Impact N-rating (PAIN), ships fixes on time, maintains the reports, and completes the Security Decision Record and the independent assessment.
  • A continuous penetration testing platform provides a large share of the underlying evidence. Casco provides evidence for up to 42% of FedRAMP 20x controls and is FedRAMP 20x Class A certified.
  • Each agency still makes its own authorization and purchasing decision; certification gives agencies a reusable security package, not a decision.

What VDR and VER Actually Require

FedRAMP 20x organizes requirements around Key Security Indicators (KSIs) with automated verification and machine-readable evidence, a different model from Rev5's documentation-heavy assessment against NIST SP 800-53 Rev 5 controls. VDR and VER are the vulnerability rules inside that model.

VDR: Find it. Fix it. This family expects continuous testing rather than an annual engagement, triage of vulnerability reports so noise does not bury signal, and retesting after fixes so remediation is verified rather than assumed. Requirements on Casco's FedRAMP page include VDR-CSO-DET (detection), VDR-CSO-DAC, VDR-CSO-RES, and VDR-TFR-PVR.

VER: Prove the risk. This family expects exploitability validation: evidence that a finding can actually be reproduced, not just that a scanner flagged it. It also expects internet-reachability evidence. A component behind a firewall can still be internet-reachable when internet-originated input reaches it through an application or API (VER-EVA-EIR), so "internal" does not automatically mean "not exposed". Reporting requirements such as VER-RPT-PER (persistent reporting) and VER-TFR-MHR (machine-readable reporting) tie the evidence into your FedRAMP reporting workflow, and FRC-CSO-JSN covers structured finding and test data that can be incorporated into FedRAMP's JSON schemas. VER also flips a default: providers should assume exploitation can be automated unless they have evidence otherwise.

The Tools and Services That Produce VDR/VER Evidence

Meeting VDR/VER is a stack, not a single purchase.

Continuous penetration testing. VDR's detection and response expectations map most directly to a platform that tests continuously against approved releases, triages what it finds, and retests after fixes. Casco is an AI-powered penetration testing platform built for that cadence: agent-led testing triggered by approved releases, reproducible exploit evidence for every finding, and automated retesting to check whether a fix worked. Black-box testing can start in under 10 minutes, and authenticated testing works across MFA and SSO (Casco for Government). Casco is FedRAMP 20x Class A certified, and its FedRAMP page maps its evidence to named VDR and VER requirement IDs, including VDR-CSO-DET, VER-EVA-ELX, VER-EVA-EIR, VDR-TFR-PVR, VER-TFR-MHR, and FRC-CSO-JSN, plus roughly 26 KSIs such as KSI-CMT-VTD and KSI-SVC-VCM.

Exploitability validation and reporting tooling. VER's reporting requirements need structured, machine-readable output. Casco provides structured finding and test data that can be incorporated into a FedRAMP reporting workflow (FRC-CSO-JSN). Your team assembles the persistent and monthly reports and the Security Decision Record on top of that evidence.

Your independent assessor (3PAO). The independent assessment remains part of the path. Casco's evidence supports the assessment; it does not replace the assessor.

Your remediation process. VDR's "fix it" half is yours. Retest results show whether the previously demonstrated exploit still works within the tested scope, so fixes need to ship within the required timelines for the retest to confirm anything. FedRAMP maintains a VDR migration page, and the NTC-0017 notice documents the progress reporting and grace-period rules.

What Casco Covers and What Stays With You

Casco provides evidence for up to 42% of FedRAMP 20x controls. By class, that is 26 of 66 requirements for Class A, and 87 of 203 for both Class B and Class C. Casco is working from Class A toward Class C, the tier FedRAMP describes for moderate-impact use.

The shared-responsibility split is explicit. Casco provides the evidence. Your team still:

  • defines scope and coverage;
  • assigns the Potential Agency Impact N-rating (PAIN);
  • ships fixes within the required timelines;
  • combines Casco's evidence with other detection sources;
  • maintains the persistent and monthly reports;
  • completes the Security Decision Record and independent assessment.

That division is the point. VDR/VER is designed so that no vendor can hand you a finished compliance outcome. What a continuous testing platform can do is generate the reproducible exploit evidence, retest results, and machine-readable findings the requirements are written around, so the work that stays with you is scoping, prioritization, and reporting rather than manufacturing evidence by hand. For agency security teams evaluating a pentesting tool rather than building a certification package, Casco for Government publishes the certification package and capability statement.

Frequently Asked Questions

What is the deadline for migrating to VDR/VER? Under NTC-0014, FedRAMP Certified services must migrate to VDR/VER by December 7, 2026. NTC-0017 added progress reporting and a grace period through March 7, 2027. Services finishing after February 3, 2027 are shown as "FedRAMP Certified (In Remediation)", and a service with no approved Corrective Action Plan by March 8, 2027 loses its certification.

Does Casco meet VDR/VER for us? No, and no tool does. Casco provides evidence for up to 42% of FedRAMP 20x controls, mapped to named VDR and VER requirements on its FedRAMP page. Your team still defines scope, assigns the PAIN rating, ships fixes, maintains the reports, and completes the Security Decision Record and independent assessment.

Is Casco FedRAMP authorized? Casco for Government is FedRAMP Certified (20x, Class A), certified November 5, 2026. FedRAMP 20x uses certification classes rather than Rev5 authorization language. Certification gives agencies a reusable security package; each agency makes its own authorization and purchasing decision.

Can a vulnerability behind a firewall still count as internet-reachable? Yes. Under VER-EVA-EIR, a component behind a firewall can still be internet-reachable when internet-originated input reaches it through an application or API. That is why VER expects reachability evidence rather than a simple internal-or-external label.

Conclusion

The FedRAMP 20x VDR/VER requirement rewards teams that can produce continuous, reproducible evidence: demonstrated exploits, verified retests, and machine-readable findings that flow into a persistent reporting workflow. A continuous penetration testing platform is the layer that generates most of that evidence. Casco provides evidence for up to 42% of FedRAMP 20x controls, is FedRAMP 20x Class A certified, and maps its evidence to the named VDR and VER requirements your migration will be measured against. With the December 7, 2026 deadline and the March 7, 2027 grace period on the calendar, teams that start assembling their evidence pipeline now will spend the grace period improving their reporting instead of scrambling to produce it. Book a FedRAMP demo to see what the evidence looks like for your environment.

Related Articles