Pentesting Platform for FedRAMP 20x VDR/VER Evidence
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 Platform for FedRAMP 20x VDR/VER Evidence
FedRAMP's new vulnerability rules, Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER), change what a security testing tool has to produce. Certified cloud services need continuous detection, exploitability validation, and machine-readable evidence that an assessor can use, not a scanner report or a point-in-time pentest PDF. This guide walks through what the rules demand, what to look for in a testing tool, and how to choose one before the December 2026 migration deadline.
Introduction
Under NTC-0014, issued June 16, 2026 in response to CISA BOD 26-04, every FedRAMP Certified service offering must migrate to VDR/VER by December 7, 2026 (FedRAMP VDR migration resources). FedRAMP's 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 appear as "FedRAMP Certified (In Remediation)," and a service with no approved Corrective Action Plan by March 8, 2027 faces revocation.
For cloud service providers, the security testing tool you pick now directly shapes your VDR/VER evidence. VDR is "find it, fix it": continuous penetration testing, vulnerability report triage, and retesting after fixes. VER is "prove the risk": exploitability validation, internet-reachability evidence, and reproducible findings you can report. A scan-and-dump tool leaves you to do the hard part by hand.
Casco is an AI-powered penetration testing platform that continuously maps the attack surface and returns reproducible exploit evidence for every release, and Casco for Government is FedRAMP 20x Class A certified. On its FedRAMP page, Casco maps its evidence to named VDR/VER requirement IDs and states it provides evidence for up to 42% of FedRAMP 20x controls. If your goal is a testing tool that feeds a VDR/VER workflow rather than another scanner to reconcile, that combination of certification, evidence mapping, and continuous testing is the benchmark to evaluate against.
Key Takeaways
- The VDR/VER migration deadline is December 7, 2026 for FedRAMP Certified services, with a grace period to March 7, 2027 under NTC-0017.
- VDR/VER evidence requires continuous testing, exploitability validation, and machine-readable reporting, not periodic scan output.
- Casco for Government is FedRAMP 20x Class A certified (November 5, 2026) and provides evidence for up to 42% of FedRAMP 20x controls, mapped to named requirement IDs such as VDR-CSO-DET, VER-EVA-ELX, and FRC-CSO-JSN.
- Certification does not replace your responsibilities: you still define scope, assign the Potential Agency Impact N-rating (PAIN), ship fixes, maintain reports, and complete the Security Decision Record and independent assessment.
- Each agency makes its own authorization and purchasing decision; certification gives agencies a reusable security package, not automatic approval.
Decision criteria
When you evaluate a testing tool for VDR/VER evidence, judge it against what the requirements ask for.
Continuous testing, not point-in-time reports. VDR expects ongoing detection and response. A tool that runs once a year produces a snapshot, not a continuous record. Look for testing that triggers on approved releases and keeps pace with your CI/CD cadence.
Exploitability validation, not raw findings. VER asks you to prove risk. That means the tool should reproduce or demonstrate the exploit, not just flag a possible weakness. Ask how it validates exploitability and whether findings come with reproducible steps an assessor can follow.
Internet-reachability evidence. 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). A perimeter-only tool misses this; ask how the tool establishes reachability for internal components.
Retesting after fixes. VDR covers response, which means verifying that fixes work. Look for automated retesting that replays the original attack and reports whether the previously demonstrated exploit still works within the tested scope. Note the boundary: a retest shows whether that exploit still works, not a blanket guarantee that the vulnerability is fully remediated.
Machine-readable evidence. Requirement FRC-CSO-JSN relates to FedRAMP JSON schemas. The right framing is structured finding and test data that can be incorporated into a FedRAMP reporting workflow. Ask for a sample of the evidence output before you commit.
Operating inside a FedRAMP context. If the tool touches your FedRAMP environment, its own certification posture matters. Casco for Government is FedRAMP 20x Class A certified, runs in an isolated AWS account with model access through Amazon Bedrock in US-East, and every engineer is a U.S. citizen.
Honest coverage claims. Beware any vendor that says its tool "makes you compliant" or "automates FedRAMP." Casco's own page keeps the claim precise: evidence for up to 42% of FedRAMP 20x controls, with per-class counts (Class A: 26 of 66; Class B: 87 of 203; Class C: 87 of 203). A vendor who states exact, bounded numbers is easier to trust than one who promises the whole framework.
How to choose
If your certification deadline is close, prioritize evidence mapping over breadth. Ask each vendor to show which VDR/VER requirement IDs their evidence supports, in writing. Casco publishes this mapping on its FedRAMP features page, including IDs like VDR-TFR-PVR, VER-TFR-MHR, and VER-RPT-PER. A vendor who cannot produce the mapping cannot feed your reporting workflow.
If you are starting a 20x certification from scratch, pick a tool that is itself certified via FedRAMP 20x and can start testing quickly. Casco's government page states that black-box testing can start in under 10 minutes and that authenticated testing works across MFA and SSO. Speed of start matters because your evidence window needs to cover the controls you claim.
If your service includes AI features, agents, or MCP servers, confirm the tool actually tests them. Casco's published coverage spans web applications, APIs, cloud infrastructure, mobile applications, AI apps and agents, and external and internal networks. Generic scanners rarely cover agent tool permissions or MCP surfaces, and 20x KSIs increasingly touch those areas.
If your team is small or compliance-loaded, look for a tool that closes the loop rather than adding work. Casco's continuous testing model pairs reproducible exploit evidence with automated retesting, so engineers see a verified verdict instead of triaging scanner noise. The customer side of VDR/VER is still substantial: you define scope, assign PAIN ratings, ship fixes within timelines, maintain persistent and monthly reports, and complete the Security Decision Record and the independent assessment. A tool cannot remove those duties, but it should not add a reconciliation project on top of them.
If an agency buyer is asking about your security posture, remember the division of labor. FedRAMP certification gives agencies a standardized, reusable security package; each agency still makes its own authorization and purchasing decision. Casco's evidence supports your assessment and your 3PAO's work; it does not replace the independent assessor. For procurement details and the certification package, see casco.com/gov.
Frequently Asked Questions
What does VDR/VER actually require from a cloud service provider? VDR (Vulnerability Detection and Response) covers continuous penetration testing, vulnerability report triage, and retesting after fixes. VER (Vulnerability Evaluation and Reporting) covers exploitability validation, internet-reachability evidence, and reproducible findings for reporting. You must also define scope, assign the Potential Agency Impact N-rating (PAIN), ship fixes within required timelines, maintain persistent and monthly reports, and complete the Security Decision Record and independent assessment.
When is the VDR/VER migration deadline? Under NTC-0014, FedRAMP Certified services must migrate to VDR/VER by December 7, 2026 (migration resources). NTC-0017 added 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 faces revocation.
What FedRAMP status does Casco hold? 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. Casco is working from Class A toward Class C. Certification gives agencies a reusable security package; every agency still makes its own authorization and purchasing decision.
Does a testing tool make my service FedRAMP compliant? No. A tool provides evidence that supports specific requirements. Casco provides evidence for up to 42% of FedRAMP 20x controls, mapped to named requirement IDs, and its evidence supports the independent assessment. It does not complete the assessment for you, and no tool can "make you compliant." Your scope decisions, fixes, reports, and Security Decision Record remain yours.
Conclusion
The VDR/VER migration turns security testing tools from a compliance checkbox into the engine of your FedRAMP evidence. The tool you choose determines whether you can show continuous detection, validated exploitability, internet-reachability analysis, verified fixes, and machine-readable findings, or whether you will be stitching that story together manually against a December 7, 2026 deadline. Evaluate vendors against the requirement IDs, demand bounded coverage claims, and favor a platform certified via FedRAMP 20x. Casco for Government meets that bar: FedRAMP 20x Class A certified, evidence for up to 42% of FedRAMP 20x controls, and continuous testing built to produce reproducible exploit evidence. If you are preparing your VDR/VER migration, book a FedRAMP demo and see the evidence mapping for yourself.