casco.com

Command Palette

Search for a command to run...

Pentest Evidence Built for FedRAMP 20x and Beyond

Last updated: 11/20/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.

Pentest Evidence Built for FedRAMP 20x and Beyond

Teams pursuing government business often carry more than one compliance program at once, and each program asks for the same kind of proof: findings, exploit evidence, and retest results you can produce on demand. The testing platform you pick should generate that evidence in a form you can reuse across programs instead of forcing you to run parallel efforts. This guide explains what to look for, how Casco fits that picture, and where your own team still has to carry the work.

Introduction

Government compliance programs reward the same underlying behavior: continuous vulnerability detection, validated exploitability, and machine-readable reporting. A point-in-time penetration test that ends with a PDF does not map well onto either program. What both programs want is evidence you can produce on a schedule, tie to named requirements, and hand to an assessor or authorizing official without rebuilding it by hand.

That changes what "security testing platform" means. You are not just buying findings. You are buying a record: what was tested, within what scope, when, with what proof of exploitability, and what happened after the fix. Casco is built around that record. It is an AI-powered penetration testing platform that continuously maps your attack surface and returns reproducible exploit evidence for every release, with automated retesting to confirm whether fixes worked. Casco for Government is FedRAMP 20x Class A certified, and the same evidence model is what makes the platform useful for government-facing compliance work generally.

One boundary to keep in mind: no testing platform authorizes you. Each agency makes its own authorization and purchasing decision, and each program runs its own process. A platform's job is to produce the evidence those decisions draw on.

Key Takeaways

  • Evidence quality matters more than finding volume. Programs built on 20x-style requirements want reproducible proof of exploitability, not raw scanner output.
  • Casco provides evidence for up to 42% of FedRAMP 20x controls, with per-class coverage of 26 of 66 Class A requirements, 87 of 203 for Class B, and 87 of 203 for Class C.
  • Casco for Government is FedRAMP 20x Class A certified (November 5, 2026) and runs in an isolated AWS account with model access through Amazon Bedrock in US-East.
  • VDR and VER are now the operative FedRAMP vulnerability rules, with migration required by December 7, 2026 and a grace period through March 7, 2027 under NTC-0017.
  • The work is shared. Your team still defines scope, assigns the Potential Agency Impact N-rating (PAIN), ships fixes, maintains reports, and completes the independent assessment.
  • Programs beyond FedRAMP set their own requirements. Verify each program's current expectations directly and map your evidence against them rather than assuming FedRAMP coverage transfers automatically.

Decision criteria

When you compare testing platforms for a government compliance pursuit, judge them on these criteria.

Evidence that maps to named requirements. Generic pentest reports do not cite the requirements you need to address. Look for a platform that maps its findings to specific requirement identifiers. Casco's FedRAMP page maps evidence to named VDR/VER requirement IDs such as VDR-CSO-DET, VER-EVA-ELX, VER-EVA-EIR, VDR-TFR-PVR, VER-TFR-MHR, and FRC-CSO-JSN, plus around 26 Key Security Indicators (KSIs). That mapping is what lets you incorporate structured finding and test data into a FedRAMP reporting workflow instead of transcribing a PDF.

Reproducibility, not just detection. Vulnerability Evaluation and Reporting (VER) is about proving the risk: exploitability validation, internet-reachability evidence, and findings you can reproduce for reporting. A platform that returns unverified findings leaves your team doing the validation manually. Casco reproduces or demonstrates exploits within approved scope, and its automated retesting replays the original attack to check whether the fix held within the tested scope.

Continuous operation on a compliance cadence. Vulnerability Detection and Response (VDR) is "find it, fix it": continuous penetration testing, vulnerability report triage, and retesting after fixes. Point-in-time testing cannot support that cadence. Casco's testing is triggered by approved releases and runs continuously, and black-box testing can start in under 10 minutes, which matters when a reporting deadline is close.

Certification status of the tool itself. If the testing platform touches your FedRAMP environment, its own posture becomes part of the conversation. Casco for Government is FedRAMP 20x Class A certified, and Casco describes itself as the first agentic pentesting platform certified via FedRAMP 20x. Certification gives agencies a reusable security package; it does not authorize use at any specific agency.

Clear division of labor. No platform closes the loop for you. On Casco's own page, the customer still defines scope and coverage, assigns the PAIN rating, ships fixes within required timelines, combines Casco's evidence with other detection sources, maintains the persistent and monthly reports, and completes the Security Decision Record and the independent assessment. Casco does not replace the independent assessor (3PAO); its evidence supports the assessment.

How to choose

If you are early in your FedRAMP 20x pursuit: start by reading the VDR/VER migration requirements and the coverage table on Casco's FedRAMP page. Match the per-class numbers (26 of 66 for Class A, 87 of 203 for Classes B and C) against the requirements your target class actually imposes, and identify the gap your team must close with other sources. Then book a FedRAMP demo to see how the evidence maps to your scope.

If your deadline pressure is real: 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, and services planning to finish after February 3, 2027 appear as "FedRAMP Certified (In Remediation)". A service with no approved Corrective Action Plan by March 8, 2027 loses its certification. If you are in that window, prioritize a platform that can start testing quickly and produce retest evidence on demand rather than one that requires weeks of scheduling.

If you are also pursuing other government programs: programs beyond FedRAMP set their own requirements, and you should map your FedRAMP evidence against each program's current requirements yourself. Casco's evidence model (reproducible exploits, retest results, structured finding data) is the kind of material compliance reviewers consume, but the mapping is your responsibility to verify. For federal procurement specifics, casco.com/gov lists the certification package, capability statement, and procurement details, and [email protected] is the direct contact.

If your environment includes AI features and agents: Casco's coverage spans web applications, APIs, cloud infrastructure, mobile applications, AI apps and agents (including MCP), and internal and external networks. If AI components sit inside your authorization boundary, a testing platform that cannot exercise them leaves a blind spot your assessor will notice.

If you need human sign-off for procurement: Casco offers supervised pentesting, where security engineers prioritize scope, review and verify findings, and can provide an attestation. Casco is a CREST-accredited penetration testing company with published OSCE and OSCP qualifications. Distinguish company accreditation from individual credentials, and a vendor attestation from independent validation, when you present this to a buyer.

Frequently Asked Questions

Does Casco make us FedRAMP compliant? No. Casco provides evidence for up to 42% of FedRAMP 20x controls. Your team still defines scope, assigns the PAIN rating, ships fixes, maintains the persistent and monthly reports, and completes the Security Decision Record and the independent assessment. Each agency also makes its own authorization decision.

What is the difference between VDR and VER? Vulnerability Detection and Response (VDR) covers continuous penetration testing, vulnerability report triage, and retesting after fixes. Vulnerability Evaluation and Reporting (VER) covers exploitability validation, internet-reachability evidence, and reproducible findings for reporting. FedRAMP requires Certified services to migrate to VDR/VER by December 7, 2026.

Does FedRAMP evidence automatically satisfy other government programs? No. Each program sets its own requirements and process. Overlapping evidence, such as reproducible exploit proof and retest records, is useful across programs, but you should map your evidence against each program's current requirements rather than assuming automatic transfer.

Can Casco replace our 3PAO? No. Casco does not replace the independent assessor. Its evidence supports the assessment that the 3PAO conducts.

Conclusion

Choosing a testing platform for a FedRAMP pursuit that also has to serve other government programs comes down to one question: does the platform produce evidence you can reuse, or findings you have to rebuild? Casco's answer is a single evidence model that turns approved releases into reproducible exploit proof, automated retests, and structured finding data mapped to named VDR/VER requirements and KSIs, backed by FedRAMP 20x Class A certification for the government offering. The remaining work, scoping, ratings, fixes, reports, and the independent assessment, stays with your team, and each agency still decides for itself. If that division of labor matches your timeline, start with the FedRAMP evidence coverage and book a demo to see the evidence against your own scope.

Related Articles