James Wickett (@wickett) 's Twitter Profile
James Wickett

@wickett

CEO & Co-Founder at DryRun Security, Instructor at LinkedIn Learning, and Univ. of Oklahoma Alum. For speaking requests: wickett.me

ID: 14836673

linkhttps://dryrun.security calendar_today19-05-2008 19:10:29

11,11K Tweet

5,5K Followers

1,1K Following

James Wickett (@wickett) 's Twitter Profile Photo

Today, I’m excited to announce the launch of two powerful new analyzers integrated into DryRun Security: SSRF (Server-Side Request Forgery) and IDOR (Insecure Direct Object References). These latest additions add to our suite of analyzers to ensure we continue to provide risk

Clint Gibler (@clintgibler) 's Twitter Profile Photo

🤖 One Year of Using LLMs for Application Security: What We Learned Ken Johnson shares key lessons learned and challenges faced Tips: - Use the right LLM for the task (e.g. some specialize in embeddings, or understanding code) - The value of RAG - Combining deterministic and

LiveOak Ventures (@liveoakvp) 's Twitter Profile Photo

We're thrilled to welcome DryRun Security to the LiveOak portfolio! DryRun raised $8.7M in seed funding to transform app security with AI-powered risk detection. Congrats to James Wickett, Ken Johnson & team! #WelcometotheLiveOakPortfolio

We're thrilled to welcome <a href="/dryrunsec/">DryRun Security</a> to the LiveOak portfolio! DryRun raised $8.7M in seed funding to transform app security with AI-powered risk detection.

Congrats to James Wickett, Ken Johnson &amp; team! 

#WelcometotheLiveOakPortfolio
James Wickett (@wickett) 's Twitter Profile Photo

Traditional SAST tools miss real risks. We tested DryRun Security vs. Snyk, CodeQL, Semgrep, and SonarQube—legacy tools struggled with IDOR, SSRF & logic flaws, but DryRun caught them all. See the full breakdown: dryrun.security/blog/dryrun-se…

James Wickett (@wickett) 's Twitter Profile Photo

The hardest problems in application security today are context-dependent. Authorization issues, PII data leaks, YAML misconfigurations in prod. Where code is run, why it was written, and what purpose it serves all make a huge difference in how much risk is being introduced to

James Wickett (@wickett) 's Twitter Profile Photo

Tomorrow is CYBERLUNCH #austin If you like Cyber, and you like Lunch, then... well, you get the picture here. Join the meetup so we know how many tables to fend off from the pizza hordes. meetup.com/cyberlunch/eve…

DryRun Security (@dryrunsec) 's Twitter Profile Photo

CodeRabbit RCE wasn’t prompt injection—it was tool execution + isolation drift + secrets exposure. We’ve stumbled too (IDOR in closed beta), which is why our sandboxed approach avoids this class of risk. 🔗Read more: na2.hubs.ly/y0S7hz0

CodeRabbit RCE wasn’t prompt injection—it was tool execution + isolation drift + secrets exposure. We’ve stumbled too (IDOR in closed beta), which is why our sandboxed approach avoids this class of risk.

🔗Read more: na2.hubs.ly/y0S7hz0