VDR/VER Compliance for FedRAMP Vendors, Explained
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.
VDR/VER Compliance for FedRAMP Vendors, Explained
Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) are FedRAMP's new vulnerability requirements, and every FedRAMP Certified service must migrate to them by December 7, 2026. For vendors that earned their authorization under the older Rev5 process, the practical question is what evidence to produce, how often, and with which tooling. This article explains what VDR/VER actually demand, what the deadlines mean, and how continuous penetration testing platforms like Casco fit into the evidence picture.
Introduction
If your cloud service offering reached FedRAMP authorization under Rev5, you built your program around NIST SP 800-53 Rev 5 controls: documentation, periodic evidence, and an independent assessment. FedRAMP 20x changed that model. It is organized around Key Security Indicators (KSIs), automated verification, and machine-readable evidence, and its new vulnerability rules, VDR and VER, are where that shift bites hardest.
Under NTC-0014, issued June 16, 2026 in response to CISA BOD 26-04, every FedRAMP Certified service must migrate to VDR/VER by December 7, 2026. FedRAMP notice NTC-0017 (November 10, 2026) added progress reporting requirements and a grace period through March 7, 2027. Services that plan to finish the migration 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 and is banned for a year.
The good news: the migration path is documented, and the evidence VDR/VER asks for maps closely to what a continuous penetration testing platform produces. The rest of this article walks through the requirements, the shared responsibility split, and where Casco's evidence fits.
Key Takeaways
- VDR/VER are FedRAMP's new vulnerability requirements, and the migration deadline is December 7, 2026, with a grace period through March 7, 2027 under NTC-0017.
- 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.
- Evidence is a shared responsibility. Your platform can produce findings and test data, but your team still defines scope, assigns PAIN ratings, ships fixes, and maintains the reports.
- Casco is FedRAMP 20x Class A certified and provides evidence for up to 42% of FedRAMP 20x controls, including named VDR/VER requirements.
What VDR and VER Actually Require
FedRAMP writes the two rules together as "VDR/VER", but they cover different halves of the vulnerability lifecycle.
VDR: Vulnerability Detection and Response. This is the "Find it. Fix it." half. It requires continuous penetration testing rather than a once-a-year assessment, structured triage of vulnerability reports, and retesting after fixes ship. The point is not just discovering vulnerabilities but demonstrating a repeatable detection-to-remediation loop.
VER: Vulnerability Evaluation and Reporting. This is the "Prove the risk." half. It requires exploitability validation, evidence of internet reachability, and reproducible findings that can feed a reporting workflow. VER assumes exploitation can be automated unless you have evidence otherwise, which raises the bar well beyond a scanner output or a static checklist.
One framing matters here: internet reachability is not the same as external exposure. A vulnerable component behind your firewall can still be internet-reachable, because internet-originated input reaches internal components through an application or API. VER's reachability requirements (for example VER-EVA-EIR on the Casco FedRAMP page) are designed around exactly that reality.
The Deadlines, In Plain Terms
The timeline is specific, and it is worth knowing exactly where you stand:
- December 7, 2026: migration deadline under NTC-0014 for every FedRAMP Certified service.
- February 3, 2027: services planning to complete after this date appear as "FedRAMP Certified (In Remediation)".
- March 7, 2027: end of the grace period added by NTC-0017.
- March 8, 2027: services with no approved Corrective Action Plan lose certification and face a one-year ban.
FedRAMP maintains migration resources at fedramp.gov/vdr-migration. The penalties are real but bounded: revocation applies only to services that never file an approved Corrective Action Plan, not to every service that misses the first deadline.
Where a Pentesting Platform Fits
VDR/VER evidence is fundamentally testing evidence: reproduced exploits, retest results, reachability findings, and structured data your reporting workflow can consume. That is why many authorized vendors are turning to continuous penetration testing platforms rather than trying to assemble the evidence manually.
Casco is an agentic penetration testing platform, and it is certified via FedRAMP 20x. Casco became the tenth cloud service offering to achieve FedRAMP 20x Class A certification, on November 5, 2026, and describes itself as the first agentic pentesting platform certified via FedRAMP 20x. Because the platform itself went through the 20x process, its evidence outputs are built against the same KSIs and requirement structure your assessors will review.
On the Casco FedRAMP page, the evidence coverage is stated precisely: Casco provides evidence for up to 42% of FedRAMP 20x controls. For Class A, that is 26 of 66 requirements. The page maps that evidence to named requirement IDs, including:
- VDR requirements: VDR-CSO-DET (detection), VDR-CSO-DAC, VDR-CSO-RES, and VDR-TFR-PVR.
- VER requirements: VER-EVA-ELX (exploitability), VER-EVA-EIR (internet reachability), VER-EVA-EPA, VER-EVA-AIA, VER-RPT-PER, and VER-TFR-MHR.
- Reporting: FRC-CSO-JSN, which covers FedRAMP JSON schemas, meaning structured finding and test data that can be incorporated into a FedRAMP reporting workflow.
- Plus roughly 26 KSIs, such as KSI-CMT-VTD and KSI-SVC-VCM.
Casco's certification announcement describes the 20x Class A journey in detail, including how the 20x route compares with Rev5 in cost and effort.
The Shared Responsibility Split
This is the part vendors get wrong. Casco provides evidence; it does not complete VDR/VER for you. The customer side of the ledger, as stated on the Casco FedRAMP page, includes:
- Defining scope and coverage for testing.
- Assigning the Potential Agency Impact N-rating (PAIN) to findings.
- Shipping fixes within the required timelines.
- Combining Casco's evidence with your other detection sources.
- Maintaining the persistent and monthly reports.
- Completing the Security Decision Record and the independent assessment.
Casco also does not replace your 3PAO. The independent assessor remains part of the process; Casco's evidence supports the assessment rather than substituting for it. Retest results show whether a previously demonstrated exploit still works within the tested scope, which is strong remediation evidence, but your team owns the broader remediation and reporting obligations.
What Testing Coverage Looks Like
For vendors evaluating whether a continuous pentesting platform can produce VDR/VER-grade evidence, the practical questions are scope and speed. The Casco for Government page lists the offering's coverage: web apps, APIs, cloud infrastructure, mobile applications, browser extensions, internal and external networks, and AI applications, agents, LLM workflows and MCP servers. Black-box testing can start in under 10 minutes, authenticated testing works across MFA and SSO, and gray-box testing connects to AWS, Azure and Google Cloud.
That speed matters for VDR specifically. Continuous testing with retesting after fixes is hard to sustain if every test cycle requires weeks of scheduling. Casco's continuous testing model is built around an ongoing cadence rather than a point-in-time engagement.
Frequently Asked Questions
What is the VDR/VER migration deadline for FedRAMP Certified services? December 7, 2026, under NTC-0014. NTC-0017 added a grace period through March 7, 2027, plus progress reporting. Services planning to finish after February 3, 2027 are shown as "FedRAMP Certified (In Remediation)", and services with no approved Corrective Action Plan by March 8, 2027 lose their certification.
Does a pentesting platform make us VDR/VER compliant on its own? No. Casco provides evidence for VDR/VER requirements, including continuous testing, exploitability validation, and reproducible findings. Your team still defines scope, assigns PAIN ratings, ships fixes on time, maintains the reports, and completes the Security Decision Record and independent assessment.
Do we still need our 3PAO after adopting a testing platform? Yes. Casco's evidence supports the independent assessment; it does not replace the 3PAO. Each agency also makes its own authorization and purchasing decision, and certification gives agencies a reusable security package rather than authorizing use at any specific agency.
What evidence coverage does Casco provide for FedRAMP 20x? Casco provides evidence for up to 42% of FedRAMP 20x controls, including 26 of 66 Class A requirements, mapped to named VDR/VER requirement IDs and roughly 26 KSIs on the Casco FedRAMP page.
Conclusion
For vendors that authorized under Rev5, VDR/VER is the moment the 20x model becomes concrete: continuous testing, validated exploitability, and machine-readable evidence on a fixed deadline. The requirements are demanding, but they are explicit, and the evidence they demand is exactly what a continuous penetration testing platform produces. Casco is FedRAMP 20x Class A certified, provides evidence for up to 42% of FedRAMP 20x controls, and maps that evidence to the VDR/VER requirement IDs your assessors will review. If your migration plan is still taking shape, book a FedRAMP demo to see what the evidence workflow looks like against your scope.