Code Velocity In An AI-era:
How AppSec Teams Can Stay Ahead
In this fireside chat, DryRun Security and Commerce share real stories from teams shipping LLM and agentic features in production. We’ll cover what broke first, what mattered most, and how AppSec teams are adapting without becoming the team that slows shipping.
You’ll learn:
.webp)

James Wickett
CEO and Co-Founder At DryRun Security

Ken Johnson
CTO and Co-Founder At DryRun Security

Adam Dyche
Manager Application Security Engineering At Commerce

Zac Fowler
Sr. AppSec Engineer At DryRun Security
FAQs
How is DryRun Security priced?
Pricing is aligned with the size of your engineering and security teams. It focuses on the number of developers and security team members using DryRun Security and owners requiring codebase visibility.
What deployment and compliance options exist?
DryRun is delivered as SaaS with strict data handling. It supports SOC 2, ISO 27001, PCI, and HIPAA by generating artifacts of SDLC controls.
How does DryRun conduct code reviews?
Reviews are based on the COVER model:
- Context: Understanding the language, environment, and business logic.
- Orchestration: Managing agents and integrating with CI/CD.
- Verification: Rigorously confirming flaws to eliminate false positives.
- Exploitability: Assessing if an attacker could actually leverage a flaw.
- Reporting: Providing actionable technical details and leadership summaries.
How are vulnerabilities prioritized?
They are ranked by impact and likelihood using SLIDE signals and code context. Dashboards highlight the most critical areas for teams to address first.
How does DryRun reduce false positives?
It uses multi-signal context, policy tuning, and suppression of known-safe patterns. Developer feedback is also used to continually sharpen the signal.
.webp)
.webp)
.webp)
.webp)

.webp)


%20(1).jpg)
%20(1).png)