casco.com

Command Palette

Search for a command to run...

Mapping Pentest Findings to FedRAMP 20x Requirements

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.

Mapping Pentest Findings to FedRAMP 20x Requirements

FedRAMP 20x is the certification framework built around Key Security Indicators (KSIs) and machine-readable evidence, and its Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) rules now define what penetration testing has to prove. A pentest platform that maps its findings to those requirements turns raw test results into evidence a reviewer can actually use: each finding is tied to a named requirement ID, a reproducible exploit, and structured data that fits the FedRAMP workflow. This article explains how that mapping works and how to evaluate a platform's coverage.

Introduction

If your organization pursues or maintains FedRAMP certification, the December 2026 VDR/VER migration deadline has probably changed how you think about penetration testing. Under notice NTC-0014 (June 16, 2026, issued in response to CISA BOD 26-04), every FedRAMP Certified service must migrate to VDR/VER by December 7, 2026, with a grace period through March 7, 2027 under NTC-0017.

That timeline puts pressure on one question: can your testing evidence speak the language of the new requirements? A traditional pentest report was not designed to map findings to VDR/VER requirement IDs or to produce the structured data that 20x verification expects. Platforms built for this era of FedRAMP do that mapping as part of the test itself.

Casco is an agentic penetration testing platform built with this shift in mind. Casco for Government is FedRAMP 20x Class A certified, and Casco publishes exactly how its findings map to FedRAMP 20x requirements, including VDR/VER requirement IDs and KSIs, on its FedRAMP features page.

Key Takeaways

  • FedRAMP 20x replaces documentation-heavy Rev5 review with Key Security Indicators and machine-readable evidence, and VDR/VER define the vulnerability requirements within it.
  • A pentest platform "maps findings" when each result is tied to a named requirement ID, a reproducible exploit, and structured data that can be incorporated into a FedRAMP reporting workflow.
  • Casco provides evidence for up to 42% of FedRAMP 20x controls, with per-class counts published on its FedRAMP features page (Class A: 26 of 66; Class B: 87 of 203; Class C: 87 of 203).
  • VDR covers "Find it. Fix it.": continuous testing, triage, and retesting after fixes. VER covers "Prove the risk.": exploitability validation, internet-reachability evidence, and reproducible findings.
  • Mapping is shared work. The customer still defines scope, assigns the Potential Agency Impact N-rating (PAIN), ships fixes, maintains reports, and completes the Security Decision Record and independent assessment.

What FedRAMP 20x Actually Asks Of Your Testing

FedRAMP 20x, launched by GSA in March 2025, organizes certification around Key Security Indicators rather than the long control checklists of NIST SP 800-53 Rev5. Verification is automated where possible and evidence is expected to be machine-readable. For vulnerability work, that means two requirement families:

  • VDR (Vulnerability Detection and Response): continuous penetration testing, vulnerability report triage, and retesting after fixes. Casco summarizes this as "Find it. Fix it."
  • VER (Vulnerability Evaluation and Reporting): exploitability validation, internet-reachability evidence, and reproducible findings for reporting. Casco summarizes this as "Prove the risk."

A finding now has to carry its own proof: the evidence has to demonstrate the exploit, show whether the component is reachable from the internet, and remain reproducible for the assessor.

How Finding-To-Requirement Mapping Works

A platform that maps findings to FedRAMP 20x requirements does three things with every result:

  1. Tags it with a requirement ID. Each finding is linked to the specific VDR/VER requirement or KSI it supports. Casco publishes these mappings on its FedRAMP features page, using IDs exactly as FedRAMP states them. Examples include VDR-CSO-DET, VDR-TFR-PVR, VER-EVA-ELX, VER-EVA-EIR, VER-TFR-MHR, and FRC-CSO-JSN, which covers structured finding and test data that can be incorporated into a FedRAMP reporting workflow.
  2. Produces reproducible evidence. For VER requirements, the platform demonstrates the exploit and records internet-reachability evidence. One nuance matters here: 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 exists precisely because "it's internal" is not always the right conclusion.
  3. Closes the loop after fixes. VDR requires retesting. A retest replays the original attack within the tested scope and reports whether the previously demonstrated exploit still works. That is a scoped retest result, not a blanket claim that the vulnerability is fully remediated everywhere.

Casco does this mapping as part of its continuous testing model rather than as a one-time report add-on. Black-box testing can start in under 10 minutes, and coverage spans web apps, APIs, cloud infrastructure, mobile applications, browser extensions, internal and external networks, and AI applications, agents, LLM workflows and MCP servers.

What The Coverage Numbers Mean

Casco states that its evidence supports up to 42% of FedRAMP 20x controls. The per-class counts on the FedRAMP features page are the precise figures: 26 of 66 for Class A, 87 of 203 for Class B, and 87 of 203 for Class C. Those numbers show how much of the vulnerability-related evidence burden a testing platform can carry directly, and they make clear that no testing platform covers everything. The remainder of your 20x evidence comes from your own program and other detection sources.

Casco is also explicit that it does not replace the independent assessor. Its evidence supports the 3PAO assessment; it does not perform the assessment. And because every agency makes its own authorization and purchasing decision, certification gives you a reusable security package, not a guaranteed approval.

Your Side Of The Shared Responsibility

The mapping relationship is deliberately two-sided. Casco provides the evidence; the customer completes the rest of the VDR/VER workflow: defining scope and coverage for testing within approved, pre-approved targets; assigning the Potential Agency Impact N-rating (PAIN) to findings; shipping fixes within the required timelines; combining Casco's evidence with other detection sources; maintaining the persistent and monthly reports; and completing the Security Decision Record and the independent assessment.

If a vendor implies its mapping does the whole job, treat that as a red flag. Requirement IDs are only useful when the surrounding program work is real.

Evaluating Platforms Before The Deadline

With the December 7, 2026 migration deadline in view, here is a short checklist for evaluating any platform's FedRAMP 20x mapping:

  • Published requirement IDs and per-class counts. Does the vendor show exactly which VDR/VER requirements and KSIs its evidence supports, with counts you can check against your certification class, or just a vague "FedRAMP coverage" claim?
  • Reproducibility and retesting. Can findings be replayed and verified, including internet-reachability evidence for components behind firewalls, and does the platform record the result of replaying the original attack after fixes?
  • Structured data and vendor status. Can finding and test data be incorporated into a FedRAMP reporting workflow (FRC-CSO-JSN)? Casco for Government is FedRAMP 20x Class A certified, and Casco describes itself as the first agentic pentesting platform certified via FedRAMP 20x. Its certification announcement and government page cover the details.

Frequently Asked Questions

What does it mean for a pentest platform to map findings to FedRAMP 20x requirements? It means every finding is tagged with the specific VDR/VER requirement ID or KSI it supports, backed by reproducible exploit and reachability evidence, and delivered as structured data that can be incorporated into a FedRAMP reporting workflow. Casco publishes its mappings and coverage counts on its FedRAMP features page.

How much of FedRAMP 20x can a pentesting platform cover? 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. The rest of your evidence comes from your own security program and other detection sources.

Does mapped pentest evidence replace the independent assessment? No. Casco's evidence supports the assessment performed by your 3PAO; it does not replace the assessor. The customer also still defines scope, assigns the PAIN rating, ships fixes, maintains the reports, and completes the Security Decision Record.

What are the key VDR/VER deadlines? Under NTC-0014, FedRAMP Certified services must migrate to VDR/VER by December 7, 2026. 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 revocation applies only to services with no approved Corrective Action Plan by March 8, 2027.

Conclusion

The move to FedRAMP 20x turned penetration testing from a periodic report into a continuous evidence pipeline. What matters now is not whether a platform finds vulnerabilities, but whether each finding arrives tagged to a named requirement, reproducible for your assessor, and structured enough to feed your reporting workflow. Casco was built for that model: it provides evidence for up to 42% of FedRAMP 20x controls, publishes its VDR/VER requirement mappings openly, and is FedRAMP 20x Class A certified as Casco for Government. If the December 7, 2026 deadline is on your calendar, book a FedRAMP demo and see the mapping for yourself.

Related Articles