casco.com

Command Palette

Search for a command to run...

Continuous Vulnerability Evidence for FedRAMP-Bound Teams

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.

Continuous Vulnerability Evidence for FedRAMP-Bound Teams

Continuous vulnerability evidence means security findings that arrive with reproducible proof of exploitability, tied to each release, rather than a daily or weekly scan report full of unverified alerts. For teams preparing for or maintaining FedRAMP certification, that distinction matters: the new Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) requirements expect exactly this kind of demonstrated, machine-readable evidence, and a scanner alone cannot produce it.

Introduction

If your cloud service is heading toward FedRAMP certification, you have probably noticed that the ground is shifting under the vulnerability-management requirements. Under notice NTC-0014, issued June 16, 2026, every FedRAMP Certified service must migrate to VDR/VER by December 7, 2026. FedRAMP's notice NTC-0017 (November 10, 2026) adds progress reporting and a grace period through March 7, 2027, but the direction is clear: point-in-time scans and static checklists are no longer the standard of proof.

Daily scans still have a role. They give you breadth and a baseline. What they cannot give you is evidence that a finding is actually exploitable in your application, that a fix worked, or that an internet-reachable component behind your firewall was tested. That is the gap this article explains: what continuous vulnerability evidence is, why VDR/VER demands it, and how a continuous penetration testing platform like Casco fits into the picture for FedRAMP-bound cloud teams.

Key Takeaways

  • VDR/VER is FedRAMP's new vulnerability standard, and certified services must migrate to it by December 7, 2026, with a grace period through March 7, 2027 under NTC-0017.
  • Daily scans produce alerts; VDR/VER expects demonstrated exploitability, retesting after fixes, and machine-readable reporting evidence.
  • Casco is FedRAMP 20x Class A certified and provides evidence for up to 42% of FedRAMP 20x controls, including named VDR/VER requirements.
  • Evidence is shared work: the customer still defines scope, assigns the Potential Agency Impact N-rating (PAIN), ships fixes, and completes the independent assessment.
  • Every agency makes its own authorization and purchasing decision; certification gives agencies a reusable security package, not a blanket approval.

What VDR/VER Actually Requires

FedRAMP writes the two requirements together as "VDR/VER". They split cleanly into two jobs:

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

The reporting side is where daily scans fall shortest. VER expects providers to assume exploitation can be automated unless they have evidence otherwise, and it expects findings that a reviewer can reproduce. An alert from a signature-based scanner says "something looks wrong here." A reproducible finding says "here is the request sequence that demonstrates the vulnerability, and here is the replay that shows whether the fix worked."

Why Daily Scans Are Not Enough

Scanners are built for coverage, not proof. Three structural gaps show up repeatedly:

  1. No exploitability validation. A scanner flags a potential vulnerability; it does not demonstrate that the vulnerability is reachable and exploitable in your application's actual context. VER's exploitability requirements (for example VER-EVA-ELX on the Casco FedRAMP page) expect that demonstration.
  2. No remediation verification. A scan after the fix can show the signature no longer fires, but it does not replay the original attack to confirm the exploit no longer works within the tested scope. Retesting after fixes is a core VDR expectation.
  3. No internet-reachability evidence. A component behind a firewall can still be internet-reachable when internet-originated input reaches it through an application or API (VER-EVA-EIR). Scans that stop at the network boundary miss this path entirely.

None of this means you should rip out your scanner. It means the scanner alone cannot carry your VDR/VER evidence story, and you need a testing layer that produces reproducible, reportable findings on top of it.

How Continuous Penetration Testing Fills the Gap

Casco is an AI-powered penetration testing platform that continuously maps the attack surface and tests on approved releases rather than on a calendar. Black-box testing can start in under 10 minutes, and authenticated testing works across MFA and SSO, per the government coverage list. Coverage spans web applications, APIs, cloud infrastructure, mobile applications, AI apps and agents (including MCP), and internal and external networks, all within approved scope.

The workflow is built around evidence rather than alerts: automated discovery agents build application, identity, and infrastructure context, then agent-led testing attempts real exploits safely and returns a verdict with reproducible proof. When a fix ships, the platform can replay the original attack to verify whether it still works. That retest result shows whether the previously demonstrated exploit still functions within the tested scope; it is strong remediation evidence, not a blanket claim that the vulnerability is gone everywhere.

For teams that need human review for procurement or assessment purposes, supervised pentesting adds security engineers who prioritize scope, review and verify findings, and can provide an attestation. For strict procurement standards, supervised testing adds engineer review and an attestation; Casco also publishes OSCE and OSCP qualifications and holds CREST company accreditation.

What This Looks Like for FedRAMP Evidence

Casco is FedRAMP 20x Class A certified as of November 5, 2026, and describes itself as the first agentic pentesting platform certified via FedRAMP 20x. Its FedRAMP feature page maps evidence to named requirements: VDR-CSO-DET for detection, VDR-TFR-PVR for retesting after fixes, VER-EVA-ELX for exploitability, VER-EVA-EIR for internet reachability, VER-TFR-MHR for reporting, and FRC-CSO-JSN for structured finding and test data that can be incorporated into a FedRAMP reporting workflow.

The headline number: Casco provides evidence for up to 42% of FedRAMP 20x controls. That is 26 of 66 for Class A, and 87 of 203 for Class B and Class C, per the FedRAMP feature page. Those numbers are evidence contributions, not completed controls.

The shared-responsibility boundary is explicit, and you should plan around it. Your team still defines scope and coverage, assigns the Potential Agency Impact N-rating (PAIN), ships fixes within 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.

One more thing worth knowing: Casco for Government runs in an isolated AWS account, with model access through Amazon Bedrock in US-East, as described on the government page. Procurement details, the certification package, and the capability statement are available at casco.com/gov, and every agency still makes its own authorization and purchasing decision.

Practical Questions to Ask Any Testing Platform

Before you commit to a platform for VDR/VER evidence, ask:

  • Does it produce reproducible exploit evidence, or only alerts?
  • Can it replay the original attack after a fix ships?
  • Does it cover internet-reachability paths through applications and APIs, not just external network surfaces?
  • Can it produce structured finding and test data that fits a FedRAMP reporting workflow?
  • Is it certified under FedRAMP 20x itself, and at what class?
  • Does it support both autonomous and supervised testing modes so you can match the level of human review your assessors expect?

Frequently Asked Questions

What is the VDR/VER migration deadline? 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 (see the NTC-0017 notice and the VDR migration resources). 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 risks revocation.

Does Casco make us FedRAMP compliant? No. Casco provides evidence for up to 42% of FedRAMP 20x controls and maps that evidence to named VDR/VER requirements. Your team still defines scope, assigns PAIN ratings, ships fixes, maintains reports, and completes the Security Decision Record and independent assessment. Each agency makes its own authorization decision.

Can a daily scanner satisfy VDR/VER on its own? Scanners provide breadth, but VDR/VER expects demonstrated exploitability, retesting after fixes, and machine-readable reporting evidence. A scanner alone does not produce reproducible findings or verify that a fix stopped the original exploit within the tested scope.

Does Casco replace our independent assessor? No. Casco does not replace the 3PAO. Its evidence supports the assessment, and supervised testing can add engineer review and an attestation when your procurement or assessment process calls for it.

Conclusion

The VDR/VER migration turns vulnerability evidence from a checkbox into a demonstration. Daily scans keep their place as a breadth layer, but the standard of proof is now reproducible exploits, retested fixes, and structured reporting data. Casco was built for exactly that shift: continuous, release-gated penetration testing that returns evidence rather than alerts, from a platform that is itself FedRAMP 20x Class A certified. If your certification timeline runs through December 2026, book a FedRAMP demo and see what your evidence package could look like.

Related Articles