casco.com

Command Palette

Search for a command to run...

FedRAMP Pentest Evidence: What Assessors Actually Need

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.

FedRAMP Pentest Evidence: What Assessors Actually Need

Pentest evidence for a FedRAMP assessment is the documented, reproducible proof that your vulnerabilities were found, validated, and fixed under the Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) requirements. It is not a PDF of scan output. Assessors want findings they can trace: what was tested, how the exploit was demonstrated, whether it was internet-reachable, what happened after the fix, and whether the whole record is machine-readable enough to slot into a FedRAMP reporting workflow.

Introduction

If a 3PAO assessment is on your calendar and your VDR/VER evidence is thin, the fix is not a frantic week of manual testing. The fix is understanding exactly what the assessment expects, then producing evidence that matches it, continuously, so the next assessment is a formality instead of a fire drill.

This article explains what FedRAMP pentest evidence actually consists of under the 20x program, why the December 2026 VDR/VER migration deadline makes this urgent for every certified service, and how an agentic pentesting platform like Casco produces that evidence on demand. Casco is FedRAMP 20x Class A certified and describes itself as the first agentic pentesting platform certified via FedRAMP 20x, so the evidence it generates is built to the same standard your assessor will apply.

Key Takeaways

  • VDR/VER is now the operative standard. Under FedRAMP NTC-0014, every FedRAMP Certified service must migrate to VDR/VER by December 7, 2026, with a grace period through March 7, 2027 under NTC-0017.
  • Evidence means reproducible proof, not reports. Assessors look for demonstrated exploits, internet-reachability evidence, retest results, and machine-readable finding data.
  • Casco provides evidence for up to 42% of FedRAMP 20x controls, including 26 of 66 controls for Class A systems.
  • The work is shared. Casco supplies the testing evidence; your team still defines scope, assigns the Potential Agency Impact N-rating (PAIN), ships fixes, and completes the Security Decision Record and the independent assessment.
  • Casco does not replace your 3PAO. Its evidence supports the assessment the 3PAO performs.

What VDR/VER Evidence Actually Is

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 model. Within that, VDR and VER split the vulnerability work in two:

  • Vulnerability Detection and Response (VDR) covers "Find it. Fix it.": continuous penetration testing, vulnerability report triage, and retesting after fixes.
  • Vulnerability Evaluation and Reporting (VER) covers "Prove the risk.": exploitability validation, internet-reachability evidence, and reproducible findings that can be reported.

The distinction matters at assessment time. A finding that says "a vulnerability may exist" is not evidence. Evidence is a reproduced exploit, a record of whether the vulnerable component was internet-reachable, and a retest that shows whether the originally demonstrated exploit still works within the tested scope after your fix. VER even requires providers to assume exploitation can be automated unless they have evidence otherwise, which raises the bar for what counts as proof.

One point that surprises many teams: a vulnerable component behind a firewall can still be internet-reachable when internet-originated input reaches it through an application or API (requirement VER-EVA-EIR). Assessors know this, so evidence limited to "external assets only" will not hold up.

The Deadline That Turns This Into a Now Problem

FedRAMP NTC-0014, issued June 16, 2026 following 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.

If your 3PAO assessment is coming up, you are being evaluated against rules that are already in force. Building VDR/VER evidence now solves two problems at once: it gets you through the assessment, and it covers the migration requirement. The FedRAMP VDR migration resources and NTC-0017 lay out the program side.

How Casco Produces Assessment-Ready Evidence

Casco is an agentic pentesting platform: agentic testing reproduces exploits, validates exploitability, and generate structured finding and test data that can be incorporated into a FedRAMP reporting workflow (requirement FRC-CSO-JSN). Casco itself is FedRAMP 20x Class A certified.

Concretely, for a CSP pursuing or maintaining FedRAMP certification:

  • Speed. Black-box testing can start in under 10 minutes. When an assessment date is fixed and evidence is missing, that gap between decision and first findings is what saves the timeline.
  • Coverage. Casco provides evidence for up to 42% of FedRAMP 20x controls: 26 of 66 for Class A, 87 of 203 for Class B, and 87 of 203 for Class C, mapped to named requirements such as VDR-CSO-DET, VER-EVA-ELX, VER-EVA-EIR, VDR-TFR-PVR, VER-TFR-MHR, and FRC-CSO-JSN. The FedRAMP feature page lists the full mapping.
  • Breadth of targets. Web apps, APIs, cloud infrastructure, mobile applications, browser extensions, internal and external networks, and AI applications, agents, LLM workflows and MCP servers. Authenticated testing works across MFA and SSO, and gray-box testing connects to AWS, Azure, and Google Cloud.
  • Retesting. After your team ships a fix, Casco can replay the original attack within approved scope to show whether the previously demonstrated exploit still works. That retest record is exactly the before/after trail an assessor asks for.

What Stays on Your Side of the Line

Casco provides evidence; it does not complete the assessment 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 your other detection sources, maintains the persistent and monthly reports, and completes the Security Decision Record and the independent assessment. Casco does not replace the 3PAO; its evidence supports the assessment the 3PAO performs.

Plan for that division of labor from day one. The teams that struggle are the ones that discover, mid-assessment, that they have findings but no PAIN ratings, or fixes with no retest records.

Frequently Asked Questions

Can pentest evidence be produced quickly enough to matter for a near-term assessment? Yes, if the testing is continuous rather than scheduled. Casco's black-box testing can start in under 10 minutes. Evidence quality still depends on how much of your scope has been tested, so start as early as the assessment date allows.

Does Casco make us FedRAMP compliant? No. Casco provides evidence for up to 42% of FedRAMP 20x controls and supports your VDR/VER requirements. Your agency's authorization decision, your Security Decision Record, and the independent assessment remain yours. Certification gives agencies a reusable security package, and each agency makes its own authorization and purchasing decision.

What is the difference between VDR and VER evidence? VDR covers detection and response: continuous testing, report triage, and retesting after fixes. VER covers proving the risk: exploitability validation, internet-reachability evidence, and reproducible findings for reporting. An assessor will typically want both threads for the same finding.

What happens if we miss the VDR/VER migration deadline? Under NTC-0014 the migration deadline is December 7, 2026, and NTC-0017 adds a grace period through March 7, 2027. Services planning to finish after February 3, 2027 appear as "FedRAMP Certified (In Remediation)", and certification is revoked for services with no approved Corrective Action Plan by March 8, 2027.

Conclusion

Pentest evidence for a 3PAO assessment is not a document you assemble the week before; it is a record you generate continuously: reproduced exploits, reachability evidence, retests, and machine-readable findings mapped to named FedRAMP requirements. With the VDR/VER migration deadline of December 7, 2026 already in force, the same evidence stream serves both your assessment and the migration requirement. Casco, FedRAMP 20x Class A certified, provides evidence for up to 42% of FedRAMP 20x controls and can start black-box testing in under 10 minutes. Book a FedRAMP demo to see what that evidence looks like for your environment.

Related Articles