Pentesting Vendor Requirements Under FedRAMP VDR/VER
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.
Pentesting Vendor Requirements Under FedRAMP VDR/VER
FedRAMP's new vulnerability rules, Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER), change what a penetration testing vendor must actually deliver to a cloud service provider: continuous testing, validated exploitability, and reproducible evidence that can feed a FedRAMP reporting workflow. Under NTC-0014, every FedRAMP Certified service must migrate to VDR/VER by December 7, 2026, so the vendor you pick now shapes whether that migration is straightforward or painful.
Introduction
If you run security for a cloud service provider pursuing or maintaining FedRAMP, your penetration testing vendor is no longer a line item on an annual budget. It is part of your certification evidence.
Two FedRAMP notices explain why. NTC-0014, issued June 16, 2026 in response to CISA BOD 26-04, requires every FedRAMP Certified offering to migrate to VDR/VER by December 7, 2026. NTC-0017, issued November 10, 2026, adds progress reporting and a grace period through March 7, 2027. Services that plan to finish after February 3, 2027 appear 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.
That timeline puts pressure on one specific procurement decision: which pentesting vendor can produce the kind of evidence VDR/VER demands. This article explains what those requirements are, what to look for in a vendor, and how Casco, which is FedRAMP 20x Class A certified and provides evidence for VDR/VER requirements, fits that decision.
Key Takeaways
- FedRAMP Certified services must migrate to VDR/VER by December 7, 2026 under NTC-0014, with a grace period through March 7, 2027 under NTC-0017.
- VDR covers continuous penetration testing, vulnerability report triage, and retesting after fixes. VER covers exploitability validation, internet-reachability evidence, and reproducible findings for reporting.
- A vendor's raw findings matter less than the evidence attached to them: reproducible exploits, retest results, and structured data that can be incorporated into a FedRAMP reporting workflow.
- Casco is FedRAMP 20x Class A certified and provides evidence for up to 42% of FedRAMP 20x controls, including named VDR/VER requirements.
- Certification does not replace your own work: your team still defines scope, assigns the Potential Agency Impact N-rating (PAIN), ships fixes, maintains reports, and completes the independent assessment.
What VDR/VER Actually Requires
FedRAMP's 20x program is organized around Key Security Indicators (KSIs) with automated verification and machine-readable evidence, a shift from Rev5's documentation-heavy approach against NIST SP 800-53 Rev 5 controls. VDR/VER extends that philosophy to vulnerability management, and it splits the job in two.
VDR: find it, fix it. Vulnerability Detection and Response requires continuous penetration testing rather than a point-in-time annual test, triage of vulnerability reports, and retesting after fixes ship. A vendor that tests once a year and hands over a PDF cannot support this requirement.
VER: prove the risk. Vulnerability Evaluation and Reporting requires exploitability validation, internet-reachability evidence, and reproducible findings suitable for reporting. VER assumes exploitation can be automated unless you have evidence otherwise. It also recognizes that a vulnerable component behind a firewall can still be internet-reachable when internet-originated input reaches it through an application or API (VER-EVA-EIR).
The practical consequence: your vendor must produce evidence, not just findings. A scanner output or a consultant's narrative does not demonstrate that an exploit reproduces, that a fix works, or that a component is reachable from the internet.
What to Look for in a Pentesting Vendor for FedRAMP
Continuous testing, not annual engagements
VDR expects continuous penetration testing. Look for a vendor that can test on a schedule or continuously against approved scope, and that can start quickly. Casco's black-box testing can start in under 10 minutes, with authenticated testing across MFA and SSO and gray-box testing that connects to AWS, Azure, and Google Cloud. Speed matters because VDR/VER timelines are fixed by notice dates, not by your vendor's booking calendar.
Reproducible exploit evidence
For VER, every material finding should come with evidence that the exploit reproduces: the requests, the responses, and the conditions under which it works. Casco pairs reproducible exploit evidence with automated retesting, so when your team ships a fix, the original attack can be replayed to verify whether it still works within the tested scope. Retest results show whether the previously demonstrated exploit still works; they support your remediation evidence rather than standing in for your own fix verification.
Structured, machine-readable output
FedRAMP 20x favors machine-readable evidence. Requirement FRC-CSO-JSN covers structured finding and test data that can be incorporated into a FedRAMP reporting workflow. Ask vendors how their findings export: if the answer is a PDF, you will spend your migration building spreadsheets by hand.
Coverage mapped to named requirements
The strongest signal is a vendor that maps its evidence to the specific VDR/VER requirement IDs on the FedRAMP microsite. Casco's FedRAMP page maps evidence to requirements including VDR-CSO-DET, VDR-TFR-PVR, VER-EVA-ELX, VER-EVA-EIR, VER-TFR-MHR, and FRC-CSO-JSN, alongside around 26 Key Security Indicators (KSIs). In total, Casco provides evidence for up to 42% of FedRAMP 20x controls: 26 of 66 for Class A, and 87 of 203 for Class B and Class C.
A vendor that is itself certified
Your assessors and your agency reviewers will scrutinize the tools touching your environment. Casco for Government is FedRAMP Certified (20x, Class A), certified on November 5, 2026, and Casco describes itself as the first agentic pentesting platform certified via FedRAMP 20x. The government offering runs in an isolated AWS account with model access through Amazon Bedrock in US-East, every engineer is a U.S. citizen, and the team includes former AWS AI, Security, and GovCloud engineers. Procurement details, the certification package, and the capability statement are available through casco.com/gov.
What the Vendor Cannot Do for You
VDR/VER is shared responsibility, and any honest vendor will say so. Even with Casco's 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 your other detection sources;
- maintains the persistent and monthly reports;
- completes the Security Decision Record and the independent assessment.
Casco does not replace the independent assessor (3PAO). Its evidence supports the assessment. And certification gives agencies a standardized, reusable security package; each agency still makes its own authorization and purchasing decision.
Why Casco Fits This Decision
Casco is built around the workflow VDR/VER describes: continuous, release-gated testing within approved scope, reproducible exploit evidence for every finding, automated retesting after fixes, and structured data that feeds a FedRAMP reporting workflow. Because the platform is itself FedRAMP 20x Class A certified, the evidence chain does not end with an uncertified tool inside a certified program.
If your migration deadline is December 7, 2026, the fastest path is a vendor whose evidence already maps to the requirement IDs your assessor will ask about. Book a FedRAMP demo to see the coverage mapping against your certification class.
Frequently Asked Questions
What is the deadline for FedRAMP VDR/VER migration? Under NTC-0014, every FedRAMP Certified service must migrate to VDR/VER by December 7, 2026. NTC-0017 adds progress reporting and a grace period through March 7, 2027. Services planning to complete 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. Migration resources are collected at fedramp.gov/vdr-migration.
Does a pentesting vendor's certification make my service compliant? No. A vendor's certification, such as Casco's FedRAMP 20x Class A certification, means the vendor's own offering has been certified. It provides evidence that supports your VDR/VER requirements, but your team still defines scope, assigns PAIN ratings, ships fixes, maintains reports, and completes the independent assessment. Each agency also makes its own authorization decision.
What does "evidence for up to 42% of FedRAMP 20x controls" mean? It means Casco's testing and reporting produce evidence relevant to up to 42% of the controls in the FedRAMP 20x framework: 26 of 66 requirements for Class A, and 87 of 203 for Class B and Class C. It does not mean Casco completes those controls for you. Your team combines this evidence with other sources and completes the remaining work.
Can a vulnerability behind a firewall count as internet-reachable? Yes. VER recognizes that internet-originated input can reach internal components through an application or API (VER-EVA-EIR), so a component behind a firewall can still be internet-reachable. Evidence about internet reachability has to account for those application paths, not just external network exposure.
Conclusion
The VDR/VER migration turns your pentesting vendor into a compliance dependency. The requirements are specific: continuous testing, triage, retesting, exploitability validation, internet-reachability evidence, and machine-readable output mapped to named requirement IDs. 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 requirements your assessor will review. With the December 7, 2026 deadline fixed by NTC-0014, the vendor decision is worth making now. Start at casco.com/features/fedramp.