Autonomous Security Testing for AI systems
Casco is your always-on AI red team — built to break your AI agents, apps, and infrastructure before real attackers do.
Trusted by teams building the future of AI
Fast moving AI companies choose Casco over traditional pentesters
Don’t take it from us. See how real teams are using Casco to test smarter and ship faster.
“In a matter of hours, Casco was able to find critical vulnerabilities that our other pentesters couldn't find for months.”
Bryan Chappell, CEO of Scout
“Casco is mission-critical for enterprise deals. We started the security assessment on a Friday and completed the procurement process by Monday.”
Saarth Shah, CEO of SixtyFour
Year-round security instead of once-a-year security
Make security a function of your codebase, and plan a vacation instead
Dec 31Jan 1
VulnerablePentestFix“Secure”VS
Dec 31Jan 1
Human pentester
Vulnerable most of the time.
Casco Automated Security
Always monitored. Always protected
Clear findings — what to fix, and why it matters
You get full context, impact, and verification in one clear report.
Improper JWT Verification Leading to Cross-User Data Exposure in AI Claims Chat.
CRITICALCVSS 9.8
SummaryThe endpoint accepts a client-supplied JWT but does not verify its signature or validate the claim against the authenticated session. An attacker can tamper the field to impersonate another user, causing the backend to fetch and feed that user’s private documents into the LLM, which then leaks sensitive data.
Business impact articulated
Impact!Unauthorized disclosure of PII, health records, and underwriting notes.
!Violation of data-protection regulations (e.g., HIPAA).
!Significant reputational damage and potential legal liability.
Reproduction- Obtain a valid JWT for User A.
- Decode the JWT payload and change the sub claim to User B’s ID.
- Re-encode the token without resigning.
- Send a POST to /claims/chat with the modified JWT in Authorization.
- Observe that the response (LLM summary) includes User B’s documents—confirming the backend never verified the signature or subject claim.
Recommendation- Enforce JWT signature validation on every request using the issuer’s public key.
- Ensure the sub claim matches the authenticated user context before data retrieval.
- Implement per-user authorization checks on document fetch APIs, rejecting mismatched subjects.
- Log and alert on any failed or tampered JWT validations.
Open
Onboard with our forward deployed security engineers
Expert-led onboarding tailored to your stack.
Direct line to your dedicated technical contact.
Scoped access to source code and staging environments.
Guided walkthrough of critical findings.