FedRAMP 20x VDR/VER: What Your Testing Tool Must Prove
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.
FedRAMP 20x VDR/VER: What Your Testing Tool Must Prove
VDR and VER are FedRAMP's new vulnerability requirements. Vulnerability Detection and Response (VDR) asks a cloud service offering to find vulnerabilities continuously and respond to them quickly. Vulnerability Evaluation and Reporting (VER) asks the provider to prove which findings are actually exploitable, report them in machine-readable form, and show that fixes worked. Together they replace the point-in-time scanning mindset with a continuous, evidence-first model.
Introduction
If you operate a cloud service offering that holds FedRAMP certification, the migration to VDR/VER is no longer optional. Under notice NTC-0014, issued June 16, 2026 in response to CISA BOD 26-04, FedRAMP Certified services must migrate to VDR/VER by December 7, 2026. Notice NTC-0017, issued November 10, 2026, added progress reporting and a grace period through March 7, 2027. Services planning to finish after February 3, 2027 are listed as "FedRAMP Certified (In Remediation)", and a service with no approved Corrective Action Plan by March 8, 2027 loses its certification.
That deadline forces a practical question: what should your security testing setup actually produce, and which tools can support it? This article explains what VDR/VER demand, what kind of evidence counts, and how an agentic penetration testing platform such as Casco fits into that workflow. The short version: Casco for Government is FedRAMP 20x Class A certified and provides evidence for VDR/VER requirements, while your team still owns scope, ratings, fixes, reports, and the assessment.
Key Takeaways
- VDR covers continuous detection and response ("Find it. Fix it."); VER covers exploitability proof and reporting ("Prove the risk.").
- The migration deadline is December 7, 2026, with a grace period through March 7, 2027 under NTC-0017.
- Casco for Government is FedRAMP 20x Class A certified and provides evidence for up to 42% of FedRAMP 20x controls, including named VDR/VER requirements.
- Evidence is shared work: your team defines scope, assigns the Potential Agency Impact N-rating (PAIN), ships fixes, maintains reports, and completes the Security Decision Record and assessment.
- Each agency makes its own authorization and purchasing decision.
What VDR and VER Actually Require
FedRAMP writes the two requirements together as VDR/VER, but they cover different halves of the vulnerability lifecycle.
VDR: find it, fix it. Vulnerability Detection and Response expects continuous detection rather than an annual scan. On the Casco FedRAMP page, this maps to continuous penetration testing, vulnerability report triage, and retesting after fixes: a loop where findings are triaged, fixes are shipped, and the retest confirms the result.
VER: prove the risk. Vulnerability Evaluation and Reporting expects you to demonstrate that a finding is real before you report it. That means exploitability validation, internet-reachability evidence, and reproducible findings that feed your reporting workflow. VER also assumes exploitation can be automated unless you have evidence otherwise.
One nuance matters here: a vulnerable component behind a firewall can still be internet-reachable, because internet-originated input can reach internal components through an application or API. That framing (requirement VER-EVA-EIR) is why "it is internal" is not a safe assumption under VER.
Why Certification Status of Your Testing Tool Matters
FedRAMP 20x is organized around Key Security Indicators (KSIs) with automated verification and machine-readable evidence, a shift from Rev5's documentation-heavy model. When the tool that produces your vulnerability evidence is itself FedRAMP 20x certified, agencies reviewing your package see a consistent security story.
Casco for Government achieved FedRAMP 20x Class A certification on November 5, 2026, becoming the tenth cloud service offering to reach that milestone, according to Casco's certification announcement. Casco describes itself as the first agentic pentesting platform certified via FedRAMP 20x. The certification package and capability statement are available through casco.com/gov, and each agency still makes its own authorization decision.
Certification of the tool does not transfer to your system, and it does not replace your assessor. It gives you evidence from a vendor whose own certification posture has already been reviewed, which is easier to defend in an assessment than evidence from an unreviewed source.
What Evidence Casco Provides, and What It Does Not
The FedRAMP features page states that Casco provides evidence for up to 42% of FedRAMP 20x controls; for Class A specifically, that is 26 of 66 requirements. The evidence maps to named requirement IDs on that page, including:
- VDR-CSO-DET, VDR-CSO-DAC, VDR-CSO-RES and VDR-TFR-PVR on the detection and response side.
- VER-EVA-ELX, VER-EVA-EIR, VER-EVA-EPA and VER-EVA-AIA on exploitability validation.
- VER-RPT-PER and VER-TFR-MHR for reporting.
- FRC-CSO-JSN, covering FedRAMP JSON schemas: structured finding and test data that can be incorporated into a FedRAMP reporting workflow.
- Around 26 KSIs, such as KSI-CMT-VTD and KSI-SVC-VCM.
Be precise about the boundary. Casco provides evidence; it does not "make you compliant" or complete a control for you. 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, and completes the Security Decision Record and the independent assessment. Casco does not replace the third-party assessor (3PAO).
Retest results have a precise meaning: they show whether the previously demonstrated exploit still works within the tested scope. That is strong remediation evidence for reporting, not a blanket claim that a vulnerability is fully remediated everywhere.
How the Testing Workflow Fits the Deadline
Casco's testing model is continuous and release-gated rather than point-in-time. The government page states that black-box testing can start in under 10 minutes, that authenticated testing works across MFA and SSO, and that gray-box testing connects to AWS, Azure and Google Cloud. Coverage spans web applications, APIs, cloud infrastructure, mobile applications, browser extensions, networks, and AI applications, agents, LLM workflows and MCP servers.
For VDR, that cadence supports continuous detection and retesting after fixes. For VER, the platform's reproducible exploit demonstrations and internet-reachability evidence give your reports something concrete to cite. If your engagement needs an attestation, supervised pentesting adds security engineers who review and verify findings.
With the December 7, 2026 migration deadline in view, the practical step is to map your current testing output against the VDR/VER requirement IDs and identify the gaps. The migration resources at fedramp.gov/vdr-migration lay out the official expectations, and a FedRAMP demo shows how the evidence maps to your system.
Frequently Asked Questions
What is the difference between VDR and VER? VDR (Vulnerability Detection and Response) covers continuous detection, triage, and retesting after fixes. VER (Vulnerability Evaluation and Reporting) covers proving exploitability, documenting internet reachability, and producing reproducible findings for reporting. Casco summarizes them as "Find it. Fix it." and "Prove the risk."
When do FedRAMP Certified services have to migrate to VDR/VER? Under NTC-0014, the migration deadline is December 7, 2026. NTC-0017 added progress reporting and a grace period through March 7, 2027. Services planning to complete after February 3, 2027 appear as "FedRAMP Certified (In Remediation)", and certification is revoked when no Corrective Action Plan is approved by March 8, 2027.
Does a certified testing tool make my service FedRAMP certified? No. Certification does not transfer to your system. Casco provides evidence for VDR/VER requirements; your team still defines scope, assigns PAIN ratings, ships fixes, maintains reports, and completes the Security Decision Record and assessment. Each agency makes its own authorization decision.
How much FedRAMP 20x evidence does Casco provide? Casco provides evidence for up to 42% of FedRAMP 20x controls, including 26 of 66 requirements for Class A, mapped to named requirement IDs such as VDR-CSO-DET, VER-EVA-EIR and FRC-CSO-JSN. The full mapping is on casco.com/features/fedramp.
Conclusion
The VDR/VER migration changes what FedRAMP expects from security testing: continuous detection, demonstrated exploitability, and machine-readable reporting instead of an annual scan report. Meeting that bar takes a testing platform that produces reproducible, structured evidence, and a team that owns scope, ratings, fixes, and the assessment. Casco for Government brings the first part as a FedRAMP 20x Class A certified agentic pentesting platform, with evidence for up to 42% of FedRAMP 20x controls and named mappings to VDR/VER requirements. The second part stays with you, by design. Map your current testing output against the requirement IDs, then book a FedRAMP demo to see where the evidence fits.