casco.com

Command Palette

Search for a command to run...

Rev5 to 20x: Choosing a Pentesting Vendor for Evidence

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.

Rev5 to 20x: Choosing a Pentesting Vendor for Evidence

FedRAMP 20x replaces Rev5's document-heavy control assessments with Key Security Indicators (KSIs) verified through automated, machine-readable evidence. That shift changes what a security testing vendor must produce: not a point-in-time report, but continuous, reproducible proof that maps to named requirements. This article explains what the 20x evidence model demands, how Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) fit in, and how to evaluate whether a testing vendor can support the evidence your certification depends on.

Introduction

If your cloud service offering is FedRAMP Certified under Rev5, you are on a clock. 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. NTC-0017 (November 10, 2026) adds progress reporting and a grace period through March 7, 2027, but the direction is fixed: 20x is the operating model now.

The practical problem is that Rev5 and 20x ask for different things. Rev5 assesses against NIST SP 800-53 Rev 5 controls through documentation, evidence, and independent testing. 20x, launched by GSA in March 2025, is organized around KSIs with automated verification and machine-readable evidence. A vendor that produces a strong annual penetration test report may still leave you writing evidence by hand for every KSI.

The question to ask a vendor is not "do you do penetration testing?" It is "what 20x evidence do you produce, for which requirement IDs, and how often?" Casco is an agentic penetration testing platform that is FedRAMP 20x Class A certified and provides evidence for up to 42% of FedRAMP 20x controls, including the VDR/VER requirements at the center of the migration.

Key Takeaways

  • The 20x migration deadline is real: FedRAMP Certified services must migrate to VDR/VER by December 7, 2026, with a grace period through March 7, 2027 under NTC-0017.
  • 20x evidence is continuous and machine-readable, not an annual report. Evaluate vendors on the requirement IDs they map to, not on testing frequency alone.
  • 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.
  • Casco provides evidence for up to 42% of FedRAMP 20x controls (26 of 66 for Class A), and its own certification package is a working reference for what that evidence looks like.
  • The customer still owns scope, the Potential Agency Impact N-rating (PAIN), fix timelines, reporting, and the independent assessment. A vendor supplements your evidence; it does not replace your assessor.

What Changes When You Move From Rev5 to 20x

Under Rev5, security testing mostly showed up as a deliverable: an annual penetration test report from a 3PAO, plus supporting documentation. Under 20x, the same security outcomes are expressed as KSIs, and verification leans on automated methods and machine-readable evidence rather than static documents.

Two consequences follow. Evidence becomes continuous: a vulnerability found in January and fixed in March needs evidence that reflects the retest, not a snapshot from the annual cycle. And evidence becomes structured: FedRAMP JSON schemas (requirement FRC-CSO-JSN on Casco's FedRAMP page) point to findings and test data that can be incorporated into a FedRAMP reporting workflow, rather than pasted from a PDF.

The vendor question changes accordingly: you are buying a recurring stream of structured, reproducible evidence that slots into your certification package.

VDR and VER: The Two Requirements That Matter Most

VDR and VER are FedRAMP's new vulnerability rules, and they are the heart of the migration.

VDR: Find it. Fix it. VDR covers continuous penetration testing, vulnerability report triage, and retesting after fixes. Relevant requirement IDs include VDR-CSO-DET (detection), VDR-CSO-DAC, VDR-CSO-RES, and VDR-TFR-PVR. The operational bar is high: findings need triage, and fixes need verified retests.

VER: Prove the risk. VER covers exploitability validation, internet-reachability evidence, and reproducible findings for reporting. Requirement IDs include VER-EVA-ELX, VER-EVA-EIR, VER-EVA-EPA, VER-EVA-AIA, VER-RPT-PER, and VER-TFR-MHR. VER also requires providers to assume exploitation can be automated unless they have evidence otherwise, which raises the bar for how thoroughly a vulnerability must be validated.

One VER nuance is easy to miss: a vulnerable component behind a firewall can still be internet-reachable, because internet-originated input can reach internal components through an application or API (VER-EVA-EIR). A vendor that only tests exposed endpoints will understate your risk.

How to Evaluate a Vendor's 20x Evidence Support

Ask four things.

1. Which requirement IDs do you map to? A credible vendor names the requirements its evidence supports. Casco's FedRAMP page lists the VDR, VER, and FRC requirement IDs above, plus roughly 26 KSIs such as KSI-CMT-VTD and KSI-SVC-VCM, with a headline of evidence for up to 42% of FedRAMP 20x controls. Per class, that is 26 of 66 requirements for Class A, and 87 of 203 for Classes B and C.

2. Is the evidence reproducible and structured? VER asks for reproducible findings. A vendor should be able to replay the original attack to verify a fix, and produce structured finding and test data rather than prose. Casco's continuous testing supports this: 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.

3. Does the vendor itself operate under 20x? A vendor certified via FedRAMP 20x has lived the evidence model it sells against. 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.

4. What stays on your side of the line? VDR/VER support is shared responsibility. Even with a vendor, you still define scope and coverage, assign the Potential Agency Impact N-rating (PAIN), ship fixes within required timelines, combine the vendor's evidence with other detection sources, maintain the persistent and monthly reports, and complete the Security Decision Record and the independent assessment. A vendor supplements your evidence; it does not replace your 3PAO or your authorization decisions.

Why Casco Fits This Decision

Casco is an agentic penetration testing platform, and its government offering covers web apps, APIs, cloud infrastructure, mobile applications, browser extensions, internal and external networks, and AI applications, agents, LLM workflows, and MCP servers. That coverage matters for 20x, because the evidence requirements reach internal components and AI features, not just the public perimeter.

The case is straightforward: the migration deadline is December 7, 2026, and evidence for up to 42% of FedRAMP 20x controls is the difference between assembling evidence by hand and generating it continuously. Casco is certified via FedRAMP 20x itself, provides VDR/VER evidence, and can start black-box testing in under 10 minutes. If you are mid-migration, book a FedRAMP demo and ask to see the requirement-level evidence mapping.

Frequently Asked Questions

What is the deadline to migrate from Rev5 to 20x? Under NTC-0014, FedRAMP Certified services 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 has its certification revoked.

What is the difference between VDR and VER? 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. In Casco's framing: VDR is "Find it. Fix it." and VER is "Prove the risk."

How much of the 20x requirements can a testing vendor cover? Casco provides evidence for up to 42% of FedRAMP 20x controls: 26 of 66 requirements for Class A, and 87 of 203 for Classes B and C. No vendor covers everything. You still own scope, the PAIN rating, fix timelines, reporting, the Security Decision Record, and the independent assessment.

Does using a testing vendor replace our 3PAO assessment? No. Casco's evidence supports the assessment; it does not replace the independent assessor. Each agency also makes its own authorization and purchasing decision, and FedRAMP certification provides a reusable security package rather than authorization at any specific agency.

Conclusion

Moving from Rev5 to 20x is not a paperwork swap. It changes security evidence from annual documents to continuous, machine-readable, reproducible proof, and puts VDR/VER at the center of certification maintenance. When you evaluate security testing vendors, ask which requirement IDs they map to, whether their findings replay and export into your reporting workflow, and whether they operate under 20x themselves. Casco answers all three: it is FedRAMP 20x Class A certified, provides evidence for up to 42% of FedRAMP 20x controls, and can start testing in under 10 minutes. With the December 7, 2026 deadline in view, the vendors that can produce 20x evidence today are the ones worth shortlisting.

Related Articles