Case Studies

Security outcomes, not just findings.

Real engagements with engineering teams across fintech, healthcare, and SaaS. Details are anonymized where required by NDA.

SECURE_CODE_REVIEWFintech

Critical authentication bypass in a payments API

Challenge

A Series B payments platform was preparing for SOC 2 Type II certification. Their engineering team had run automated SAST tooling across the codebase and received a clean report. They engaged us for a manual review before their audit window opened.

What we found

We identified a JWT validation flaw in their API gateway that allowed an attacker to forge tokens for any user account by exploiting a missing algorithm enforcement check — a variant of the 'alg: none' attack that their scanner had not flagged because the vulnerable path was behind a feature flag.

Outcome

The vulnerability was patched within 48 hours of disclosure. We provided a remediation code review, confirmed the fix, and delivered a findings report accepted by their SOC 2 auditor. The platform completed certification on schedule.

1 critical

finding missed by SAST

48 hrs

time to patch

SOC 2

certification achieved

THREAT_MODELHealthcare Tech

Threat model for a PHI data pipeline before HIPAA audit

Challenge

A healthcare SaaS company was building a new data ingestion pipeline for patient health information. Their engineering team had strong security instincts but no formal threat modeling process. They needed a structured analysis before the pipeline went to production.

What we found

Our threat model identified three high-severity issues: an insecure direct object reference in the patient record API, a missing audit log for PHI access events, and a privilege escalation path in their internal admin tooling that could expose records across tenant boundaries.

Outcome

All three issues were remediated before the pipeline launched. The threat model document was included in their HIPAA compliance package. The engineering team adopted our STRIDE template for future feature design reviews.

3 high

severity issues found

0 findings

at HIPAA audit

STRIDE

process adopted by team

PENTESTSaaS Platform

Broken access control across a multi-tenant SaaS product

Challenge

A B2B SaaS company with 200+ enterprise customers needed a penetration test before renewing contracts with two Fortune 500 clients. Their product had grown rapidly and the authorization layer had been patched incrementally over three years.

What we found

We discovered a horizontal privilege escalation vulnerability in their resource-sharing API that allowed a user in one tenant to enumerate and read documents belonging to users in other tenants. The flaw was in a legacy endpoint that had been excluded from their automated test suite.

Outcome

The vulnerability was classified critical and patched within one sprint. We re-tested the fix and issued a clean attestation letter. Both enterprise contracts were renewed. The team subsequently engaged us for a secure SDLC integration to prevent similar issues in future releases.

Critical

cross-tenant data exposure

1 sprint

time to remediation

2 contracts

enterprise renewals secured

SDLCDev Tools Company

Secure SDLC integration for a 40-engineer team

Challenge

A developer tooling company had grown from 8 to 40 engineers in 18 months. Security reviews were ad hoc, secrets occasionally ended up in commits, and there was no consistent process for evaluating third-party dependencies. They needed security embedded in their workflow without slowing down a fast-moving team.

What we found

Our audit of their CI/CD pipeline found no secrets scanning, no SAST gates on pull requests, and 14 high-severity CVEs in production dependencies that had been present for over six months.

Outcome

We configured GitHub Actions security gates, integrated Semgrep for SAST, deployed Gitleaks for secrets detection, and set up Dependabot with a triage workflow. Within 30 days all 14 CVEs were resolved and the team had a documented security review process for new features.

14 CVEs

resolved within 30 days

3 tools

integrated into CI/CD

40 engineers

onboarded to new process

Want results like these for your codebase?

Every engagement starts with a scoping call. We'll tell you exactly what we'd look at and what we expect to find.