Windows Copilot was so terrible it might very well have seeded the AI opposition we now see among normies. Useless functionality, hyped to the moon, and a dumb key on every keyboard that did nothing worthwhile. youtube.com/watch?v=erRVsllM…
James Wickett retweeted
Trying to clarify different AI software factory loops: (blogpost pending)
- production loops: these act on the code
- maintenance loops: keeps the line running within the factory rules
- feedback loops: changes the rules what the factory decides
Thoughts are welcome!
James Wickett retweeted
PR FEEDBACK IS LIVE IN DRYRUN SECURITY 🔥🔥🔥
When a security finding shows up in a pull request, it shouldn’t turn into a side quest. PR Feedback closes that loop.
Now when DryRun Security flags something, developers can reply directly in the thread to mark a false positive or nitpick. DryRun updates the findings instantly, regenerates the PR summary, and logs the action for a clean audit trail.
No tickets to file.
No separate workflow to manage.
No chasing someone down to clear it.
Read how it works → dryrun.security/blog/securit…
James Wickett retweeted
AppSec leaders: quick gut check. Can you answer these questions about your program with confidence?
In this short video, @cktricky, DryRun Security CTO & Co-founder, shares the pointed questions he keeps hearing teams struggle with as development and risk accelerates:
❓Can you train developers based on the actual risks they introduce instead of one-size-fits-all training?
❓Do you know what’s being shipped without being told beyond the release/review process?
❓Are your developers ready to build secure AI applications?
❓Do you know which teams are using AI coding assistants, and do you have the right guardrails?
❓Can you respond to zero-days in minutes, with clear visibility into exposure and next steps?
If any of these made you pause, you’re not alone. A lot of teams are still forced into the “old way” of doing AppSec while engineering velocity keeps climbing.
We built DryRun Security to help practitioners close these gaps with a modern approach to code risk and visibility.
If you want confidence in answering these questions, schedule a demo with us at dryrun.security/get-a-demo
James Wickett retweeted
📢 We’re thrilled to welcome Andrew Peterson to our Board of Directors, effective immediately!
Andrew is a rare blend of security builder, technologist, and investor with a track record of helping create category-defining companies. He:
➡️ Co-founded Signal Sciences, helping pioneer modern web app & API security (acquired by Fastly in 2020)
➡️ Founded Aviso Ventures, an early-stage fund focused on enterprise & infrastructure software
➡️ Has backed standout AI security teams including Protect AI (acquired by Palo Alto Networks in 2024) and SGNL.ai (acquired by CrowdStrike earlier this year)
As Andrew put it:
“As AI agents take on more responsibility in writing and reviewing code, security must evolve into something more intelligent, contextual, and adaptive.”
That’s exactly the mission at DryRun Security: AI-native code security intelligence built for the agentic era—reducing noise, surfacing real risk, and bringing policy-driven visibility to agentic code changes.
Since emerging from stealth, DryRun Security customers are now running 250,000+ code reviews per month through DryRun Security, proof that the way software is built is changing fast, and security has to keep up.
Welcome, Andrew! We’re excited to build what’s next! 💥
🔗 Read more at globenewswire.com/news-relea…
James Wickett retweeted
AI did not create entirely new AppSec problems.
It changed where they show up.
Prompts. Generated code. Tool calls. Model integrations.
The risks are familiar. The workflows are not.
Join our live fireside chat, Code Velocity in an AI-era: How AppSec Teams Can Stay Ahead, with Adam Dyche with @poweredbyCMRC, @wickett , @cktricky, and Zac Fowler with DryRun Security.
They'll unpack how real teams are securing LLM-powered applications without rebuilding their entire AppSec stack.
🗓️ Feb 4 | 1PM ET
Register 👉 na2.hubs.ly/H037Qhw0
James Wickett retweeted
LLMs are everywhere in your stack and every layer brings new #risk
buff.ly/QxQvEVg
@HelpNetSecurity @Wickett @DryRunSec #cybersecurity #business #digital #innovation #digitaltransformation #leadership #management #CIO #CTO #CISO #CEO #CDO #AIrisks #tech #LLM #genAI
James Wickett retweeted
LLM apps are moving fast, and the risks are moving faster.
That’s why we’ve developed a guide for securing AI Applications.
In “Building Secure AI Applications,” we break down how the OWASP LLM Top 10 shows up in real systems and map each risk to controls teams can actually implement today.
If you’re building or securing LLM features, we include a full vendor-neutral reference architecture.
Download the Guide → dryrun.security/resources/ow…
James Wickett retweeted
Mark Burgess once pointed out that determinism in large systems is mostly an illusion. He was right.
We pretend our tools can capture risk with fixed rules, but modern software isn’t static enough for that.
In our most recent post, @wickett discusses how AI is pushing us into an era where code evolves faster than rule sets ever could. Probabilistic security isn’t a trend; it’s becoming the only model that fits reality.
Read the whole post at dryrun-staging.webflow.io/bl…
James Wickett retweeted
Huge thanks to the @LASCONATX volunteer team (incredible hosts) and to everyone who stopped by our booth for great #appsecurity conversations.
If you missed it live, catch @wickett's talk "Out of Control: Promise Theory and the Future of Code Security Agents" slides here: promise-theory-34zpp7h.gamma…
James Wickett retweeted
Thrilled to team up with @secdim to connect DryRun Security contextual risk insights with hands-on secure coding labs. This helps engineering teams turn findings into learning and fixes faster. Thanks, Pedram, for this innovative use case for the DryRun MCP!
This is how you use SAST findings to upskill developers in security, right in your Claude IDE. Brought to you by @dryrunsec + @secdim #sast #training #securecoding
James Wickett retweeted
Get superhuman visibility into your security posture, architecture, and more! Announcing DryRun Security Code Insights MCP.
Now you can ask your code what changed and why:
👉 “Hey DryRun, are there any new admin endpoints this week?”
👉 “Which PRs touched auth or payments?”
Don’t let important security changes slip past review, or waste hours gathering data for your next audit.
With Code Insights MCP, you can speak or type a request and get results in seconds, complete with charts and auto-remediation.
Read more on our blog from Ken Johnson: na2.hubs.ly/H011CJs0
#AppSec #DevSecOps #CodeSecurity #AI #MCP
James Wickett retweeted
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
James Wickett retweeted
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 your codebase.
@DryRunSecurity lets you phrase a security rule exactly the way you’d say it in a design review—“Does this endpoint require admin rights?”—and have DryRun enforce that rule every time a developer opens a pull request. Instead of guessing with brittle regular expressions, our Contextual Security Analysis engine translates plain-English rules into precise, always-up-to-date checks.
Still chasing false positives with regex? 😵💫
Our NLCPs treat code as context, not just text—so you catch real risk, fast.
See how AppSec teams are spotting auth gaps, insecure workflows & PII leaks 🔍
👇 Read the blog
na2.hubs.ly/y0kSB50
#AppSec #DevSecOps #AI
James Wickett retweeted
We're thrilled to welcome @dryrunsec 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
James Wickett retweeted
🤖 One Year of Using LLMs for Application Security: What We Learned
@cktricky 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 probabilistic methods works best
- Agent-based execution enhances performance: give access to tools and docs vs single-shot question and answer interactions
dryrun.security/blog/one-yea…
James Wickett retweeted
survivalTipThatProgrammersDontWantYouToKnow reddit.com/r/programmerhumor…

























