AI Office Hours with the
DryRun Security Founders
Surviving AppSec in the AI Trenches
James and Ken will unpack the latest industry news, share what’s new at DryRun, and discuss what AI-driven development means for AppSec teams working to keep up with faster code creation and a rapidly changing threat landscape.
Then we’ll open the floor for a live Q&A and an open discussion about all things AI, AppSec, code security, and DryRun. Bring your questions and your hot takes from the AI trenches.
.webp)

Ken Johnson
CTO and Co-Founder @ DryRun Security

James Wickett
CEO and Co-Founder @ DryRun Security
FAQs
Review and prioritize the highest-risk issues
Within a few hours you’ll get the results and if you want, one of our top appsec experts will review the top issues with you and a provide a practical path to remediation. That’s it, no strings attached.
Run DeepScan Agent on your codebase
You kick off the scan from the dashboard. We monitor progress and handle any issues should they come up (don’t worry, they won’t!).
Connect your repo
You perform a 5-minute install in the GitHub or GitLab app for your repo(s). We’ll walk through permissions and keep the process simple.
Meet with a DryRun Security expert
Short discovery call to confirm repo scope and what you want to learn (auth, business logic, secrets, or all three).
When should I use a DeepScan Agent review instead of a PR review?
Use it when you need broader coverage, for example onboarding a repo, preparing for an audit, after major refactors, before a release, orwhen developers introduce a new language.
Many teams run DeepScan on a cadence per production repo (monthly/quarterly), at key release checkpoints, or when risk changes, for example after big dependency updates or major architectural changes.
.webp)
.webp)
.webp)
.webp)

.webp)


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