Menu

I couldn't find an AI agent for AppSec audits, so I built one and benchmarked it on real CVEs
πŸ“°

I couldn't find an AI agent for AppSec audits, so I built one and benchmarked it on real CVEs

DEV Community: appsecΒ·vlfdΒ·3 days ago
#e9vwstBt
#devtoappsec#devto#dev#agent#code
Reading 0:00
15s threshold

Ask Claude Code, or any coding agent, to "check this module for vulnerabilities" and you know how it goes. It skims a couple of controllers, flags string concatenation in a test file, writes a confident three-screen report, and an hour later you can't tell which requirements it actually checked and which it quietly skipped. Ask again tomorrow and you get a different report.

I wanted something else: an audit where the agent sees everything a human AppSec engineer would look at (the entry point map, Semgrep and Trivy output, the company's own security standard, the dependency report, past decisions) and where the result lands in a database, tied to a commit, and goes stale when the code changes.

I didn't find a tool that did that, so I built aiegis. It's an Electron and TypeScript desktop app, plus a headless service for Linux, that drives your local coding agent and turns its output into a managed process.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.