TestGuild Devops Toolchain Podcast

There are genuine data points and a coherent technical workflow (scan → auto-remediate → validate → pull request loop, up to 6 iterations), but the episode is heavily padded with product marketing, filler affirmations, and repetition of the same concepts across multiple answers. The ratio of novel claims to filler is moderate at best.

“we have customers that are running 55, 60,000 scans a month, which is completely unheard of”

“we're seeing static tools that are at 60, 70% false positives. That's just not acceptable”

The validated auto-remediation loop (dynamic proof before and after fix) is a genuinely differentiated framing compared to the 'AI fixing AI' static approach, and the 500-600% vulnerability growth claim from AI-assisted coding is thought-provoking - but the episode largely stays in vendor-pitch territory without first-principles or contrarian arguments that a practitioner couldn't deduce independently.

“these same developers are creating 150 to 200% of code, but 500 to 600% of vulnerabilities”

“we are not relying on AI to fix AI. We are guiding the AI”

Gadi Bashvitz is a genuine operator - CEO of an 8-year-old DAST company with real enterprise deployments and a military cybersecurity background - giving him credible practitioner standing. However, the format is essentially a vendor demo, which limits the candid insight that elevates caliber scores higher.

“we have companies with 15, 16, 20,000 developers using the solution”

“you're looking at some of the world's largest banks, companies like Blackstone, so very large financial institutions”

There are several concrete numbers (15,000+ payloads, 55-60k scans/month, 90% auto-remediation rate, <3% false positive commitment for technical vulns, 12 weeks→12 hours, 98% improvement) that anchor the episode. The main drag is that most enterprise customers are unnamed ('world's largest private equity company,' 'world's largest financial institution') and headline claims like the 500-600% vulnerability increase carry no cited source.

“our commitment is, look, we're going to have less than 3% false positives for technical vulnerabilities”

“we will run up to six iterations because we've seen that after six, there's diminishing returns”

The host consistently leads the witness, summarises the guest's own answers back to him, and delivers zero meaningful pushback on significant unverified claims (e.g., the 500-600% vulnerability multiplier, the 90% auto-remediation success rate). Questions function as prompts for marketing talking points rather than genuine probes.

“This sounds awesome, but I know developers have been burned in the past”

“I can assume if you're in like, in a regulated environment like uh, banking or healthcare, you need proof of certain things. This sounds like it's doing it all automatically for you”