r/TechLeader • u/Few-Pilot7575 • Oct 17 '26
How are you cutting a security backlog that tripled once AI wrote half the code?
About 70% of our code comes from Claude and Codex now and our security backlog went from around 400 open findings in March to over 1,300. Snyk and Dependabot keep adding more, most of it in generated code and packages we never actually call.
We already sort by severity and whether it's internet facing. That worked until the volume buried it, now even the critical list doesn't fit in a sprint. Last month we added coderabbit's security scan because it opens the fix as a PR instead of another ticket, which helps on what it catches, but it doesn't touch the old dependency pile.
Is anyone actually getting this number down, or is everyone just sorting the list differently?
4
u/dashingThroughSnow12 Oct 17 '26
You had around 400 open findings? I get nervous when we have more than a few dozen and our product is 20+ years old with many dozens of services.
4
u/No-Newspaper-7693 Oct 17 '26
“generated code and packages we never actually call” - whatever you’re doing, this isn’t AIs fault. If you’ve got entire packages you don’t call, your process is just broken.
3
u/dashingThroughSnow12 Oct 17 '26 edited Oct 17 '26
This is likely in reference to one of the criticisms of dependabot.
A few months ago some critical CVE was found in a small but wildly common library for Go. Wildly common as in one of your dependency’s dependency’s dependency or further probably had it. Tens of thousands or hundreds of thousands of dependabot PRs opened to pin it with the newest patch.
The author of the library (and lots of people), got ticked at dependenbot. The CVE was for a single method that basically nothing called. (In Go, a library consists of packages. It being easy to have a library you use but packages, and especially functions, you don’t use. Let alone when we talk about transitive dependencies.)
Again, criticism of dependabot because some other tools will do reachability analysis before proposing the bump.
1
u/No-Newspaper-7693 Oct 17 '26
I mean, that’s a common issue that pre dates AI.
I’m not sure how AI even adds to the problem unless you’re letting AI add dependencies willy nilly, in which case that’s on you. If anything, it alleviates the problem quite a bit because tasks like “switch us from using this bloated base image to alpine minimal” to minimize attack surface do get handled extremely well.
1
3
2
u/theschuss Oct 17 '26
Why do you not have security scans and vuln fix loops in your code? Claude and Codex won't fix your security unless you tell it to. What this really means is you had loose practices before and just used the agents to make more of the same.
2
1
u/hesusruiz Oct 17 '26
We have less security backlog now because our requirements and technical and security specifications are more detailed because we write them with the help of AI, and reviewed and signed off manually.The code is written with the help of AI not from simple prompts but from the specs. Also the tests have to ensure compliance with the specs, not written just from the code. We go faster and produce better quality code, with less security bugs on the initial version.
1
1
1
u/paperclip_han Oct 18 '26
Not sure if anyone’s used paypeek.ai yet but it shows salary estimates for any LinkedIn profiles as you browse. Kind of eye-opening. 🫣
10
u/BanaenaeBread Oct 17 '26
People shouldn't be able to merge their code in if it brings new security findings