@adampatarino2Rig: security verification for AI coding agents (Indianapolis)
Hi, I'm Adam Patarino, co-founder and CEO of Rig AI in Indianapolis. We're building Rig, security verification for AI coding agents. When an agent finishes its work, Rig checks the application and sends any findings straight back to the agent, while the code and context are still fresh.
The problem we keep seeing is that agents create code faster than teams can review it, and legacy scanners bury real issues under false positives. We're still early. Right now we're working out how the fix and verify loop should feel to developers, and how much context an agent needs to fix a finding correctly the first time.
What I'd love from this community is feedback from anyone running coding agents on production code, especially on how your team handles security findings today. Intros to security-minded engineers are also welcome.
Comments2
Going after the false positives from legacy scanners is a smart wedge, since most security leads have a story about losing days to noise. Who will you sell to first: the engineering head running the agents, or the security team that approves tools?
We are selling to security leads but building a bottoms up for engineers to adopt and bring into their orgs.
2 comments
Going after the false positives from legacy scanners is a smart wedge, since most security leads have a story about losing days to noise. Who will you sell to first: the engineering head running the agents, or the security team that approves tools?
We are selling to security leads but building a bottoms up for engineers to adopt and bring into their orgs.