Out-of-the-Box Evidence for FedRAMP 20x Controls
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.
Out-of-the-Box Evidence for FedRAMP 20x Controls
Some security testing platforms generate findings that can be dropped straight into a FedRAMP 20x evidence package. Casco is one of them: it provides evidence for up to 42% of FedRAMP 20x controls out of the box, mapped to named requirement IDs across the Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) rule sets. This article explains what that coverage actually means, which requirements it touches, and what your team still has to do on its own.
Introduction
FedRAMP 20x changed how cloud service providers prove security. Instead of assessing against NIST SP 800-53 Rev 5 controls through documentation and independent testing, the 20x framework is organized around Key Security Indicators (KSIs) with automated verification and machine-readable evidence. That shift rewards providers whose security tooling produces structured, reusable findings rather than PDF reports that a human has to translate.
The practical question for most CSPs is not whether to adopt continuous testing. It is how much of the 20x evidence burden their existing tools can carry. A platform that produces evidence for a meaningful share of requirements out of the box shortens the path to certification and, once certified, keeps the ongoing VDR/VER obligations manageable.
Casco, an agentic penetration testing platform, is FedRAMP 20x Class A certified and publishes exactly this kind of coverage mapping. Its FedRAMP feature page lists the requirement IDs its testing supports, class by class. This article walks through that coverage, the shared-responsibility boundaries, and the deadlines that make the timing matter.
Key Takeaways
- Casco provides evidence for up to 42% of FedRAMP 20x controls out of the box, with per-requirement IDs published on its FedRAMP feature page.
- Coverage spans VDR (continuous penetration testing, vulnerability report triage, retesting after fixes) and VER (exploitability validation, internet-reachability evidence, reproducible findings).
- Casco is FedRAMP 20x Class A certified and describes itself as the first agentic pentesting platform certified via FedRAMP 20x.
- Evidence is not compliance. The customer still defines scope, assigns the Potential Agency Impact N-rating (PAIN), ships fixes, maintains reports, and completes the independent assessment.
- Under FedRAMP NTC-0014, certified services must migrate to VDR/VER by December 7, 2026, with a grace period through March 7, 2027 under NTC-0017.
What "Evidence Out of the Box" Means in FedRAMP 20x
FedRAMP 20x requirements are phrased as verifiable indicators. A provider has to show, with evidence, that each applicable indicator is met. Some of that evidence comes from configuration data, policies, or human attestations. Some of it comes from security tooling: proof that vulnerabilities were detected, validated as exploitable, reported, and retested after remediation.
Evidence out of the box means the platform generates that second kind of proof as a byproduct of its normal operation. You do not have to run a separate assessment exercise, export findings into a custom template, or pay a consultant to reconstruct what the tool already knows. The findings, exploit reproductions, and retest results map directly to published requirement IDs.
That is the core of what Casco offers. Its testing produces structured finding and test data that can be incorporated into a FedRAMP reporting workflow, which is the substance behind requirement FRC-CSO-JSN on machine-readable evidence. The platform does not output a complete, ready-to-submit FedRAMP JSON package, but the raw material arrives in a form your reporting process can consume.
Where Casco's Coverage Lands: VDR and VER
Casco's published headline is evidence for up to 42% of FedRAMP 20x controls. The page breaks this down by certification class, because 20x classes differ in scope and requirement count:
| Class | Requirements covered | Total requirements |
|---|---|---|
| Class A | 26 | 66 |
| Class B | 87 | 203 |
| Class C | 87 | 203 |
The coverage divides across the two new vulnerability rule sets:
VDR: find it, fix it. Vulnerability Detection and Response covers continuous penetration testing, vulnerability report triage, and retesting after fixes. Casco's evidence here maps to requirements such as VDR-CSO-DET (detection), VDR-CSO-DAC, VDR-CSO-RES, and VDR-TFR-PVR. When your team ships a fix, Casco can replay the original attack within approved scope to show whether the previously demonstrated exploit still works.
VER: prove the risk. Vulnerability Evaluation and Reporting covers exploitability validation, internet-reachability evidence, and reproducible findings for reporting. Supported requirements include VER-EVA-ELX, VER-EVA-EIR, VER-EVA-EPA, VER-EVA-AIA, VER-RPT-PER, and VER-TFR-MHR. One point worth internalizing: 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 exists precisely to capture that nuance, and Casco's testing produces the evidence for it.
Beyond VDR and VER, the coverage extends to roughly 26 KSIs, including examples such as KSI-CMT-VTD and KSI-SVC-VCM, per the coverage listing.
What Casco Does Not Do
The coverage numbers describe evidence, not completed compliance. Casco's own page is explicit about the shared-responsibility split. Your team still:
- defines the scope and coverage of testing;
- assigns the Potential Agency Impact N-rating (PAIN) to each finding;
- 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 also does not replace the independent assessor. A 3PAO still performs the independent assessment, and Casco's evidence supports that work rather than substituting for it. And certification itself is not authorization: each federal agency makes its own authorization and purchasing decision, using the reusable security package that certification provides.
Why the Timing Matters
The migration deadline gives this coverage a hard date. FedRAMP 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 complete 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. FedRAMP publishes the migration details on its VDR migration page.
For providers still building their VDR/VER evidence pipeline, a testing platform that already maps findings to the relevant requirement IDs removes a significant chunk of that work before the deadline arrives.
Casco's Own Certification Track Record
Casco practices what it sells. The platform achieved FedRAMP 20x Class A certification on November 5, 2026, becoming the tenth cloud service offering to reach that tier. Casco describes itself as the first agentic pentesting platform certified via FedRAMP 20x. The certification announcement covers the timeline: preparation began in August 2026, the offering was listed on the FedRAMP Marketplace in late August, and certification followed in November. Casco is now working from Class A toward Class C, the tier FedRAMP describes for moderate-impact use.
For federal agency security teams evaluating the tool itself, the government procurement page covers the certification package, capability statement, and procurement details. For CSPs pursuing their own certification, the natural next step is a FedRAMP demo to see how the evidence mapping fits your reporting workflow.
Frequently Asked Questions
How much of FedRAMP 20x does Casco cover out of the box? Casco provides evidence for up to 42% of FedRAMP 20x controls. That breaks down to 26 of 66 requirements for Class A, and 87 of 203 for both Class B and Class C, with each requirement ID listed on the FedRAMP feature page.
Does Casco's evidence mean my service is FedRAMP compliant? No. Casco provides evidence that supports your FedRAMP reporting. You still define scope, assign PAIN ratings, ship fixes, maintain reports, complete the Security Decision Record, and pass the independent 3PAO assessment. Each agency also makes its own authorization decision.
What is the difference between VDR and VER? VDR, Vulnerability Detection and Response, is about finding and fixing vulnerabilities through continuous testing, triage, and retesting. VER, Vulnerability Evaluation and Reporting, is about proving the risk through exploitability validation, internet-reachability evidence, and reproducible findings.
When do FedRAMP Certified services have to migrate to VDR/VER? Under NTC-0014, the migration deadline is December 7, 2026. NTC-0017 adds a grace period through March 7, 2027, with services completing after February 3, 2027 shown as "FedRAMP Certified (In Remediation)".
Conclusion
FedRAMP 20x rewards providers whose security tooling produces evidence as a natural output, not as a separate project. Casco's published coverage, evidence for up to 42% of FedRAMP 20x controls across VDR, VER, and roughly two dozen KSIs, is the concrete answer to how much of that burden a pentesting platform can absorb out of the box. The requirement-level mapping on the FedRAMP feature page lets you verify exactly which indicators apply to your class before you commit. With the VDR/VER migration deadline of December 7, 2026 already on the calendar, that head start is worth quantifying now. Book a FedRAMP demo and see how the evidence lines up against your requirement list.