How much time passes between discovering a vulnerability and getting the right person to fix it? On Tech Talks Daily, I'm joined by Vineet Edupuganti, co-founder and CEO of Cogent Security, to talk about the work that takes place after a scanner finds a problem.
Vineet describes it as an assembly line: someone has to find the affected systems, work out where they're exposed, identify the owner, and get the fix completed. Each handoff gives a ticket somewhere to get stuck.
One of the simplest examples Vineet gives is a vulnerability sent to the wrong person. The agent may have identified a real problem, but the recipient can't act on it. The ticket goes back and forth while the system stays exposed. We talk about how Cogent brings together security and operational data to help agents determine who owns what, and why the quality of those records affects what you can ask an agent to do.
We also discuss what Vineet calls governed autonomy. He describes customers setting their own boundaries and starting in environments where the consequences of a mistake are easier to contain. A development system and a customer-facing production service may need different permissions. He makes the case for auditable actions and limits on what an agent can change. I ask where analysts still need to be involved, especially when a fix could interrupt the business or when someone has to weigh a security risk against the cost of downtime.
For anyone considering another security tool, Vineet suggests looking at measures such as time to remediate and how often teams fix issues within their agreed deadlines. We also discuss the trade-off between a broader platform and a specialist tool that may do one job better.
I'd love to hear what you're seeing in your own organization. Which handoff would you trust an agent to handle today, and where would you still want a person to make the call? Please share your thoughts.

